Skip to content

Universal Commerce Protocol (UCP)

UCP, the open commerce protocol from Google, Shopify and partners: capabilities, discovery, transports, payments, governance and adoption.

Updated October 4, 2026 6 min read .md

In short: The Universal Commerce Protocol (UCP) is an open standard for how AI agents and other platforms discover a business’s commerce capabilities and use them, from catalog search and carts through checkout, account linking and orders. Google announced it at NRF on January 11, 2026, co-developed with Shopify, Etsy, Wayfair, Target and Walmart. As of October 2026 the latest release is v2026-08-25, which expanded UCP beyond retail shopping into food and lodging.

What UCP is for

Without a shared standard, every AI surface needs a custom integration with every merchant, which Google describes as an N×N problem. UCP gives businesses one way to describe what they support and how to call it. Any compatible agent can then work with any compatible business.

UCP is published at ucp.dev, with the specification and reference implementations on GitHub under the Apache 2.0 license. Samples are available in Python and TypeScript.

Roles

RoleDescription
PlatformThe agent or app acting for the buyer, such as a shopping assistant or marketplace
BusinessThe merchant that sells, processes orders and is merchant of record
Credential provider / PSPThe party holding or processing payment credentials

Capabilities and extensions

UCP is organized as capabilities, units of functionality that a business can support, and extensions, which add fields or behavior to a capability.

Capabilities use reverse-domain names, so the namespace shows who governs them. Core capabilities live under dev.ucp.*, for example dev.ucp.shopping.checkout. Third parties can define their own, such as com.example.payments.installments, without a central registry. Extensions declare which capability they extend. Discounts, for example, extend checkout.

As of the August 2026 release, core capabilities include:

  • Catalog: product search and lookup (added April 2026)
  • Cart: building a basket before checkout (added April 2026)
  • Checkout: totals, fulfillment, discounts, loyalty, subscriptions and payment, including an embedded checkout option for cases that need a merchant-rendered step
  • Identity linking: OAuth 2.0-based account linking with capability-specific scopes, so a buyer’s loyalty status or saved details can carry into the agent experience
  • Order: order retrieval and post-purchase events

The v2026-08-25 release restructured the protocol so it can support more than one industry. It added Food and Lodging alongside Shopping, plus grocery features (location search, opening hours, fractional quantities). It also added 3-D Secure 2 authentication flows, payment schedules and split payments across instruments, and independent versioning for each capability. A draft Lodging Booking capability followed on September 25, 2026.

Discovery and negotiation

A business publishes a profile at /.well-known/ucp. The profile lists:

  • the supported protocol version
  • the available services and transports
  • the capabilities and their schema URLs
  • the accepted payment handlers
  • public signing keys, as a JSON Web Key Set

A platform sends its own profile URL in a UCP-Agent header on each request. The two sides then compute the overlap: the capabilities both support, at the highest version both understand, dropping any extension whose parent capability isn’t shared. Platforms must check that a capability’s schema is hosted on a domain matching its namespace before fetching it. That rule stops a third party from impersonating the dev.ucp namespace.

Versions are dates (YYYY-MM-DD). The protocol version is fixed for a session, while capabilities negotiate their versions independently.

Transports

UCP defines the same operations over several transports:

TransportTypical use
RESTServer-to-server HTTP/JSON, defined with OpenAPI
MCPExposes UCP operations as tools to LLM-based agents
A2AAgent-to-agent exchanges with a merchant’s own agent
EmbeddedIn-page or in-process integration

Shopify’s agent tooling is an example. Its catalog, cart, checkout and order MCP servers implement UCP capabilities through the MCP binding. In April 2026 Shopify brought its earlier Storefront Catalog MCP into line with the UCP Catalog capability.

Payments

UCP separates payment instruments (what the buyer pays with) from payment handlers (who processes it). Businesses list the handlers they accept in their profile, keyed by reverse-domain name. That lets wallets, PSPs and networks take part without changes to the core protocol. The spec describes three patterns:

  1. Digital wallet: the platform tokenizes the credential, for example with Google Pay.
  2. Direct tokenization with challenge: supports strong customer authentication and 3-D Secure.
  3. Autonomous agent: uses the AP2 mandates extension, so an agent can complete a purchase under a mandate the user signed earlier.

Relationship to AP2 and ACP

  • AP2 is the payment-authorization layer UCP uses for agent-signed transactions. Google designed UCP to be compatible with AP2 from the start, and the AP2 project describes itself as extending UCP.
  • ACP, from OpenAI and Stripe, covers overlapping ground: checkout sessions, feeds, carts and orders. The two are separate specifications without a formal bridge. In practice, PSPs and platforms such as Stripe, Shopify and Visa’s Intelligent Commerce Connect support both behind one merchant integration.

Governance

UCP is open source, but it is governed by companies, not by a foundation:

  • A Tech Council was set up at launch with Google, Shopify, Etsy, Target and Wayfair. On April 24, 2026 it expanded, adding Amazon, Meta, Microsoft, Salesforce and Stripe.
  • A Governing Council added Stripe as a permanent member alongside Google and Shopify on April 28, 2026.
  • Industry councils followed. Food (July 2026) includes Block, DoorDash, Toast and Uber Eats. Lodging (August 2026) includes Amadeus, Booking.com, Expedia, Hilton, Marriott and Trip.com. Payments (September 2026) includes Adyen, Ant International, Coinbase, Global Payments, PayPal, Shopify and Stripe.

As of October 2026 UCP has not moved to a neutral foundation such as the Linux Foundation, which now hosts MCP and A2A.

Adoption

As of October 2026:

  • Google uses UCP for checkout in AI Mode in Search and the Gemini app. It began with eligible US merchants and later expanded to more markets. Google said a March 2026 update added cart, catalog and identity-linking support on its surfaces.
  • Shopify merchants are UCP-enabled through the platform. Shopify’s agent developer tools (catalog, cart, checkout and order MCP servers, and a UCP CLI) are built on it, and self-serve developer access replaced an approval process in 2026. On September 28, 2026 Shopify extended its browser-side WebMCP tools to checkout, also built on UCP.
  • Microsoft made UCP-ready product feeds generally available in Microsoft Merchant Center for Copilot in the US in April 2026.
  • Endorsers at launch included Adyen, American Express, Best Buy, Flipkart, Macy’s Inc., Mastercard, Stripe, The Home Depot, Visa and Zalando.

Practical notes

  • Merchants on supporting platforms mostly need good product data and the correct platform settings. Custom stacks need a /.well-known/ucp profile and at least the checkout capability.
  • Identity linking is a distinguishing feature. It lets loyalty pricing and member benefits apply inside an agent experience.
  • Expect frequent releases. UCP shipped four dated releases in its first eight months.

Sources

The newsletter

Agentic commerce, explained as it happens.

New protocols, launches and what they mean for you. Plain language, no hype.

I'm a…