Agentic Commerce Protocols
For AI agents to transact with online stores, shared standards are essential. Currently, five protocols define the rules of Agentic Commerce — each with a different focus and different initiators.
Why Does Agentic Commerce Need Protocols?
Without standardized protocols, every AI agent would need to build a custom integration for every online store. With millions of stores and dozens of agents, that does not scale. Protocols solve this problem by defining a common language — for product data, checkout, payment, and communication.
The analogy to the web: HTTP, HTML, and URLs are the protocols that made the World Wide Web possible. Without them, every website would be an isolated system. Agentic Commerce needs its own protocol layer — and that layer is being built right now.
ACP — Agentic Commerce Protocol
Agentic Commerce Protocol
The open standard for checkout and payment in chat. ACP defines how AI agents discover products, create shopping carts, and complete purchases via tokenized payments.
- Focus: Checkout & Payment
- Status: Beta, live in ChatGPT
- License: Apache 2.0 (Open Source)
UCP — Universal Commerce Protocol
Universal Commerce Protocol
The most comprehensive protocol: UCP covers the entire commerce lifecycle — from product discovery through identity linking and checkout to post-purchase management.
- Focus: Full Commerce Lifecycle
- Status: Beta
- License: Open
AP2 — Agent Payments Protocol
Agent Payments Protocol
A universal payment framework for AI agents. AP2 uses digitally signed "Mandates" — authorizations that define what an agent is allowed to spend.
- Focus: Universal Payment
- Status: Beta
- License: Open
MCP — Model Context Protocol
Model Context Protocol
The infrastructure layer: MCP connects AI models with external tools and data sources — the "USB port for AI." Not a commerce protocol per se, but the foundation on which commerce takes place.
- Focus: AI-Tool Communication
- Status: Production, broad adoption
- License: Open Source
x402 / mpp — Micropayment Protocols
Micropayment Protocols
For the machine-to-machine economy: x402 uses the HTTP status code 402 to embed payments in HTTP requests. Payment via stablecoins (USDC). Ideal for API access and digital content.
- Focus: Micropayments, M2M
- Status: Early
- License: Open
Comparison
| Eigenschaft | ACP | UCP | AP2 |
|---|---|---|---|
| Initiator | OpenAI + Stripe | Google + Shopify | Google + Mastercard |
| Fokus | Checkout & Payment | Full Lifecycle | Universal Payment |
| Lizenz | Apache 2.0 | Offen | Offen |
| Status | Beta | Beta | Beta |
| Erste Impl. | ChatGPT | Google Search | Google Wallet |
A detailed comparison with recommendations can be found on the ACP vs. UCP vs. AP2 page.
Frequently Asked Questions
Which protocol is the most important?
That depends on the context. For checkout and payment, ACP is currently the most advanced. For the entire commerce lifecycle, UCP offers the broadest scope. AP2 leads on the payment layer. MCP is the universal infrastructure underneath.
Do merchants need to implement all protocols?
No. Start with the protocol that matches your primary sales channel — ACP for ChatGPT, UCP for Google. A multi-protocol strategy makes sense long-term but is not immediately necessary.
Are the protocols compatible with each other?
Partially. UCP is compatible with MCP and AP2. ACP can be delivered via MCP servers. The protocols complement rather than compete with each other — similar to HTTP, OAuth, and JSON on the web.