Glossary
In short
Forty terms the scanners and the AgentReady spec use, each with a plain definition and an example from a cited source. Terms run from agent readiness and initial HTML to Web Bot Auth, x402 and the Concordance itself. Every term has its own page with its source and read date.
All terms
- A2A agent card
- A JSON file, usually at /.well-known/agent-card.json, describing an agent's skills and endpoint for other agents. Ora's a2a-agent-card check is a 2-point bonus check.
- ACP
- Agentic Commerce Protocol: an Apache 2.0 standard for checkout between buyers, AI agents and merchants of record. Cloudflare's scanner checks for ACP under Commerce.
- Agent experience (AX)
- The agent-side counterpart of user experience: whether an agent on your site can find, read and use what it needs. Ora defines AX as whether the buyer's agent can find, read and check your site itself.
- Agent Experience Platform (AXP)
- Scrunch's product that detects agent traffic and serves agents a stripped, structured version of each page. Sitecore's acquisition release says AXP formats content for LLMs without changing the human experience.
- Agent readiness
- How well a site or product lets AI agents find it, read it, act on it and pay it, measured by checks against public URLs. Ora scores agent readiness 0 to 100 across Discovery, Access, Usability and Payments.
- Agent readiness scanner
- A tool that fetches a URL and its machine files and reports which agent-facing practices pass, usually as a score. isitagentready.com checks 23 standards across 5 categories.
- Agent Skills index
- A well-known file listing skill documents an agent can fetch to learn a task. isitagentready.com publishes a skill document for every standard it checks.
- Agentic Resource Discovery (ARD)
- A catalog format at /.well-known/ard.json plus a registry layer that indexes catalogs across sites. Ora's ard-catalog check was reweighted to 1 point in an August 2026 audit (from 3).
- AgentReady identifier
- A stable AR-* id for one requirement in the AgentReady spec, used to refer to it in tooling and conformance claims. AR-FIND-01 is the MUST to not block agent and crawler access in robots.txt or at the network layer.
- agents.json
- A Wildcard format built on OpenAPI that describes API flows an agent can chain. agent-ready.dev check C6 validates Wildcard agents.json.
- AI Catalog
- A JSON manifest at /.well-known/ai-catalog.json listing every agent-facing resource a site ships. AgentReady AR-FIND-04 marks publishing an AI Catalog as MAY.
- Answer engine optimization (AEO)
- Work aimed at what AI answers say about a brand, usually by tracking prompts and influencing the sources models cite. Profound runs structured prompts across AI platforms and tracks citations, sentiment and ranking.
- AP2
- Agent Payments Protocol: payment authorization through verifiable digital credentials, now at the FIDO Alliance. Google released AP2 v0.2 with Human Not Present payments when it announced the donation.
- API Catalog (RFC 9727)
- A well-known document at /.well-known/api-catalog listing a site's APIs and their specs. RFC 9727 defines the api-catalog well-known URI and link relation that help automated discovery of published APIs.
- auth.md
- A markdown file at /auth.md describing how agents get access to a service, from a WorkOS proposal. ora.ai/auth.md says reads are keyless and API keys are issued by email.
- Content Signals
- A Content-Signal line in robots.txt stating preferences for ai-train, ai-input and search. isitagentready.com's robots.txt sends Content-Signal: ai-train=yes, search=yes, ai-input=yes.
- Essentials score
- The alternate reading of an Ora scan in which required checks carry most of the weight; it is what is-agentic.com displays. is-agentic gives Essential checks an 80-point pool.
- HTTP Message Signatures
- RFC 9421, the IETF standard for signing parts of an HTTP message, used by Web Bot Auth. Ora publishes its keys at /.well-known/http-message-signatures-directory.
- Initial HTML
- The HTML a server returns before any JavaScript runs; plain-fetch agents only see this. AR-READ-01 requires the answer to be present in the initial HTML.
- Journey run
- A test in which a real AI agent attempts a set task on a site while each step is recorded. is-agentic.com says the observed journey is supporting evidence, not part of the numeric score, because one task cannot represent every agent, user goal or production condition.
- JSON-LD
- Structured data in a script block using schema.org vocabulary, readable by agents from raw HTML. Ora's json-ld check is worth up to 4 points in the Access layer.
- Leaderboard
- A ranked list of scanned domains by score and category. Ora's leaderboard rows carry rankDelta7d and scoreDelta7d.
- llms-full.txt
- A companion file holding a site's full text or documentation in one markdown file. ora.ai/llms-full.txt carries Ora's complete public documentation in one file.
- llms.txt
- A markdown file at /llms.txt that gives agents a short, linked index of a site. Ora links its llms.txt from the top of every page.
- Markdown content negotiation
- Serving a markdown version of a page at the same URL when the request sends Accept: text/markdown. Radar found 3.9 percent of top sites passed markdown negotiation.
- MCP Apps
- An MCP extension where a tool points to a ui:// resource that the host renders as a sandboxed view. AR-ACT-05 says products with a UI MAY ship an MCP Apps view.
- MCP server card
- A JSON description of an MCP server, published before connection so an agent knows its tools and auth. Cloudflare checks for a server card at /.well-known/mcp/server-card.json.
- Model Context Protocol (MCP)
- A JSON-RPC protocol through which AI hosts call tools, resources and prompts on external servers. Ora runs an MCP server at https://www.ora.ai/api/mcp with 18 tools.
- MUST, SHOULD, MAY
- The three strength levels in AgentReady: MUST for what an agent fails without, SHOULD for practices that changed agent behaviour, MAY for emerging conventions. AgentReady lists agent payments (AR-ACT-08) as MAY.
- NLWeb
- A Microsoft-originated protocol for an /ask endpoint that answers natural-language questions with schema.org results. ora.ai/ask serves NLWeb v0.55 with no credential.
- OAuth protected resource metadata
- OAuth metadata, published as an IETF RFC, that tells an agent which authorization server protects an API. AR-ACT-01 cites RFC 8414 and RFC 9728 for agent-completable auth.
- Plain fetch
- An HTTP client that downloads a page without running JavaScript, as most agent tools do. Ora's experiment probed each configuration with a plain fetch and a JavaScript-running client.
- robots.txt
- The file at a site root that tells crawlers which paths they may fetch, standardised in RFC 9309. Radar found 78 percent of the top 200,000 domains had a robots.txt.
- Scanner concordance
- This site's measure of how closely different scanners agree when they score the same domains on the same day. Two of the scanners, Ora and is-agentic, share one engine, which a concordance has to account for.
- Soft 404
- A missing page answered with HTTP 200, which agents cannot tell apart from a live page. AR-READ-02 forbids a 200 for a missing page.
- UCP
- Universal Commerce Protocol: building blocks for agentic commerce from discovery to checkout, with AP2 for payment mandates. UCP published a Lodging draft specification by November 2026.
- Vary: Accept
- A response header telling caches that the content differs by the Accept header, needed when one URL serves HTML and markdown. Cloudflare's markdown responses carry vary: accept.
- Web Bot Auth
- An IETF draft profile of HTTP Message Signatures that lets bots sign requests and publish verification keys. OraBot signs every request with an Ed25519 key under the Web Bot Auth profile.
- WebMCP
- A browser API, drafted in a W3C Community Group, letting a page register tools on document.modelContext for an in-page agent. AR-ACT-07 raised WebMCP to SHOULD in AgentReady v2.0.
- x402
- An open payment standard that uses HTTP 402 Payment Required so a client can pay per request and retry. The x402 Foundation launched under the Linux Foundation on 2 April 2026.
Sources
- Ora complete public documentation (llms-full.txt). https://ora.ai/llms-full.txt, read 2026-11-04.
- AX is the new AEO (Ora research, 2026-10-08). https://ora.ai/blog/ax-is-the-new-aeo, read 2026-11-04.
- Profound pricing. https://www.tryprofound.com/pricing, read 2026-11-04.
- isitagentready.com llms.txt. https://isitagentready.com/llms.txt, read 2026-11-04.
- AgentReady spec.md v2.0. https://github.com/agentready-org/standard/blob/main/spec/spec.md, read 2026-11-04.
- Introducing AgentReady.org (Ora blog, 2026-10-19). https://ora.ai/blog/agentready-launch, read 2026-11-04.
- Cloudflare: Introducing the Agent Readiness score (2026-04-17). https://blog.cloudflare.com/agent-readiness/, read 2026-11-04.
- Cloudflare Markdown for Agents docs. https://developers.cloudflare.com/fundamentals/reference/markdown-for-agents/, read 2026-11-04.
- Ora methodology page. https://ora.ai/methodology, read 2026-11-04.
- Ora check catalog /api/checks (contract 1.38.0). https://ora.ai/api/checks, read 2026-11-04.
- OraBot page. https://ora.ai/bot, read 2026-11-04.
- AgentReady CHANGELOG. https://github.com/agentready-org/standard/blob/main/CHANGELOG.md, read 2026-11-04.
- agent-ready.dev methodology. https://agent-ready.dev/methodology, read 2026-11-04.
- rfc-editor.org. https://www.rfc-editor.org/rfc/rfc9727.html, read 2026-11-05.
- Ora auth.md. https://ora.ai/auth.md, read 2026-11-04.
- Coinbase docs: x402 Foundation. https://docs.cdp.coinbase.com/x402/support/x402-foundation, read 2026-11-04.
- ucp.dev. https://ucp.dev/, read 2026-11-04.
- Google: donating AP2 to FIDO Alliance (2026-04-28). https://blog.google/products-and-platforms/platforms/google-pay/agent-payments-protocol-fido-alliance/, read 2026-11-04.
- is-agentic methodology. https://is-agentic.com/methodology, read 2026-11-04.
- is-agentic.com. https://is-agentic.com/, read 2026-11-04.
- We partnered with Vercel to launch is-agentic.com (2026-08-20). https://ora.ai/blog/is-agentic-with-vercel, read 2026-11-04.
- Sitecore press release: acquires Scrunch (2026-06-03). https://www.sitecore.com/de-de/company/newsroom/press-releases/2026/06/sitecore-acquires-scrunch-to-help-brands-influence-discovery--and-buying-decisions, read 2026-11-04.
Last reviewed 2026-11-05