What Is Agentic Commerce? UCP, ACP, AP2, and x402 Explained
Agentic commerce explained: what UCP, ACP, AP2, MCP, and x402 each actually do, how they layer together, and why it isn't only a big-retailer story.
Long Nguyen
Founder · System Architect
What agentic commerce actually means
For twenty years, "who's shopping on your site" had one answer: a person. Then it got a second answer: a person using an AI assistant to research before buying. In 2026, a third shopper showed up — an AI agent that discovers a product, decides it fits the brief, and completes the purchase on a person's behalf, inside a chat window, without the person ever landing on your site.
Agentic commerce is the umbrella term for that shift: AI agents discovering, comparing, and transacting with businesses directly, using machine-readable protocols instead of a human clicking through a storefront. It's not one product or one company's feature — it's a stack of overlapping open standards that different platforms adopted through 2026, each solving a different layer of the same problem.
The protocols powering it: UCP, ACP, AP2, MCP, and x402
The names get thrown around as if they're competitors. They mostly aren't — they sit at different layers of the same stack, and a single agent-driven purchase can touch several of them at once.
| Protocol | Built by | What it standardizes | Status through 2026 |
|---|---|---|---|
| UCP (Universal Commerce Protocol) | Google + Shopify | The full commerce journey — discovery, cart, checkout, orders, post-purchase | Launched January 11, 2026 at NRF; expanded in March 2026 with cart and catalog access; powers Google's Universal Cart across Search AI Mode, Gemini, YouTube, and Gmail since I/O 2026 |
| ACP (Agentic Commerce Protocol) | OpenAI + Stripe | The in-chat checkout handshake and merchant product feeds | Announced September 29, 2025; powered ChatGPT's native Instant Checkout, which OpenAI wound down on March 24, 2026 in favor of product-discovery feeds; ACP now runs over MCP as a transport |
| AP2 (Agent Payments Protocol) | Originated at Google | Cryptographic proof that a shopper actually authorized the agent's spend (signed Intent, Cart, and Payment mandates) | Donated to the FIDO Alliance on April 28, 2026; designed to work alongside UCP and other checkout layers, not to replace them |
| MCP (Model Context Protocol) | Anthropic, now Linux Foundation-governed | The general-purpose layer agents use to read data and call tools on a site or service | The transport layer several of the commerce-specific protocols above are built to run over |
| x402 | Coinbase + Cloudflare (x402 Foundation) | Machine-to-machine micropayments over HTTP, using the long-dormant HTTP 402 status code | Under Linux Foundation stewardship since April 2026, with AWS, Cloudflare, and Anthropic as members; adoption running into the hundreds of millions of transactions in its first year, mostly for pay-per-call API and data access rather than shopping carts |
The practical mental model: UCP and ACP answer "how does an agent discover and check out," AP2 answers "who authorized this spend," MCP answers "how does the agent talk to your systems at all," and x402 answers a narrower, adjacent question — "how does an agent pay for a single API call or a piece of paid content," which matters even for sites that aren't running a storefront.
This isn't only a big-retailer story
UCP and ACP get covered as retail-platform news because the launch partners are the names you'd expect — Shopify, Walmart, Etsy, Best Buy. That coverage misses the part that matters for most website owners: those two protocols are the heavyweight path, built for merchants integrating with Google's and OpenAI's shopping surfaces at scale through Merchant Center or a platform-native app.
There's a second, much lighter path that has nothing to do with Merchant Center feeds: making your own site legible and actionable to the agents that visit it directly — a browsing assistant fetching your pages, a research agent comparing you against competitors, a user's assistant filling out your contact form. That layer is built from the same underlying primitives (MCP, structured data, machine-readable discovery) without requiring you to become a UCP-registered merchant. It's the layer that applies whether you run a 500-SKU storefront or a two-person service business with a contact form and a quote request.
We rebuilt Netalith's own site around exactly that lighter layer rather than waiting for a Merchant Center integration that doesn't fit a service business — the specifics are worth its own walkthrough, which we cover in how to integrate agentic commerce into a website.
What this means for how you think about your website
The concrete shift is this: your website now has two audiences reading it — a human deciding whether to trust you, and an agent deciding whether it can transact with you at all. A page can be excellent for the first audience and completely illegible to the second if there's no structured way for an agent to confirm your prices, availability, service scope, or how to actually submit a request. Schema markup (covered in our ecommerce schema guide) gets you halfway there — it makes your site readable. Agentic commerce, in its lighter form, is about the other half: making your site actionable.
None of this is a reason to rebuild your site this quarter. It's a reason to know where the discovery, data, and action layers sit on your roadmap, and to build them in that order rather than chasing checkout-protocol headlines before an agent can even reliably find and read your pages. If you want a second opinion on where your site currently sits, our SEO/AEO/GEO service covers this exact stack.