What Is Universal Commerce Protocol (UCP)? May 2026
What Is Universal Commerce Protocol (UCP)? May 2026
UCP is the open standard for agentic commerce — letting AI agents buy across retailers without bespoke integrations per platform. Co-developed by Google and major retailers, detailed at Google I/O 2026 on May 19, 2026, and now powering native checkout in Search and the Gemini app.
Last verified: May 19, 2026
Quick facts
| Property | Value |
|---|---|
| What | Open protocol for agentic commerce |
| Co-developed by | Google + Shopify + Etsy + Wayfair + Target + Walmart |
| Endorsed by | Adyen, AmEx, Best Buy, Flipkart, Macy’s, Mastercard, Stripe, The Home Depot, Visa, Zalando, others |
| Built on | REST + JSON-RPC |
| Works with | MCP (tools), A2A (agent-to-agent), AP2 (payments) |
| First reference implementation | Google AI Mode + Gemini app native checkout |
| Spec home | ucp.dev |
| Initial focus | Checkout, Identity Linking, Order Management |
What UCP actually does
UCP defines a common language for AI agents, retailers, and payment providers across the shopping journey. Without UCP, every agent has to build a bespoke integration per retailer — that’s the same problem MCP solved for tools and A2A for agent messaging.
Three initial pillars:
- Checkout — agent can complete a purchase against a retailer’s cart and order API without custom code.
- Identity Linking — link a user’s identity at the retailer to the agent context, with consent.
- Order Management — track, modify, return, refund — all through the same protocol.
How it fits in the agentic protocol stack (May 2026)
| Layer | Protocol | What it does |
|---|---|---|
| Tools / data | MCP (Model Context Protocol) | Agent accesses tools and data sources |
| Agent-to-agent | A2A (Agent2Agent) | Agents discover and message each other |
| Payments | AP2 (Agent Payments Protocol) | Secure agent-initiated payment authorization |
| Commerce | UCP (Universal Commerce Protocol) | Discovery, checkout, identity, orders across retailers |
UCP sits at the commerce layer and uses MCP, A2A, and AP2 as primitives. They’re complementary; UCP doesn’t replace them.
What users get
| Surface | Feature | What UCP enables |
|---|---|---|
| AI Mode in Google Search | Native Checkout | Buy directly inside AI Mode, no redirect |
| Gemini app | Native Checkout | Buy inside Gemini conversation |
| Google Search | Business Agent | Chat with eligible US retailers as a virtual sales associate |
| AI Mode | Direct Offers | Personalized discounts shown in-result |
| Any UCP-compliant agent | Cross-retailer cart | One agent, many retailers, no per-merchant code |
What retailers get
- Multi-agent reach — be present in AI Mode, Gemini, ChatGPT (if it adopts UCP), and any future agent surface with one integration.
- Merchant of Record control — retailers keep customer relationships and business logic; UCP doesn’t disintermediate them.
- Lower abandonment — Native Checkout eliminates the redirect that loses carts.
- Standard plumbing — REST + JSON-RPC, with reference implementations.
Who’s on board (May 2026)
Co-developers / adopters: Shopify, Etsy, Wayfair, Target, Walmart.
Endorsers / payment partners: Adyen, American Express, Best Buy, Flipkart, Macy’s, Mastercard, Stripe, The Home Depot, Visa, Zalando — and more than 20 additional global partners.
That’s enough scale that UCP is the de facto agentic-commerce protocol at launch.
How UCP compares (and how to think about it)
UCP isn’t yet in head-to-head competition with another commerce protocol — no major alternative has the same scope or partner list. The closest comparison points:
| UCP | Stripe + custom APIs | A2A (commerce-flavored) | |
|---|---|---|---|
| Scope | Discovery → checkout → orders | Payments only | Agent messaging only |
| Reach | Multi-retailer standard | Per-merchant integration | Cross-vendor agent layer |
| Strength | Standardised commerce primitives | Mature payment platform | Open agent-to-agent messaging |
| Used by Google’s stack | Yes (AI Mode native checkout) | Sometimes (alongside) | Yes (for agent discovery) |
UCP probably layers on top of Stripe (Stripe is a UCP partner) and uses A2A under the hood.
Strengths
- Cross-retailer one-shot — agents can buy from any UCP-compliant retailer with one integration.
- Major partner network — Shopify + Etsy + Wayfair + Target + Walmart at day one.
- Built on standards — REST + JSON-RPC; not proprietary.
- Composable with MCP / A2A / AP2 — fits the existing agentic stack.
Risks and open questions
- Single sponsor — Google is the lead author. Will OpenAI, Anthropic, and Microsoft adopt or fork it?
- Identity model — Identity Linking has to satisfy both retailer fraud rules and user consent expectations.
- Refund / dispute UX — order management through a third-party agent introduces new dispute flows.
- Margin pressure — if every agent can shop across all retailers seamlessly, retailers compete more on price than on storefront stickiness.
What’s next
- More retailers — expect rapid expansion of UCP-compliant retailers through 2026.
- More agent surfaces — ChatGPT, Claude, Perplexity each have shopping ambitions; the open question is which adopt UCP versus build proprietary.
- AP2 + UCP — payment + commerce co-evolution.
- International expansion — initial focus is US retailers; international launch pacing TBD.
TL;DR
UCP is the open commerce protocol for the agentic web — co-developed by Google and major retailers, layered on top of MCP / A2A / AP2. It powers Native Checkout in Google’s AI Mode and the Gemini app today, and is positioned to be the standard plumbing for any agent that buys things on a user’s behalf.