AgentReady v1.0.0 conformance
AgentReady is the open, vendor-neutral standard for agent readiness. It shares our name by coincidence (we are unaffiliated) — so we resolve the collision the honest way: by implementing it. This page is our public self-audit, requirement by requirement, cited by the spec's stable IDs.
Status: every applicable MUST passes (12 requirements implemented; deviations and non-applicable requirements documented below, as the spec's conformance rules require). The spec itself: agentready.org · github.com/agentready-org/standard · snapshot in our repo.
| Stable ID | Requirement | Strength | Status | Where / rationale |
|---|---|---|---|---|
AR-DISC-01 |
robots.txt with AI policy | MUST | ✅ pass | /robots.txt — explicit AI-crawler section |
AR-DISC-02 |
Sitemap | SHOULD | ✅ pass | /sitemap.xml |
AR-DISC-03 |
llms.txt | SHOULD | ✅ pass | /llms.txt |
AR-DISC-04 |
llms-full.txt | MAY | ✅ pass | /llms-full.txt — docs + full research corpus, one file |
AR-DISC-05 |
HTTP Link header | MAY | ✅ pass | rel=sitemap, describedby, api-catalog, alternate + rel=service on every page |
AR-DISC-06 |
NLWeb schema feeds | MAY | — n/a | no natural-language retrieval surface |
AR-CONT-01 |
JSON-LD structured data | SHOULD | ✅ pass | Organization, Product, Offer, FAQPage on /, /pricing, /about |
AR-CONT-02 |
Markdown content negotiation | MAY | 🕓 planned | evaluating for key pages |
AR-CONT-03 |
/index.md fallback | MAY | ✅ pass | /index.md |
AR-CONT-04 |
Speakable markup | MAY | — n/a | no voice-agent content |
AR-CAPA-01 |
MCP | MUST | ✅ pass | /mcp — Streamable HTTP, keyless |
AR-CAPA-02 |
MCP Server Card | SHOULD | ✅ pass | /.well-known/mcp/server-card.json |
AR-CAPA-04 |
A2A Agent Card | MUST | ✅ pass | /.well-known/agent-card.json |
AR-CAPA-08 |
OpenAPI | MUST | ✅ pass | /openapi.json (OpenAPI 3.1) |
AR-IDEN-01 |
Web Bot Auth | SHOULD | ⚠️ documented deviation | documented rationale: every agent surface is public, free and keyless — signature verification would gate nothing; revisit when Pro-scoped agent access ships |
AR-IDEN-02 |
OAuth 2.0 | MUST | — n/a | no delegated third-party access to user-owned resources (owner-held API key only) |
AR-IDEN-03 |
OAuth AS Metadata | MUST | — n/a | no OAuth authorization server |
AR-IDEN-05 |
PKCE | MUST | — n/a | no OAuth clients |
AR-IDEN-04 |
OAuth Protected Resource | SHOULD | — n/a | no OAuth-protected resources |
AR-IDEN-06 |
API Catalog | MAY | ✅ pass | /.well-known/api-catalog (RFC 9727) |
AR-COMM-* |
Commerce (x402/ACP/UCP/MPP) | MAY | — n/a | we do not accept agent payment; our audit MEASURES these protocols on merchants' stores |
Per the spec's conformance language, a product conforms when it implements every applicable MUST; SHOULD deviations are permitted with documented rationale (see AR-IDEN-01 above). Commerce requirements are alternatives that apply to products accepting agent payment — we don't; our audit measures those protocols (UCP, ACP, x402) on merchants' stores instead.