AgentReady standard v2.0 — conformance
AgentReady is an open standard for making a site readable and usable by AI agents, now at v2.0 with normative MUST / SHOULD / MAY levels. It shares our name by coincidence (we are unaffiliated, operated by Villepinte Studio at agentready.market) — so we resolve the collision the honest way: by implementing its surfaces and publishing this self-audit, cited by its stable IDs.
Status: 4 of 4 MUSTs met; 19 of 24 requirements fully implemented — partials, planned items and non-applicable requirements documented below. The weight column is the standard's own; the status column is ours. The standard itself: agentready.org · github.com/agentready-org/standard (spec/spec.md, v2.0, October 2026).
| Stable ID | Requirement (abridged) | Weight | Our status | Where / rationale |
|---|---|---|---|---|
AR-FIND-01 |
Don't block agent and crawler access (robots.txt or network layer) | MUST | ✅ pass | /robots.txt welcomes AI agents and crawlers by name; no WAF challenge on public pages |
AR-FIND-02 |
Citable answers on one canonical, first-party docs page | SHOULD | ✅ pass | /api (+ /api.md), /methodology, /pricing |
AR-FIND-03 |
sitemap.xml referenced from robots.txt | SHOULD | ✅ pass | /sitemap.xml, named in /robots.txt and in the Link header |
AR-FIND-04 |
AI Catalog at /.well-known/ai-catalog.json | MAY | ✅ pass | /.well-known/ard.json (ARD v0.91) + legacy ai-catalog.json |
AR-READ-01 |
Answer present in the initial HTML, not injected by JS | MUST | ✅ pass | every page is server-rendered by Django |
AR-READ-02 |
Accurate status codes: 404 for missing paths, 429 with Retry-After | MUST | ✅ pass | structured JSON 404 on unknown /api paths; 429 carries Retry-After and IETF RateLimit headers |
AR-READ-03 |
Homepage as raw HTML with real links to docs, product, pricing | SHOULD | ✅ pass | / links /api, /pricing, /methodology in plain anchors |
AR-READ-04 |
Docs answer the tasks users bring to agents | SHOULD | ✅ pass | /api walks through scan, read a report, MCP setup |
AR-READ-05 |
Code snippets fenced and language-tagged | SHOULD | ✅ pass | every <pre><code> carries class="language-…"; markdown fences in articles and the agent brief are tagged |
AR-READ-06 |
Discovery files linked from content agents visit | SHOULD | ✅ pass | <link rel=alternate> in every page head, RFC 8288 Link header on / |
AR-READ-07 |
A lean, described llms.txt | SHOULD | ✅ pass | /llms.txt (plus /llms-full.txt) |
AR-READ-08 |
JSON-LD on key pages, homepage above all | SHOULD | ✅ pass | Organization, Product, Offer, FAQPage on /, /pricing, /about |
AR-READ-09 |
Markdown mirror advertised via rel=alternate text/markdown | MAY | ✅ pass | /index.md advertised in the Link header of /; twins /pricing.md, /api.md, /auth.md, /agents.md |
AR-READ-11 |
Pricing on a first-party page, as text | SHOULD | ✅ pass | /pricing, plans and limits in plain HTML |
AR-ACT-01 |
Authentication completable by an agent | SHOULD | 🟡 partial | reads and the MCP server are keyless; the Pro key is issued after a human checkout (/auth.md) |
AR-ACT-02 |
Public API described by an OpenAPI contract | SHOULD | ✅ pass | /openapi.json (OpenAPI 3.1, /api/v1 versioning, documented limits) |
AR-ACT-03 |
MCP server over Streamable HTTP at /mcp | SHOULD | ✅ pass | /mcp, keyless; docs server at /mcp/docs |
AR-ACT-04 |
MCP server card for pre-connection discovery | MAY | ✅ pass | /.well-known/mcp/server-card.json |
AR-ACT-05 |
MCP Apps view (ui:// resource) | MAY | — n/a | not shipped: the report page itself is the hand-back surface |
AR-ACT-06 |
Published SDKs and a CLI | SHOULD | 🕓 planned | no package on npm/PyPI yet; agents act through /mcp and the HTTP API |
AR-ACT-07 |
WebMCP tools on document.modelContext | SHOULD | ✅ pass | check_merchant_readiness registered on document.modelContext on every page (feature-detected, forwards to /mcp); the scan forms declare scan_store_agent_readiness via toolname |
AR-ACT-08 |
Agents can pay (x402 / MPP / UCP / ACP) | MAY | — n/a | we don't take agent payment; our audit MEASURES these protocols on merchants' stores |
AR-ACT-09 |
NLWeb /ask endpoint, same tool over MCP | MAY | 🟡 partial | NLWeb-style /ask served; the MCP equivalent is search_agentready_research on /mcp/docs |
AR-ACT-10 |
At least one interface an agent can act through: MCP server or CLI | MUST | ✅ pass | /mcp (AR-ACT-03) |
The standard covers sites and products in general; it
does not audit the transaction. Its only commerce line is AR-ACT-08
(agent payments, MAY). That is the lane our audit measures on merchants' stores:
can an agent find the offer, read the price and stock, reach the cart and the
checkout. Beyond the standard, we also serve llms-full.txt, RFC 8288 Link
discovery headers and an A2A agent card.