The Universal Commerce Protocol, as stores publish it
UCP lets an agent find out what a store can do, then do it: search, build a cart, check out and pay. The spec says what's possible. This page also shows what stores actually declare: about 1.2 million of 3.7 million live ecommerce sites publish a valid UCP profile (November 2026 market read), and below, what the stores we check declare.
- DiscoverRead the profile
One JSON file at /.well-known/ucp says what the store offers.
- NegotiateAgree what's shared
A release both support, and only the capabilities both declare.
- CallUse a service
Over one of four transports: MCP, REST, A2A or Embedded (the store's checkout, opened in the buyer's browser).
- PayThrough a handler
With one of the store's payment handlers, usually as a token, not a card number.
The protocol, layer by layer
What each part of a profile does, and the share of the stores we check with a valid profile that declare it.
ucp.versionRelease
Which release's rules the store follows.
Releases are dated. Stores follow their platform's release, which is why one or two dominate.
ucp.servicesTransports
Where an agent sends requests, and how.
A store can offer several. Embedded opens the store's checkout in the buyer's browser.
ucp.capabilitiesWhat an agent may do
The shopping core, its extensions, and shared capabilities.
Names shortened from dev.ucp.shopping.* and dev.ucp.common.*. Vendor extensions sit beside them, like dev.shopify.catalog (68.4%).
ucp.payment_handlersHow it's paid
The payment methods a store accepts, and how to tokenise them.
Required since 2026-01-23, even when empty. The most declared three are shown.
keysHow messages are checked
Public keys an agent uses to verify what the store signs.
Optional, beside ucp at the root of the profile; called keys since 2026-08-25, signing_keys before.
What the checks show that the spec can't
of the stores we check with a valid profile run on two platforms
Shopify (68.4%) and Wix (21.7%). Much of what UCP looks like in practice is what those two switch on by default. Platforms
of MCP endpoints we called answered
Of the stores whose MCP endpoint our services check called, this share answered tools/list. Declared and working, mostly, line up. How we check
publish no signing keys
Keys let an agent check messages a store signs, like order updates. Optional. The share is of the stores we check with a valid profile.
declare a capability release 2026-08-25 added
2026-08-25 added permalink, location search, location lookup, ask, loyalty, payment terms, payment authentication and split payments. The share is of the stores we check with a valid profile. What changed
Shares are of the stores we check with a valid profile, from each store's latest check. Read 20 November 2026.
What is the Universal Commerce Protocol (UCP)?
/.well-known/ucp that says which release it follows, and its services, capabilities and payment handlers.How does an agent find a store that supports UCP?
https://{domain}/.well-known/ucp. That JSON file names the store's release, the services an agent can call and how, its capabilities and its payment handlers. The profile, field by fieldWhat are UCP capabilities?
dev.ucp.shopping.checkout, and extensions build on the core ones. Every capability