AgentReady standard — draft conformance
AgentReady is an open, vendor-neutral standard for agent readiness, currently a v0.0.1 working draft (no requirement is normative until its v1.0.0). It shares our name by coincidence (we are unaffiliated) — so we resolve the collision the honest way: by implementing its surfaces and tracking the draft as it evolves. This page is our public self-audit, cited by the draft's stable IDs.
Status: 9 of the draft's 19 requirements implemented today — partials and non-applicable requirements documented below. The draft keeps every requirement's normative weight TBD, so this table reports our surface status, not a conformance claim; we will re-audit when normative wording lands. The draft itself: agentready.org · github.com/agentready-org/standard (spec/draft.md, 2026-04-26).
| Stable ID | Requirement (draft wording, abridged) | Weight in draft | Our status | Where / rationale |
|---|---|---|---|---|
AR-DISC-01 |
robots.txt declaring AI-agent policy | TBD | ✅ pass | /robots.txt — explicit AI-crawler section |
AR-DISC-02 |
A2A Agent Card at /.well-known/agent-card.json | TBD | ✅ pass | /.well-known/agent-card.json |
AR-DISC-03 |
llms.txt at the site root | TBD | ✅ pass | /llms.txt (plus /llms-full.txt — everything in one file, beyond the draft) |
AR-DISC-04 |
Sitemaps cover agent-relevant content | TBD | ✅ pass | /sitemap.xml |
AR-CONT-01 |
JSON-LD / Schema.org on key pages | TBD | ✅ pass | Organization, Product, Offer, FAQPage on /, /pricing, /about |
AR-CONT-02 |
Content negotiation for Accept: text/markdown | TBD | 🟡 partial | markdown twins served as URLs (/index.md, /pricing.md, /api.md, /auth.md, /agents.md); Accept-header negotiation itself planned |
AR-CONT-03 |
Stable, addressable URLs for agent-consumed entities | TBD | ✅ pass | reports /r/<id>, articles /research/<slug>, live badges /badge/<host>.svg |
AR-CAP-01 |
MCP server card (products exposing an MCP surface) | TBD | ✅ pass | /.well-known/mcp/server-card.json — MCP server itself at /mcp, Streamable HTTP, keyless |
AR-CAP-02 |
OpenAPI 3.1 document for HTTP API surfaces | TBD | ✅ pass | /openapi.json (OpenAPI 3.1) |
AR-CAP-03 |
A2A capability descriptors (A2A surfaces) | TBD | — n/a | no A2A task endpoint — the discovery card (AR-DISC-02) is served; revisit if an A2A surface ships |
AR-CAP-04 |
/.well-known/api-catalog for multiple HTTP APIs | TBD | ✅ pass | RFC 9727 linkset |
AR-AUTH-01 |
OAuth 2.0 for delegated agent access | TBD | — n/a | no delegated third-party access to user-owned resources (owner-held API key only) |
AR-AUTH-02 |
Authorization Code flow with PKCE | TBD | — n/a | no OAuth clients |
AR-AUTH-03 |
OAuth Authorization Server Metadata | TBD | — n/a | no OAuth authorization server |
AR-AUTH-04 |
OAuth Protected Resource Metadata | TBD | — n/a | no OAuth-protected resources |
AR-AUTH-05 |
OpenID Provider Configuration | TBD | — n/a | no OIDC |
AR-AUTH-06 |
Web Bot Auth (RFC 9421 + key directory) | TBD | 🟡 partial | /.well-known/http-message-signatures-directory implemented, and our audit crawler signs Ed25519 when keyed; key publication pending configuration |
AR-COMM-01 |
x402 on machine-initiated-payment surfaces | TBD | — n/a | we do not accept machine-initiated payment — our audit MEASURES x402 adoption on merchants' stores |
AR-COMM-02 |
ACP / UCP / MPP per-surface support | TBD | — n/a | same — measured on merchants' stores, not accepted here; the mapping is the draft's open question #5 |
Per the draft's per-surface conformance model, requirements
apply only to the surface types a product exposes — the n/a rows document which
surfaces we don't have (no OAuth-delegated access, no A2A task endpoint). The
commerce rows (AR-COMM-*) apply to surfaces accepting machine-initiated payment —
we don't accept agent payment; our audit measures those protocols
(x402, UCP, ACP) on merchants' stores instead. Beyond the draft, we also serve
llms-full.txt, /index.md, RFC 8288 Link discovery headers on every page, an ARD
ai-catalog and an NLWeb-style /ask endpoint.