Agentic commerce

UCP vs ACP vs MCP: which agentic-commerce rails matter for your business?

Three protocols now decide whether AI agents can find your business and pay you. Here is what each one actually does, who runs it, what it costs you to support, and the honest order to adopt them in.

Updated August 20, 2026 · 9 min read

If you sell anything online, three acronyms started crowding your feeds over the past year: ACP, UCP, and MCP. They sound interchangeable. They are not, and the differences decide which AI surfaces can discover your business, which can book or buy from you, and how much engineering each one demands.

The stakes stopped being theoretical a while ago. Salesforce reported that AI influenced $262 billion of online sales during the 2025 holiday season, and every major assistant now ships some form of shopping. This guide defines each protocol in plain English, compares them side by side, and ends with an honest decision guide.

Three protocols, three different jobs

Here is the shortest accurate version. ACP is the open checkout specification OpenAI and Stripe published, now maintained as a standard with adopters including PayPal and Stripe, though the ChatGPT surface it launched with is gone. UCP is Google’s commerce protocol: it connects your catalog and checkout to Gemini and Google’s AI shopping surfaces, onboarded through Merchant Center, and it is where live agentic checkout actually happens in 2026. MCP is the general-purpose tool protocol: it is how agents call any external capability at all, and commerce actions like searching listings or starting a booking are just one use of it.

A useful mental model: UCP is a sales channel with a spec attached. ACP is a specification looking for surfaces after losing its original one. MCP is plumbing. Confusing them is easy because all three landed within about fourteen months of each other, but they solve different problems and you evaluate them differently.

ACP: the open checkout spec that outlived its launch surface

OpenAI and Stripe published the Agentic Commerce Protocol as an open spec in September 2025 under Apache 2.0, and it powered Instant Checkout in ChatGPT. Etsy sellers were the launch cohort, with a small group of Shopify merchants following. Then OpenAI retired in-chat checkout on March 4, 2026, roughly five months later, after Walmart and others found that checkout inside the assistant converted far worse than sending buyers to their own sites.

The protocol did not go with it. ACP has two halves: a product feed that lets agents discover and compare your items, and a checkout API (checkout sessions) that you or your platform host, with payment handled through a delegated token so raw card details never touch your servers. The feed half transfers cleanly to other surfaces because structured product data is the shared input everywhere. The checkout half now pays off only where something you use actually speaks ACP, which today means PayPal, Stripe’s Agentic Commerce Suite, or a platform that implements it.

Status as of August 2026: the specification is active, with a stable revision dated April 17, 2026 covering checkout, payment delegation, cart, feed, orders, authentication, and integration with MCP. That convergence with MCP is the strongest signal about where it is heading. The practical detail is in our ACP guide.

UCP: Google’s commerce protocol for Gemini and Search

Google introduced the Universal Commerce Protocol at NRF in January 2026 as the standard way its AI surfaces talk to merchants, co-developed with Shopify, Etsy, Wayfair, Target, and Walmart. The front door is Google Merchant Center: your catalog data flows in the way Shopping feeds always have, and UCP layers agent-facing capabilities on top so Gemini, AI Mode in Search, and YouTube Shopping can move from recommending a product to transacting for it.

The design choice worth noticing is that UCP is transport-flexible. The same commerce capabilities can be served over a plain REST API, over MCP, or over A2A, Google’s agent-to-agent protocol. Payments compose with AP2, the Agent Payments Protocol Google published in September 2025 with a long roster of payments partners; AP2 handles the "did a human actually authorize this purchase" mandate so an agent cannot spend without provable consent.

Status as of August 2026: this is the live agentic checkout rail with real distribution behind it. Shopify enabled Agentic Storefronts by default in its Winter 2026 Edition, activating UCP for its merchants without per-merchant integration work. If you already maintain a Merchant Center feed for Shopping ads, you are much closer to UCP-ready than you probably think. The merchant-side detail is in what is Google UCP.

MCP: the protocol agents use to actually do things

The Model Context Protocol is the odd one out because it was never a commerce spec. Anthropic released it as an open standard in November 2024 to give AI models one uniform way to call external tools. OpenAI adopted it in March 2025, Google followed, and it is now the closest thing agents have to a USB port. The spec and ecosystem live at modelcontextprotocol.io.

