Verified 1 September 2026
ARD conformance: what the official test checks, and how to run it on any registry or manifest
The Agentic Resource Discovery specification ships its own conformance tool. It validates a
manifest (is this ard.json something a consumer can rely on) and a registry (does this
search service behave as the specification says). Neuronto passes both with zero errors and zero warnings; the
commands below reproduce that result against any URL, including this one.
Run it
git clone https://github.com/ards-project/ard-spec
cd ard-spec
conformance/bin/conformance-test manifest https://neuronto.com/.well-known/ard.json
conformance/bin/conformance-test registry https://neuronto.com
Substitute your own domain to test your manifest, or another registry's root to test it as a registry.
What the manifest check covers
- the document parses and carries
specVersion, ahostand anentrieslist - every entry has an
identifierin the URN form the specification defines, with the publisher segment matching the domain - every entry delivers its resource by value or by reference, not both and not neither
- media types are ones the specification recognises
What the registry check covers
POST /searchanswers 200 with a results list, and every item carriesidentifier,scoreandsourcePOST /explore, if present, returns a facets objectGET /agents, if present, returns a properly paginated object, not a bare list
Where registries fail
The most common failure seen across the public registries is GET /agents answering 200 with a body
that is not a paginated object. The tool marks the whole registry FAIL on exactly that, however good its
search results are. The second is a manifest served on only one of the two well-known paths: the
specification's version 0.91 renamed ai-catalog.json to ard.json, and most deployed
publishers still serve only the older name, so a consumer checking one path misses most of the ecosystem.
Serve both.
Neuronto's result
| Role | Result | Errors | Warnings | Checked |
|---|---|---|---|---|
manifest, /.well-known/ard.json | PASS | 0 | 0 | 1 September 2026 |
registry, POST /search, /explore, /agents | PASS | 0 | 0 | 1 September 2026 |
It is re-run after every deployment. The result is stated here rather than as a badge because a badge cannot be re-run and a command can. Last re-run: 2 November 2026, PASS, 0 errors, 0 warnings, for both roles.
What the IETF drafts add, and the tool does not check yet
On 30 October 2026 ARD was submitted to the IETF as three Internet-Drafts, under the name Agent Resource Discovery. A few of their requirements are not in the conformance tool, so a manifest can pass it and still be skipped by a client that follows the drafts. Check these by hand, or with the free audit, which reports all three.
| Requirement | Check | Neuronto |
|---|---|---|
Manifest served as application/ard+json | curl -sI https://example.com/.well-known/ard.json | yes |
Link: rel="ard" on HEAD / | curl -sI https://example.com/ | yes |
SVCB at _index._agents (optional) | dig _index._agents.example.com TYPE64 | yes |
Registry entry url is the base URL | the application/ai-registry+json entry | yes |
| Errors as RFC 9457 Problem Details | POST /search with an empty query | yes |
On 2 November 2026, of 179 publishers serving /.well-known/ard.json, none served it as
application/ard+json. The details are in our write-up of the drafts,
and the count is re-measured daily on the ARD IETF readiness tracker.
Check your own manifest without installing anything
The free audit runs the same conformance checks on your manifest, entry by entry, with
each finding written as an instruction rather than an error code, and then asks every public registry whether
they return you. pip install ard-publish gives you ard-publish validate for the local
half and ard-publish check for the live one.
Check your own domain. The console fetches what you publish and asks every public registry whether they return you.
Run a free audit