Standards
The Standards Map
22 standards and conventions that decide how agents find, read, talk to, pay and trust an organization. Each has an owner, a maturity and a plain explanation.
Last reviewed November 2026
How to read this map
The map follows the Framework’s six domains. Within each, a card gives the standard’s name, what it does, who owns it and where it stands.
Stable
Finished or long established, with a named owner and wide use. Safe to build on.
Emerging
In real use and moving. Adopt it, but expect revisions and check the current version.
Watching
Early, unsettled or lightly used. We track it and do not yet advise building on it.
The Institute decides these labels, with practitioners’ input. A standard can move in either direction.
Discover: Be found
Agents can reach you wherever they look: your site, directories, feeds, marketplaces and the assistants people already use.
robots.txt rules for AI agents
A file that says which crawlers and agents may fetch which pages.
Owner: IETF (RFC 9309); the agent names belong to each AI provider
Content Signals
Three yes or no lines in robots.txt: search, ai-input, ai-train.
Owner: Cloudflare (released CC0)
IETF AI preferences (aipref)
A shared vocabulary for how content may be used by AI, in a header or robots.txt.
Owner: IETF aipref working group
llms.txt
A markdown summary of your site, at /llms.txt, written for models.
Owner: Community proposal by Jeremy Howard (September 2024)
Markdown versions of pages
Every page also available as clean markdown, by URL or request header.
Owner: A convention, used by Cloudflare, Vercel and documentation platforms
Sitemaps
The list of your pages and when each last changed.
Owner: sitemaps.org (Google, Microsoft, Yahoo)
Product feeds for agents
Your catalog in a form shopping assistants load: Google Merchant Center, OpenAI’s feed.
Owner: Google (Merchant API) and OpenAI (product feed, part of the Agentic Commerce Protocol)
Google Business Profile
The local listing (hours, places, reviews) that Maps, Search and AI Mode use.
Owner: Google
NLWeb
A site answers natural-language questions from its own structured data.
Owner: Microsoft (MIT license)
Describe: Be understood
What you are, what you offer and on what terms, written so a machine reads it correctly and a person would recognize it.
schema.org JSON-LD (including potentialAction)
Typed facts hidden in the page: organization, product, offer, job, event and actions.
Owner: schema.org (founded by Google, Microsoft, Yahoo and Yandex)
OpenAPI and the API catalog
A machine-readable description of your API, and a list of your APIs at a known address.
Owner: OpenAPI Initiative (versions 3.1 and 3.2); RFC 9727 (IETF, June 2025)
Converse: Be asked
Agents can ask you questions and get fast, accurate answers, with a clear path to a person when an answer needs one.
MCP (Model Context Protocol)
How an agent calls your tools, reads your resources and uses your prompts.
Owner: Created by Anthropic; given to the Linux Foundation’s Agentic AI Foundation in December 2025
MCP server cards
A JSON file that describes a remote MCP server before anyone connects.
Owner: MCP project (SEP-2127)
A2A (Agent2Agent) and agent cards
How one agent hands a task or a message to another, with a card describing each.
Owner: Created by Google; given to the Linux Foundation in June 2025
Agent Skills (SKILL.md)
A folder with a SKILL.md that an agent loads when the task fits.
Owner: Format by Anthropic, an open standard since late 2025; the discovery index is a Cloudflare-led draft (v0.2.0)
Transact: Be chosen
Agents can act, not just read: book, buy, apply, request a quote or join, through actions you define and rails you trust.
UCP (Universal Commerce Protocol)
One protocol for catalog, cart, checkout and orders, with the business as merchant of record.
Owner: Google, with Shopify, Etsy, Wayfair, Target, Walmart and Stripe (Apache 2.0)
ACP (Agentic Commerce Protocol)
OpenAI and Stripe’s specs for product feeds, agentic checkout and delegated payment.
Owner: OpenAI and Stripe (Apache 2.0)
AP2 (Agent Payments Protocol)
Signed mandates that prove what the person approved before an agent pays.
Owner: Google; reported moved to the FIDO Alliance with Verifiable Intent in April 2026
x402
HTTP 402 Payment Required, with a stablecoin payment in the retry: pay per call, no account.
Owner: Coinbase and Cloudflare (May 2025); reported moved to an x402 Foundation at the Linux Foundation in 2026
Trust: Be trusted
You know which agents you deal with and they know who you are: identity, permissions, policies for agents and honesty toward the people behind them.
Web Bot Auth
An agent signs each request, and you verify who it is from its published keys.
Owner: IETF working group
OAuth for agents (MCP authorization, client ID metadata documents)
How an agent gets permission to act on a person’s account.
Owner: IETF RFCs and the MCP specification
Know Your Agent (KYA)
A label for checking who built and runs an agent. A name, not a standard.
Owner: No owner. Vendors’ products, 2025 to 2026 (examples: Skyfire, Trulioo, Sumsub, Mastercard)
Measure: Know the score
You see what agents do with you: visits, questions, actions, failed tasks and the outcomes they lead to, counted the same way everywhere.
No shared standard yet
More from Standards
Standards change fast. Last reviewed November 2026.