Universal Commerce Protocol (UCP)
The Universal Commerce Protocol (UCP) is a Google-led open protocol, published on 11 January 2026, that lets a business advertise commerce capabilities to AI agents at a /.well-known/ucp discovery endpoint. It is broader than a checkout spec, covering catalog search and lookup, cart building, identity linking, checkout, and order management, and it runs over REST and JSON-RPC with AP2, A2A and MCP support built in.
What it is and how discovery works
UCP launched with Shopify, Etsy, Wayfair, Target, Walmart and around twenty other partners. Its distinguishing mechanic is discovery: a business publishes what it can do at a /.well-known/ucp endpoint, and an agent reads that document to find out which capabilities are available before doing anything else.
The capability set spans the commerce lifecycle rather than just the payment moment: catalog search, product lookup, cart building, identity linking, checkout, and order management. Transport is REST and JSON-RPC, with AP2 for payments, A2A for agent-to-agent interaction, and MCP supported. It has begun extending past retail into lodging and food.
Catalog lookup is the part distributors should read twice
Checkout gets the attention. Catalog search and lookup as a named, specified capability is the more consequential development for anyone with a large catalog, because it makes the quality of your product record directly queryable by a machine that will compare it against someone else's.
Until now, a competitor with better attribute coverage beat you slowly, through better filtering and better search results. A protocol that lets an agent query both catalogs and evaluate the responses in the same turn compresses that into a single comparison. Coverage gaps stop being a slow leak and become an immediate loss.
Which puts the emphasis back on the record: fill rate on the attributes buyers filter on, normalized MPNs, real unit of measure and pack hierarchies, branch-level availability. The wire format is the cheap half.
UCP versus ACP
| UCP | ACP | |
|---|---|---|
| Led by | Google, with launch partners | OpenAI and Stripe |
| Published | 11 January 2026 | Beta, spec revised through 2026 |
| Scope | Catalog, cart, identity, checkout, orders | Checkout and payment delegation |
| Discovery | /.well-known/ucp endpoint | Merchant-integrated APIs |
| Governance | Google-led open protocol | Founding maintainers, foundation path stated as future |
They are not mutually exclusive and the ecosystem has not settled. A distributor being asked to pick one this year is being asked to bet on an outcome nobody knows yet, which is an argument for investing in the underlying record — the part that is valuable under every outcome — rather than in a wire format.
Does this replace PunchOut?
Not yet, and not soon in the segments where PunchOut is entrenched. PunchOut and cXML are how a buyer's procurement system already reaches a supplier catalog with contract pricing and approval routing attached, and they are deeply embedded in enterprise purchasing.
The interesting question is whether agentic protocols end up serving the same job with a different mechanism — an agent inside the buyer's procurement environment querying supplier catalogs directly. If that happens, the winning suppliers will be the ones whose catalog answers a structured query completely, which is the same requirement PunchOut buyers have had all along.
Frequently asked questions
What is the Universal Commerce Protocol?
A Google-led open protocol published on 11 January 2026 that lets businesses advertise commerce capabilities to AI agents at a /.well-known/ucp discovery endpoint. It covers catalog search and lookup, cart building, identity linking, checkout, and order management over REST and JSON-RPC.
How does UCP differ from the Agentic Commerce Protocol?
UCP is broader and Google-led, covering the whole merchant surface from catalog lookup through order management with a discovery endpoint. ACP is maintained by OpenAI and Stripe and focuses on checkout and payment delegation. They address overlapping but different scopes and the ecosystem has not consolidated.
What is the /.well-known/ucp endpoint?
A discovery document at a fixed path on the merchant's domain where a business advertises which UCP capabilities it supports. An agent reads it first to learn what interactions are available before attempting catalog queries, cart operations, or checkout.
Should a distributor implement UCP now?
Implement it when the catalog behind it can answer a structured query well. The protocol makes product-record quality directly comparable between suppliers in a single agent turn, so shipping an endpoint over a catalog with large attribute gaps mostly makes the gaps easier to measure.