What UCP is and why it exists
As AI agents that buy on behalf of users become common, an infrastructure problem appears: the agent
needs to know what a particular store can do before the transaction starts. Without a standard,
every agent integrates with every retailer separately.
UCP answers that with a capability profile — a machine-readable document in which the store
declares the operations it supports: product search, adding to the basket, placing an order,
tracking delivery, returns. The agent reads the profile, understands the capabilities and acts
accordingly.
The agentic commerce standards landscape (2026)
At the start of 2026 there are several competing standards:
| Protocol | Initiator | Focus |
|---|---|---|
| UCP | Google (NRF 2026) | The merchant’s commercial capabilities |
| ACP | OpenAI / Stripe | Payment operations and mandates |
| MCP | Anthropic | The general agent-to-tool protocol |
| YCP | Yandex | Commercial operations inside the Yandex ecosystem |
Yandex is the dominant search engine in Russia and several CIS markets, so YCP matters to retailers
operating there and is largely irrelevant elsewhere. The likely outcome across all of them is
convergence or mutual compatibility, but for now retailers have to watch each one.
What it means for a retailer
UCP is not only a technical standard — it is a question of visibility in agent-driven search. A
Google Shopping agent, or any other agent built on UCP, will only be able to transact in stores that
support the protocol. A retailer without UCP is invisible to agent traffic, in the same way a site
without a sitemap is invisible to a search crawler.
Important: UCP does not replace a store’s existing API — it adds a standardised description on
top of it. Adoption looks more like publishing structured data (schema.org) for search crawlers
than like rebuilding the API.