ACP vs UCP vs AP2 vs MCP: agentic commerce protocols explained
- Type
- Applies to
- Medusa v2.x
- Updated
Short answer
ACP (OpenAI and Stripe) covers the product feed, checkout, and delegated payment for ChatGPT. UCP (Google, with Shopify and other retailers) covers catalog, checkout, and orders for Google AI Mode and Gemini. AP2 proves payment authorization. MCP connects AI apps to tools. Medusa has an official ACP guide; UCP and AP2 are custom.
What is an agentic commerce protocol?
An agentic commerce protocol (ACP) is a shared specification that lets AI agents find products, check out, or pay on a customer's behalf. It doesn't require a custom integration between the AI agent and the store.
When optimizing your store for AI agents, you'll find concepts like ACP, UCP, AP2, and MCP. Each of these cover a different way or layer of allowing an AI agent to make a purchase in your store.
This article explains each and the differences between them.
ACP vs UCP vs AP2 vs MCP at a glance
What is ACP?
The Agentic Commerce Protocol (ACP) is the protocol OpenAI uses for Instant Checkout in ChatGPT. It's created by Stripe and OpenAI, and it's published on agenticcommerce.dev as open source under Apache 2.0.
To support ACP in an ecommerce store, the store must implement the following flows:
- A product feed that ChatGPT can use to index the catalog.
- The Agentic Checkout Spec, which are REST endpoints like Copy to clipboard
POST /checkout_sessionsthat ChatGPT calls to create, update, and complete a checkout. - The Delegated Payment Spec, where a payment provider issues a scoped one-time token. Stripe's Shared Payment Token is the first implementation.
The ecommerce store handles processing payments and refunds with the payment providers it configures.
What is UCP?
The Universal Commerce Protocol (UCP) is an open standard that allows agents to discover, buy, and track orders across ecommerce stores. Google uses it for agentic checkout through AI Mode in Google Search and Gemini.
UCP supports REST and JSON-RPC to handle catalog, cart, checkout, orders, and more. It also supports identity linking through OAuth 2.0, and has built-in support for AP2 and MCP.
What is AP2?
The Agent Payments Protocol (AP2) is an open protocol that proves whether a buyer authorized a payment that an agent made. It's an extension of the Agent2Agent (A2A) protocol and UCP.
AP2 uses verifiable digital credentials called mandates:
- A checkout mandate records what the user approved for a purchase.
- A payment mandate authorizes a specific amount for that checkout, and goes to the credential provider and payment processor.
What is MCP?
The Model Context Protocol (MCP) is an open-source standard for connecting AI agents to a service or ecommerce store. These tools allow the agent to perform actions like searching for products, creating carts, and more.
MCP servers can be used by any MCP client. They're not specific to ecommerce stores, so there's no official spec for them. UCP and ACP both offer MCP as a transport, so MCP is often used to allow agents to consume these protocols.
How do the protocols fit together?
The protocols stack by layer rather than compete one-to-one:
- Discovery: an ACP product feed, UCP catalog capability, or MCP tools that allow agents to search the catalog of a store.
- Checkout: ACP checkout sessions or the UCP checkout capability that allow agents to checkout on the customer's behalf.
- Payment: the ACP Delegated Payment Spec, or AP2 mandates under UCP.
- Transport: REST, MCP, or A2A that agents use to perform the requests to the ecommerce store.
A store that wants to sell in both ChatGPT and Google AI Mode needs to implement ACP and UCP side by side. Both of them map onto the same cart, order, and payment logic in the backend.
Where does Medusa fit for each protocol?
Medusa is an AI-native open-source commerce platform whose cart, order, and payment modules can sit behind any of these protocols.
For ACP, Medusa has an official guide with example code that explains how to build the feed, the checkout session routes, and order webhooks.
UCP and AP2 have no Medusa guide yet, but you can build them as custom API routes and workflows.
When is Medusa not the right choice?
- You want agent checkout channels managed for you with no code. Shopify documents UCP-based agent tools for its merchants.
- You have no developer to implement and maintain protocol endpoints.
Common questions
Is ACP open source?
Yes. The Agentic Commerce Protocol is open source under the Apache 2.0 license, published at agenticcommerce.dev by Stripe and OpenAI.
Is UCP the same as AP2?
No. UCP defines catalog, cart, checkout, and order capabilities, while AP2 handles proof that the buyer authorized a payment. UCP uses AP2 for secure payment.
Do I need MCP to sell through AI agents?
Not necessarily. ChatGPT Instant Checkout uses ACP's REST endpoints, but UCP and ACP both support MCP as a transport, so an MCP server is one way to expose commerce tools to agents.
Does Medusa support UCP?
Medusa has no UCP guide or plugin today. You can implement UCP endpoints as custom API routes and workflows on top of Medusa's cart and order modules.