For a merchant, MCP means exposing your business as callable tools: search my offers, check availability, book an appointment, start a checkout. Any MCP-capable agent can then act against your business directly instead of scraping your website and guessing. That includes Claude, ChatGPT’s developer mode, and the long tail of custom agents companies are building internally, which is a market no feed reaches.

There is also a distribution angle people miss. MCP servers are listed in the official MCP registry and mirrored across directories like Smithery and mcp.so, so a listed server is discoverable by agent builders in a way a private API never was. And because both UCP and the current ACP spec accept or integrate MCP, a well-built commerce MCP server is not a dead end; it is a component the bigger rails reuse.

Side by side: who runs what, and what it takes

One caveat, and March 2026 is the proof of it: "status" in this space has a shelf life measured in months. Treat the August 2026 column as a snapshot, not a prediction.

Where they overlap, and where they compose

These are not three competitors fighting for one socket. UCP explicitly supports MCP as a transport, so the "Google protocol" can literally run over the "Anthropic protocol," and the current ACP spec integrates MCP too. ACP’s product feed is a close cousin of the Merchant Center feed, close enough that one well-structured catalog generates both. And AP2 is a payments layer, not a rival channel; it can sit underneath more than one of these rails.

The deeper overlap is the substrate. All three assume your business data exists in structured, machine-readable form, and an agent that discovers you through any protocol still cross-checks your actual website before recommending you. Schema.org JSON-LD, clean crawlable HTML, and conventions like llms.txt remain the common denominator underneath every rail; we cover that layer in what llms.txt actually does.

In practice the protocols compose per buyer, not per merchant. One customer’s agent finds you through Gemini, another arrives from a ChatGPT recommendation and buys on your own site, a third books through a custom concierge agent hitting your MCP server. Same catalog, three doors. The winners stopped asking which door and started keeping one catalog behind all of them.

Which should you support first? The honest answer

None of them, at first. The bulk of agent traffic in 2026 is still a model reading your web pages, so structured data and crawlability pay off before any protocol does, and every protocol either consumes that same catalog data or verifies against it. Be honest about the fads too: Ahrefs found no ranking correlation for llms.txt and Google’s guidance says it is not required, so treat that file as a cheap courtesy, not a strategy. The JSON-LD and clean markup underneath it are the part that compounds.

1. Fix the substrate. Every offer or service gets schema.org JSON-LD, a crawlable HTML page, and accurate prices and availability. Verify with a free agent-legibility scan rather than assuming.
2. Win discovery everywhere before transacting anywhere. Being findable and accurately described is the ungated half on every rail, and with ChatGPT checkout gone it is the entire opportunity on that surface.
3. Follow your buyers for the transactional layer. If you sell products, UCP is where live agentic checkout is in 2026, and Merchant Center is the shortest path in. If your buyers are businesses or agent builders, an MCP server reaches them all. Add ACP checkout when a platform or payment provider you use requires it.
4. Watch your referrers and let data pick your next move. Agent traffic shows up in server logs and analytics in odd shapes; two months of real evidence beats any punditry, including this article. The measurement guide covers how.

If you run a service business, one more honest note: ACP and UCP grew up around physical products. Their feeds model SKUs, shipping, and returns, and bookable services fit awkwardly today. If you sell appointments, consults, or classes, an MCP server wired to real availability plus a normal Stripe checkout will beat waiting for the feed specs to catch up; we wrote up how that flow works end to end in how AI agents book service businesses.

The compounding move: one catalog, every rail

If maintaining a product feed, a checkout API, an MCP server, and structured markup sounds like a lot, that is the actual argument for a hosted layer. Nexez publishes each listing simultaneously as a human web page, JSON-LD, agent.json, llms.txt, an OpenAPI spec, and a per-merchant MCP server listed in the official registry, plus ACP and UCP feeds generated from the same core. Buyers pay through hosted Stripe checkout with you as merchant of record, including Calendly-backed scheduling for bookable services.

You keep your own website and your own Stripe account as merchant of record. The protocols become output formats of one catalog instead of four separate projects, which is exactly the shape this market rewards while the specs keep moving.