What is UCP?
Universal Commerce Protocol (UCP) is an open standard that lets AI agents shop for people: search a catalog, add items to a cart and complete a checkout, all through calls a program can make.
The problem
Online stores are built for people clicking buttons. An agent needs structured, machine-readable ways to browse products, compare options and buy. Without a shared protocol, every store needs its own integration.
How UCP solves it
UCP defines a set of capabilities any store can implement. An agent connects to the store's UCP endpoint and uses standard operations. Exact tool names vary a little by store and transport; typical ones are:
- search_catalog: search products with filters, pagination and sorting (Shopify's older storefront endpoint calls it
search_shop_catalog) - lookup_catalog / get_product: fetch full product details, including variants, prices and availability
- create_cart / update_cart: manage a cart and its line items
- create_checkout / update_checkout / complete_checkout: run the checkout, including payment
The specification is versioned by date. The current releases are 2026-08-25 (latest) and 2026-04-08.
Transports
A store can declare four transports in its UCP profile, the ways an agent connects:
- MCP (Model Context Protocol): JSON-RPC over HTTP for tool calls. The main transport for agents.
- REST: standard HTTP endpoints, for stores that serve UCP as an HTTP API.
- A2A: agent to agent. The store side is itself an agent, the store agent, described by an agent card. UCP's A2A binding covers checkout: the buyer's agent sends checkout actions to the store agent as messages.
- Embedded: the Embedded Checkout Protocol (ECP). The agent builds the checkout, then the store's own checkout page opens inside the agent's window and the buyer finishes there. The page and its host talk in JSON-RPC messages over
postMessage.
UCP Playground connects over all four. Runs and Inspect call the store's tools over MCP or REST, send checkout to the store agent over A2A (0.3 or 1.0), and open the store's own checkout page (Embedded). See A2A: the store's agent and Embedded: the store's checkout.
Some stores also register tools on their own website through WebMCP. That is a separate route, not a UCP transport. The Playground can send an agent through the store's website and set it beside the store's UCP tools; see WebMCP: the store page.
What is UCP Playground?
UCP Playground is a place to test stores and agents over UCP. You can:
- Inspect: open a store in Inspect and send its tools your own calls, one at a time, to see exactly what it returns. Without an account, the public Inspector does the same.
- Run: on Runs, give an agent a task at a store and watch it shop over UCP, or through the store's website. Pick the model (Claude, GPT, Gemini and others) and see how far it gets.
- Replay and share: every run is kept whole. Replay it, read every call in its trace, and Share it as a link or an embed.
- Look back: History lists every run and Inspect session in your workspace.
- Compare models: the public Leaderboard and Models compare pages show how models do across stores.
- Audit: published UCP compliance scores across profile, runtime and gap consistency are on the UCP Checker Leaderboard.
New to UCP Playground? The Quick start takes you through your first run in a few minutes.
Discovery
A store says it supports UCP through its UCP profile: the JSON file at /.well-known/ucp that tells agents what the store supports. It says which UCP version the store runs, which transports it serves and where, what capabilities it declares and which payment methods it accepts.
UCP Playground reads this profile as soon as you choose a store, so you can see what the store supports before you run anything.
Something wrong on this page?