# Standards

> 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.

Source: https://agentrelations.org/standards

Last reviewed November 2026

Standards change fast. Dates and versions here come from the owners’ pages where we could read them. Where only trade press supports a claim, the page says “reported”. See the [changelog](https://agentrelations.org/standards/changelog).

## 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.

7 on the mapStable

### Stable

Finished or long established, with a named owner and wide use. Safe to build on.

10 on the mapEmerging

### Emerging

In real use and moving. Adopt it, but expect revisions and check the current version.

5 on the mapWatching

### 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.

[Stable

### 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

Read more →](https://agentrelations.org/standards/robots-txt)[Emerging

### Content Signals

Three yes or no lines in robots.txt: search, ai-input, ai-train.

Owner: Cloudflare (released CC0)

Read more →](https://agentrelations.org/standards/content-signals)[Watching

### 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

Read more →](https://agentrelations.org/standards/aipref)[Emerging

### llms.txt

A markdown summary of your site, at /llms.txt, written for models.

Owner: Community proposal by Jeremy Howard (September 2024)

Read more →](https://agentrelations.org/standards/llms-txt)[Emerging

### 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

Read more →](https://agentrelations.org/standards/markdown-pages)[Stable

### Sitemaps

The list of your pages and when each last changed.

Owner: sitemaps.org (Google, Microsoft, Yahoo)

Read more →](https://agentrelations.org/standards/sitemaps)[Stable

### 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)

Read more →](https://agentrelations.org/standards/product-feeds)[Stable

### Google Business Profile

The local listing (hours, places, reviews) that Maps, Search and AI Mode use.

Owner: Google

Read more →](https://agentrelations.org/standards/google-business-profile)[Watching

### NLWeb

A site answers natural-language questions from its own structured data.

Owner: Microsoft (MIT license)

Read more →](https://agentrelations.org/standards/nlweb)

## 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.

[Stable

### 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)

Read more →](https://agentrelations.org/standards/schema-org)[Stable

### 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)

Read more →](https://agentrelations.org/standards/openapi)

## 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.

[Emerging

### 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

Read more →](https://agentrelations.org/standards/mcp)[Emerging

### MCP server cards

A JSON file that describes a remote MCP server before anyone connects.

Owner: MCP project (SEP-2127)

Read more →](https://agentrelations.org/standards/mcp-server-cards)[Emerging

### 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

Read more →](https://agentrelations.org/standards/a2a)[Emerging

### 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)

Read more →](https://agentrelations.org/standards/agent-skills)

## 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.

[Emerging

### 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)

Read more →](https://agentrelations.org/standards/ucp)[Emerging

### ACP (Agentic Commerce Protocol)

OpenAI and Stripe’s specs for product feeds, agentic checkout and delegated payment.

Owner: OpenAI and Stripe (Apache 2.0)

Read more →](https://agentrelations.org/standards/acp)[Watching

### 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

Read more →](https://agentrelations.org/standards/ap2)[Watching

### 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

Read more →](https://agentrelations.org/standards/x402)

## 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.

[Emerging

### Web Bot Auth

An agent signs each request, and you verify who it is from its published keys.

Owner: IETF working group

Read more →](https://agentrelations.org/standards/web-bot-auth)[Stable

### 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

Read more →](https://agentrelations.org/standards/oauth-agents)[Watching

### 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)

Read more →](https://agentrelations.org/standards/know-your-agent)

## 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

Every vendor counts agent activity its own way. The Institute has drafted one, open for comment: [AR-1 Agent Activity Measurement](https://agentrelations.org/standards/proposals/activity-measurement).

## More from Standards

[### Proposals

The Institute’s own draft specifications, open for comment

Open →](https://agentrelations.org/standards/proposals)[### Open source

Reference tools and templates

Open →](https://agentrelations.org/standards/open-source)[### Changelog

What changed in agent standards

Open →](https://agentrelations.org/standards/changelog)

Standards change fast. Last reviewed November 2026.
