Analysis · reviewed 8 September 2026

UCPUniversal Commerce Protocol

Sponsor
Google and Shopify, with retail partners
Status
Open specification, Apache 2.0, announced January 2026
First published
11 January 2026
Layers
Commerce

UCP is the merchant-side answer to ACP, and its existence proves the commerce conversation and the payment authorisation are now separate standards problems with separate owners.

What it is

Announced at NRF in January 2026 and published under Apache 2.0, UCP defines how agents discover and transact with merchants across the whole shopping journey: product discovery, capability negotiation, checkout, and post-purchase handoff. It was co-developed by Google and Shopify with a coalition of retailers and is wired into Google's own agent surfaces.

It is explicitly designed to compose with the rest of the stack: A2A for agent-to-agent communication, AP2 for payment authorisation, MCP for tool access. UCP does not attempt to define how the buyer's authority is established — it assumes something else does.

Announced11 January 2026, NRF
LicenceApache 2.0
StagesDiscovery, capability negotiation, checkout, post-purchase handoff
CompositionWorks with A2A, AP2 and MCP

Two commerce protocols, one merchant

A merchant that wants to be reachable by agents now faces ACP, maintained by OpenAI and Stripe and reached through ChatGPT, and UCP, co-developed by Google and Shopify and reached through Google's surfaces. Both cover discovery-to-checkout. Both are Apache 2.0. Neither is a superset of the other.

This is a distribution fight, not a technical disagreement, and it will probably be resolved the way such fights usually are: with adapters, with commerce platforms implementing both on the merchant's behalf, and eventually with convergence in a neutral body. The useful consequence for anyone building authority infrastructure is that the commerce layer is visibly not the layer where delegation will be settled — both protocols point at something else for that.

What it does not do

  • Says nothing about whether the buyer authorised the purchase; it defers to AP2 and equivalents.
  • Reach is tied to the surfaces that implement it, which today means Google's and its retail coalition's.
  • Consumer retail in shape and vocabulary; not a business-to-business procurement protocol.

Where mnd8t sits relative to it

Orthogonal. UCP standardises the shopping conversation. Whether the agent should be shopping at all, at this amount, with this counterparty, at this hour, is decided before the conversation starts — and that decision, with its reasons, is what mnd8t produces and retains.

Last reviewed 8 September 2026. Corrections: hello@mnd8t.com.