agents.json at /.well-known/agents.json (obsolete)
What it checks
Whether the site still publishes an agents.json document (Wild Card AI, spec v0.1.0) at /.well-known/agents.json. A document is recognised by the shape the spec defines: an info object with a sources or a flows array.
The check never asks a site to publish the file. It exists to tell an owner who still publishes it that no reader is known.
| State | Result |
|---|---|
| a parseable agents.json document | warn, priority low |
| no response, a non-200, an HTML page, an empty body, a body that is not JSON, or JSON of another shape | notApplicable |
Why it matters
Mechanism: agents.json was proposed in 2025 as an OpenAPI-derived contract that lets agents discover and call a site’s API workflows. The claim this audit tests is that nothing reads it today.
Evidence
- The spec repository was last pushed on 2025-08-21 and the spec never moved past v0.1.0 — wild-card-ai/agents-json (verified 2026-10-18)
- The project homepage, agents-json.com, did not answer on 2026-10-18.
/.well-known/agents.jsonis not in the IANA Well-Known URIs registry — IANA (verified 2026-10-18)- No AI vendor or agent framework documents fetching the path. At least four incompatible formats publish files at it.
Limits
The repository is not archived, so the project could resume. The audit would then be re-graded.
How it scores
Grade: D — no consumer is documented, the spec is dormant, and the path is unregistered. An obsolete audit carries weight 0 and never returns fail (sunset.test.ts; Audit.toCheckResult lowers a stray fail to warn). It does not move any score.
Example finding
/.well-known/agents.json serves {"info":{…},"sources":[…]}. The report says no client reads the file and names A2A agent-card.json, an MCP Server Card, or RFC 9727 api-catalog as maintained routes.
Sources
- wild-card-ai/agents-json — Wildcard AI, draft-spec (verified 2026-10-18)
- agents-json.com — upstream repo’s listed homepage, unreachable — Wild Card AI, vendor-doc (verified 2026-08-21)
- IANA Well-Known URIs registry — IANA, spec (verified 2026-10-18)
- Only Four API Providers Publish a Real .well-known/api-catalog Right Now — API Evangelist, study (verified 2026-08-20)
- RFC 9727 — api-catalog: A Well-Known URI and Link Relation to Help Discovery of APIs — IETF, spec (verified 2026-08-21)
- experimental-ext-server-card — docs/discovery.md — Model Context Protocol, draft-spec (verified 2026-10-18)
- Live deployment: Vercel /.well-known/api-catalog (RFC 9727) — Vercel (probed by Agent Lighthouse research, 2026-08-20), dataset (verified 2026-08-20)
- Live deployment: Vercel /.well-known/ai-catalog.json — Vercel (probed by Agent Lighthouse research, 2026-08-20), dataset (verified 2026-08-20)
- Live deployment: Zapier /.well-known/api-catalog — Zapier (probed by Agent Lighthouse research, 2026-08-20), dataset (verified 2026-08-20)