On 30 October 2026 Agentic Resource Discovery was submitted to the IETF as three Internet-Drafts, under the name Agent Resource Discovery. Every day we check every domain known to publish an ARD manifest against them. Last measured 2026-11-02 14:41:26 UTC, 460 publishers.
A manifest at /.well-known/ard.json, served as application/ard+json: the initial
contact draft gives a response with any other media type the outcome no manifest. Optionally, a
Link: rel="ard" header on the root, an SVCB record at _index._agents.<domain>
naming a host that serves the manifest, and DNS-SD under _ard._tcp. The write-up of the drafts is
here.
| Content-Type | Publishers | Share |
|---|---|---|
application/json | 167 | 94.4% |
application/ai-catalog+json | 7 | 4.0% |
application/ard+json | 2 | 1.1% |
application/ard-manifest+json | 1 | 0.6% |
The two served as application/ard+json on 2 November 2026 were neuronto.com and
ardregistry.net, which switched that day.
| Date | Checked | ard.json | ard+json | Link rel=ard | SVCB | DNS-SD |
|---|---|---|---|---|---|---|
| 2026-11-02 | 460 | 177 | 2 | 35 | 51 | 0 |
curl -sI https://example.com/.well-known/ard.json | grep -i content-type curl -sI https://example.com/ | grep -i '^link' dig +short _index._agents.example.com TYPE64
Or run the free audit, which reports all three, or pip install ard-publish
and ard-publish check example.com.
Download the latest measurement as JSON (summary, history and one row per publisher) or CSV, under CC BY 4.0. The publishers are the domains our crawler has found serving a manifest at either well-known path. Each is requested once a day with a ten second timeout. A DNS answer counts only when its record type matches, because a wildcard record answers every name.