Agent Readiness Compare

Agent readiness checklist summary

What readiness checks cover by layer, the AgentReady spec behind them, and who tests how much of it.

In short

Agent readiness checks cover five layers: find, read, act, pay and trust. The AgentReady spec turns them into 24 identifiers in three stages, four of them MUSTs. The spec scores nobody. Public scanners test very different shares of those identifiers, from about a sixth to all of them by this site's mapping.

What the checks cover

This page summarises what a readiness check looks at. It does not give step-by-step fixes. The five layers come from lesson 1, and each answers one question an agent's task depends on.

Layers, the question each asks and where the standards sit
LayerQuestionWhat the checks look atStandards
FindCan an agent find you, and is it allowed in?Whether robots.txt and network rules let agents through, and whether key pages are discoverableRFC 9309, Content Signals
ReadCan it read what you offer?Whether the answer is in the initial HTML, whether status codes are accurate, and whether markdown, llms.txt and structured data existllms.txt
ActCan it complete a task?Whether an MCP server, CLI, WebMCP tools or an API description let an agent do the taskMCP, WebMCP, NLWeb, agents.json
PayCan it pay you?Whether a machine-readable payment path exists where you chargex402, UCP, ACP
TrustCan you tell which agent it is?Whether your edge verifies signed requests and delegates access safelyWeb Bot Auth

The AgentReady spec

AgentReady launched on 19 October 2026 as an open standard for what a product should implement so agents can use it. Its repository README says the spec is written by ora.ai and Vercel, and that the research was conducted by the ora.ai research lab. Ora's launch post lists committee reviewers by area: Ora, Vercel, Mintlify, Auth0, Stripe, Tavily and Elementor. Google and MIT are named as partners there.

Version 2.0, from October 2026, has 24 live identifiers. They sit in three stages, and each carries a strength level of MUST, SHOULD or MAY.

AgentReady v2.0 identifiers by stage
StageLive identifiersRange
Find4AR-FIND-01 to 04
Read10AR-READ-01 to 09 and 11; AR-READ-10 is retired
Act10AR-ACT-01 to 10

The spec has no separate pay or trust stage. Agent payments are AR-ACT-08, a MAY. Verified identity touches AR-FIND-01 through Web Bot Auth.

The four MUSTs

  • AR-FIND-01: do not block agent and crawler access in robots.txt or at the network layer.
  • AR-READ-01: put the answer in the initial HTML.
  • AR-READ-02: return accurate status codes.
  • AR-ACT-10: expose an MCP server or a CLI when agents should act on the product.

Everything else is SHOULD or MAY. The MUST, SHOULD, MAY levels reflect what an agent fails without, which practices changed agent behaviour, and which conventions are still emerging.

What version 2.0 changed

  • AR-ACT-10, an MCP server or a CLI, became a MUST.
  • WebMCP (AR-ACT-07) rose to SHOULD.
  • AR-READ-10 was retired.
  • New identifiers: AR-FIND-04 (AI Catalog), AR-READ-11 (first-party pricing), AR-ACT-08 (agent payments) and AR-ACT-09 (NLWeb).

The repository recorded these changes in its changelog, last pushed on 21 October 2026.

What the spec does not do

The spec names scoring as a non-goal. It sets no weights, thresholds or badges, and it introduces no manifest format of its own. It scores nobody. Scoring is left to scanners and their methodologies, and the spec points to Ora's. A spec identifier is not a grade, and passing every MUST is not a ranking.

Source of the evidenceOra's lab found (19 Oct 2026), across 19 configurations of one docs site and 190 probes, that only a JavaScript-only answer and a 403 for agent user agents stopped retrieval. Markdown mirrors, llms.txt, JSON-LD and sitemaps did not change it. That is a vendor claim from Ora's own experiment.

How many identifiers each scanner tests

The counts below are this site's own mapping of each scanner's published checks to the 24 identifiers, read on 4 November 2026. They are not scores and not quality ratings.

Scanner coverage of the 24 AgentReady identifiers, by this site's mapping
ScannerIdentifiers coveredNote
OraAll 24132-check catalog, from robots and bot detection to MCP, WebMCP, x402, UCP and ACP
agent-ready.devAbout 15The 72-check list leaves out bot protection, the AI Catalog, WebMCP and CLIs
CloudflareAbout 11Does not test JavaScript-only content, status codes, JSON-LD or code fences
Mintlify Agent ScoreAbout 6Documentation only; nothing on act or pay
SiteSpeakAIAbout 4Four named areas; no check list is published
is-agentic.comSame checks as OraCapability checks count only in the 20-point Recommended pool when a site offers them

The Scanner Concordance shows how those differences play out on sixty real domains.

Sources

  1. AgentReady specification, v2.0. https://github.com/agentready-org/standard/blob/main/spec/spec.md, read 2026-11-04.
  2. AgentReady repository README. https://github.com/agentready-org/standard/blob/main/README.md, read 2026-11-04.
  3. AgentReady changelog. https://github.com/agentready-org/standard/blob/main/CHANGELOG.md, read 2026-11-04.
  4. Ora, AgentReady launch post. https://ora.ai/blog/agentready-launch, read 2026-11-04.
  5. Ora, check catalog (contract 1.38.0). https://ora.ai/api/checks, read 2026-11-04.
  6. Cloudflare, isitagentready.com llms.txt. https://isitagentready.com/llms.txt, read 2026-11-04.
  7. agent-ready.dev, methodology. https://agent-ready.dev/methodology, read 2026-11-04.
  8. SiteSpeakAI, AI Agent Readiness Scanner. https://sitespeak.ai/tools/ai-agent-readiness-scanner, read 2026-11-04.
  9. Mintlify, Agent Score. https://mintlify.com/blog/agent-score, read 2026-11-04.
  10. is-agentic.com, methodology. https://is-agentic.com/methodology, read 2026-11-04.

Last reviewed 2026-11-05