Short answer
Agentic commerce protocols are open standards that each handle one step of an AI agent's visit or purchase. llms.txt and MCP help agents read and use your site, A2A lets agents work with other agents, UCP and ACP run checkout, AP2 proves a person approved the payment, x402 handles pay-per-request payments, Web Bot Auth proves which agent is calling, and PAP lets a shopper's personal agent say who it acts for.
Key takeaways
- Each protocol handles one layer: tools, agents, checkout, payment or identity.
- UCP and ACP run checkout; AP2 proves the shopper approved it.
- x402 is for paying per request, not for a cart of goods.
What are agentic commerce protocols?
Agentic commerce protocols are open standards that let an AI agent find a business, work with it, buy from it, pay, and prove who it is. No single protocol does all of that. Each one handles one job, and they stack together like layers.
Here is the whole picture, from first contact to payment:
- Discovery and tools: llms.txt and MCP help an agent understand your site and use what it offers.
- Agent to agent: A2A lets one AI agent find and work with another.
- Checkout: UCP and ACP give an agent a standard way to build an order and check out.
- Payment authorisation: AP2, and the card networks' own agent programs, prove that a person approved the purchase.
- Pay per request: x402 lets an agent pay for a single page or API call.
- Identity: Web Bot Auth lets an agent sign its requests so you can check who sent them, and PAP lets a shopper's personal agent say who it is and who it acts for.
Eight standards sounds like a lot, and a newer one, PAP, makes nine. Most stores deal with only two or three directly, and often through their platform or payment provider rather than their own code. This guide explains what each layer is for, so you can tell which ones matter to you. For the idea behind all of them, see what agentic commerce is.
How do AI agents find your site and talk to it?
Three standards cover this layer: llms.txt for reading, MCP for using tools, and A2A for working with other agents.
llms.txt is a proposed standard for a plain Markdown file at /llms.txt. It gives AI tools a short, curated overview of your site, with links to the pages worth reading. It can also sit in a subfolder, such as /docs/llms.txt, to cover just that section. It is a map, not a set of actions: an agent reads it, then decides where to go.
MCP (Model Context Protocol) is an open-source standard for connecting AI applications to outside systems. Its own documentation compares it to a USB-C port for AI. Through MCP, apps such as Claude or ChatGPT can connect to data sources and tools and carry out tasks.
For a website, an MCP server is how you give an agent real actions instead of pages to scrape. A store might offer tools such as "search products" or "check stock". The agent calls the tool and gets structured data back, rather than guessing from your page layout.
A2A (Agent2Agent) is an open standard that lets AI agents discover, communicate and transact with each other across different frameworks. Google originally developed it, and the Linux Foundation now hosts it. In April 2026 the Linux Foundation said A2A had reached v1.0, its first stable specification, with more than 150 organisations supporting it. Version 1.0 added signed Agent Cards, so an agent's identity can be checked cryptographically.
The difference between MCP and A2A is who is on the other end. MCP connects an agent to tools and data. A2A connects an agent to another agent with its own skills. For most store owners, A2A works in the background, as one of the ways a platform or a checkout protocol connects.
Which protocols handle agent checkout?
UCP and ACP are the two open checkout standards. Both let an agent build an order and pay on a store without a custom integration for every shop. They overlap, and both are still changing.
UCP (Universal Commerce Protocol) covers the whole shopping journey: catalog, cart, checkout, identity linking and orders. Google and Shopify launched it in January 2026. Its site now lists shopping co-developers including Google, Shopify, Etsy, Wayfair, Target, Walmart, Amazon, Microsoft, Meta, Salesforce and Stripe. The business stays the merchant of record. UCP runs over REST and JSON-RPC, supports MCP and A2A, and is designed to work with AP2 for payment authorisation.
We explain how it works, and how it reaches shoppers in Google's AI Mode and Gemini, in what UCP is.
ACP (Agentic Commerce Protocol) is an open standard for connecting buyers, their AI agents and businesses. OpenAI and Stripe are its founding maintainers, Meta joined them as a maintainer in April 2026, it is under the Apache 2.0 licence, and the project describes itself as in beta. Its latest stable version, dated 2026-04-17, adds cart, product feed, orders, authentication and MCP to the earlier checkout and delegated payment specs.
The practical difference is who backs them. UCP is the standard Google uses for checkout in AI Mode in Search and the Gemini app, and it lists a long set of retailers and platforms as co-developers. ACP is maintained by OpenAI, Stripe and Meta. For a side-by-side look at how each one handles payment, see our comparison of ACP, AP2, UCP and x402.
How do agents prove a person approved the payment?
AP2 (Agent Payments Protocol) handles this. It gives an agent's purchase signed proof of what the person authorised, so a checkout does not have to take the agent's word for it.
Google developed AP2 with payments and technology companies, and in April 2026 contributed it to the FIDO Alliance. FIDO describes AP2 as introducing "a model for secure delegation, verifiable authorization and trusted transaction execution."
The key idea is the mandate: a signed record of what a person asked for and approved, such as a budget or an exact cart. A checkout can check the mandate before it accepts an order. For a plain explanation, see what an agent mandate is.
AP2 is not a checkout on its own. UCP is designed to work with it, so some stores will meet AP2 through a UCP integration rather than as a separate project.
Card networks are working on the same problem:
- Mastercard contributed its Verifiable Intent framework to the FIDO Alliance at the same time as AP2. It was co-developed with Google and is designed to work with AP2.
- FIDO's Payments Technical Working Group, chaired by members from Mastercard and Visa, is developing specifications for agent-initiated commerce.
- Visa and Mastercard's agent programs also lean on the identity layer. Cloudflare reported in October 2025 that Visa's Trusted Agent Protocol and Mastercard's Agent Pay both use Web Bot Auth to authenticate agents, and that American Express planned to do the same.
What is x402 for?
x402 lets an agent pay for a single request, such as one API call or one report, without an account or a checkout page. It solves a different problem from store checkout.
The flow is short:
- The agent asks for a paid resource.
- Your server replies with HTTP status 402 Payment Required and the payment details.
- The agent pays and sends the request again with proof of payment.
- A service called a facilitator verifies and settles the payment, and your server returns the content.
GET /paid HTTP/1.1
HTTP/1.1 402 Payment Required
payment-required: <price and accepted networks>
Stripe's documentation shows x402 payments settling in USDC, a stablecoin, on networks including Base, and recorded in Stripe as normal payments. Coinbase started x402. In July 2026 the Linux Foundation announced that the x402 Foundation was up and running under its governance.
x402 fits APIs, data and digital content better than a cart of physical goods. If you sell products, you are more likely to meet UCP or ACP first.
How does a site know which agent is calling?
Web Bot Auth lets an agent sign each request so your site can check who sent it. The agent signs with a private key. Your site, or your CDN, checks the signature against a public key that the agent's operator publishes.
It builds on HTTP Message Signatures (RFC 9421). It is being written at the IETF as a working-group Internet-Draft, so it is not a finished standard yet. The current draft defines a Signature-Agent header that tells your site where to find the agent's public keys.
This identity layer sits under everything else. A checkout protocol tells you what an agent wants to buy. Web Bot Auth tells you which agent is asking. A name in a user agent string proves nothing, because anyone can copy it. A valid signature is much harder to fake.
For the full walkthrough, read how signed agent requests work.
PAP (Personal Agent Protocol, also called Poppy) adds who the agent is acting for. Meta and Sierra are developing it, and version 1.0 was published in November 2026. A store publishes a file at /.well-known/poppy.json, and a shopper's personal agent signs each request to the store's APIs and agent with a session header that names the session and a per-store ID for the shopper. The agent can start as a guest and, if the shopper signs in on the store's own page, act on their account within the access they approve. PAP carries no payment: for checkout it hands off to UCP. See what PAP is.
Which protocols does your store actually need?
Most online stores need a checkout standard (usually through their platform), a way to verify agents, and the basic discovery files. The rest depends on what you sell.
| Protocol | Layer | What it does | Led by | Does a typical store need it? |
|---|---|---|---|---|
| llms.txt | Discovery | A Markdown map of your site for AI tools | Community proposal | Useful and low effort |
| MCP | Tools | Lets AI apps call your tools and read your data | Open-source project | Useful if you want agents to search or act, not scrape |
| A2A | Agent to agent | Lets agents discover and work with each other | Linux Foundation (from Google) | Mostly handled by platforms |
| UCP | Checkout | Catalog, cart, checkout, identity linking and orders | Google, Shopify and co-developers | The first checkout standard to look at for physical goods |
| ACP | Checkout | Agent checkout and delegated payment | OpenAI, Stripe and Meta | Check where it stands in ChatGPT before you plan around it |
| AP2 | Payment authorisation | Signed mandates showing what the person approved | FIDO Alliance (from Google) | May arrive through UCP |
| x402 | Pay per request | Pay for one request with HTTP 402 | x402 Foundation (from Coinbase) | Only if you charge for APIs, data or content |
| Web Bot Auth | Identity | Signed requests that prove which agent is calling | IETF working group | Yes, through your CDN or a plugin |
| PAP | Identity and sessions | A personal agent identifies itself and who it acts for, as a guest or signed in | Meta and Sierra | Worth checking; Sierra says Shopify stores publish it automatically |
A sensible order for a store:
- Publish llms.txt and keep your product data clean, so agents can read you.
- Verify agents where you can, so you know who is calling.
- Pick one checkout route, usually the one your platform or payment provider already supports.
- Ignore x402 unless you sell access to content or APIs.
How Sill helps. Sill publishes the files agents read (llms.txt, an agent card, an MCP server, a catalog) and keeps them current. It serves MCP, A2A, AP2 mandates, UCP checkout on sites with a connected Stripe account, PAP 1.0 guest sessions (no shopper sign-in), and llms.txt. ACP is built but not enabled, and x402 is not supported. Sill verifies signed agent requests (Web Bot Auth) on Cloudflare and WordPress installs, and when an agent places an order, your rules approve it, decline it or hold it for a person, with every decision signed and recorded. You can see where your site stands with a free readiness scan.
Questions people ask
What is the difference between MCP and A2A?
MCP connects an AI application to tools and data, such as a product search. A2A connects one AI agent to another agent that has its own skills. They solve different problems and are often used together.
Are these agentic commerce protocols official standards yet?
They are at different stages. A2A reached a stable v1.0 under the Linux Foundation, ACP describes itself as in beta, AP2 is being developed in the FIDO Alliance, and Web Bot Auth is still an IETF draft.
Do I have to build these protocols myself?
Usually not. Most stores get checkout and payment protocols through their ecommerce platform or payment provider. Check what yours already supports before you build anything.
Does UCP replace ACP?
No. Both are open checkout standards with different backers, and both are still being developed. A store may meet one, both or neither, depending on its platform and the AI apps its customers use.
Sources
- Model Context Protocol: What is MCP? · checked 16 Nov 2026
- Linux Foundation: A2A protocol surpasses 150 organizations in its first year · checked 16 Nov 2026
- Universal Commerce Protocol (UCP) · checked 16 Nov 2026
- Agentic Commerce Protocol on GitHub · checked 16 Nov 2026
- FIDO Alliance: developing standards for trusted AI agent interactions · checked 16 Nov 2026
- Stripe Docs: x402 · checked 16 Nov 2026
- Linux Foundation: operational launch of the x402 Foundation · checked 16 Nov 2026
- IETF: draft-ietf-webbotauth-httpsig-protocol · checked 16 Nov 2026
- Personal Agent Protocol: Specification (version 1.0) · checked 16 Nov 2026
- Sierra: Releasing Personal Agent Protocol 1.0 · checked 16 Nov 2026
- ACP maintainers · checked 17 Nov 2026
- Stripe Docs: Agentic Commerce Protocol · checked 17 Nov 2026