Google’s Common Commerce Protocol is the primary manufacturing blueprint for what each web site (ecommerce or not) will finally want to reveal to AI brokers: discoverable actions, predictable outcomes, persistent classes, and specific agent insurance policies.
UCP was launched as infrastructure for Google Service provider Middle retailers. However the extra necessary story is the structure beneath it. UCP is the primary actual implementation of what I’ve been speaking about within the Interplay pillar of machine-first structure. If you wish to perceive what agent-ready web sites seem like in follow, you could have a look at UCP’s developer documentation. The structure is the lesson, and it goes far past Google Buying.
What Google Truly Constructed
UCP is an open normal Google unveiled in January 2026 on the Nationwide Retail Federation convention alongside Shopify, Etsy, Wayfair, Goal, and Walmart, as a typical language between AI surfaces (Gemini, Google AI Mode) and service provider backends. In keeping with Google’s “Beneath the Hood” submit on UCP, the protocol has 4 transferring components value taking note of.
A discovery endpoint at /.well-known/ucp. Brokers question the /.well-known/ucp URL to be taught what a service provider’s web site can do, which merchandise it sells, which actions it exposes, and which transports it helps. This manifest is the handshake between an AI agent and a service provider’s backend. With out that manifest, an agent has no data of what it must parse or name. At finest, it would attempt to guess.
Three REST endpoints for checkout. UCP reduces the whole transaction to 3 calls: Create a session, replace a session, full a session. That’s it. No cart web page, no tackle type, no affirmation display screen. The checkout state lives in session responses, not in rendered HTML. Human layer of your web site will get fully ignored. An interface will exist, but it surely is not going to be the one you designed.
Transport flexibility. UCP helps REST, Mannequin Context Protocol (MCP) bindings, and A2A (Agent-to-Agent), so brokers constructed on totally different stacks can speak to the identical service provider backend with out customized adapters. An agent working inside Gemini and an agent working on a customized MCP consumer can each hit the identical UCP endpoints. This was a really sensible transfer.
An open specification at ucp.dev. UCP is revealed as an open spec any web site, AI platform, or service provider platform can implement. Google doesn’t personal the protocol or its governance. The openness issues as a result of the structure turns into moveable to any web site exterior Google Service provider Middle, even when Google’s onboarding path doesn’t.
Google is constructing UCP for its personal Buying ecosystem first. UCP’s design is the true lesson for everybody else, and that design is a textbook implementation of the Interplay pillar of machine-first structure. Buying carts are deserted by roughly 70% of people (per Baymard Institute’s long-running checkout analysis). You may count on the agent abandonment fee on web sites with no Interplay layer to be nearer to 100%.
For UCP’s place within the broader agentic commerce panorama, alongside OpenAI and Stripe’s ACP, Shared Cost Tokens, and the platforms already promoting via AI brokers, see Promoting to AI: The Full Information to Agentic Commerce. For the particular capabilities Google shipped in March 2026 (Cart, Catalog, and Id Linking), see Google’s UCP Replace: Carts, Catalogs, and Loyalty in AI Buying.
UCP Is The Interplay Pillar In Manufacturing
The Interplay pillar of machine-first structure describes what an internet site should expose so an AI agent can accomplish a aim on it. 5 properties: discoverable actions, predictable outcomes, workflow continuity, error restoration, and agent insurance policies. UCP maps to every one virtually completely.
Discoverable actions. The Interplay pillar says brokers want a machine-readable index of what they’re allowed to do on a web page earlier than they attempt to do it. UCP’s /.well-known/ucp functionality manifest is precisely the machine-readable motion index the Interplay pillar requires, shipped as a manufacturing endpoint. An agent fetches the manifest, reads the checklist of accessible operations, and plans its subsequent step. No trial and error, no DOM scraping.
Predictable outcomes. The Interplay pillar says each motion ought to return machine-readable state (computed totals, allotted stock, success flags), not a 200 OK with an HTML receipt. UCP session responses carry structured knowledge at each step: pricing breakdowns, low cost allocations, and specific session state. An agent studying a UCP response is aware of precisely what simply occurred and what it owes subsequent.
Workflow continuity. The Interplay pillar says brokers want secure session references that survive throughout multi-step workflows, so they don’t lose context mid-task. UCP classes have persistent IDs, and PUT updates carry that ID ahead. An agent can add a line merchandise, apply a reduction, regulate delivery, and full the order throughout a number of calls with out re-creating state.
Error restoration. The Interplay pillar says failures ought to return structured options, not lifeless ends. When a UCP low cost code fails, the session response explains why and surfaces options the agent can strive. A human would possibly click on “strive once more.” An agent wants a payload that tells it what to do subsequent.
Agent insurance policies. The Interplay pillar says web sites ought to declare what brokers are allowed to do, what requires human affirmation, and what’s off-limits totally. UCP’s functionality declarations are that coverage layer: A service provider indicators which actions brokers can invoke, beneath what situations, and the place human approval is required. Request signatures and tokenized funds implement the coverage on the protocol stage.
Google’s /.well-known/ucp endpoint is the Interplay pillar’s “discoverability of actions” being shipped as manufacturing infrastructure. Brokers question it to be taught what an internet site can do earlier than they try and do it. UCP requires three REST endpoints for checkout: session creation, updates, and completion. That’s the complete Interplay pillar decreased to 3 API calls.
The Hole UCP Exposes For Everybody Else
UCP is Google’s reply to the agent-traffic hole inside its Buying ecosystem. Each non-UCP web site nonetheless has the hole, although not each retailer agrees on the place the hole truly lives.
Breanna Fowler, Dell’s Head of World Shopper Income Packages, informed Digital Commerce 360 in an April 2026 interview that she has not but seen “something behaviorally constant” within the agent site visitors reaching Dell.com. Her focus is search and discoverability, not agent-specific infrastructure: “If I can’t discover your merchandise simply and effortlessly, no quantity of content material and configurator capabilities, no person actually provides a crap about that stuff.”
Fowler is true that nothing issues if brokers can’t discover the product. However for an AI agent, “discovering” a product doesn’t imply typing right into a search field. Discovering means querying a functionality manifest, studying a structured product catalog, and invoking a discoverable motion. In a human-first web site, findability is a UI drawback. In an agent-ready web site, findability is a protocol drawback. UCP exists as a result of Google determined that treating findability and checkout as protocol issues, not UI issues, is the one manner agent conversions ever scale.
A Gemini agent buying via a UCP-enabled service provider doesn’t parse a product grid, doesn’t guess at type fields, and doesn’t hope nothing re-renders beneath it. The agent queries /.well-known/ucp, reads the aptitude manifest, and advances the session via UCP’s three checkout endpoints. The remainder of the online (each SaaS dashboard, each B2B quote circulation, each reserving system, each subscription portal) has no equal protocol coming to rescue it.
Baymard Institute’s aggregated checkout analysis places the human cart abandonment fee at 70.22% throughout 50 research. The agent abandonment fee on web sites with out an Interplay layer is nearer to 100% as a result of people hesitate at checkout, whereas brokers can’t even discover checkout.
What Each Web site Can Be taught From UCP’s Structure
You don’t want to implement UCP. You might be most likely not even a commerce enterprise. UCP’s structure nonetheless generalizes into 5 ideas any agent-ready web site ought to implement: a functionality manifest, structured actions, machine-readable state, persistent classes, and an specific agent coverage.
1. Publish a functionality manifest. Brokers have to know what your web site can do earlier than they begin. That manifest may be a /.well-known/ endpoint, an llms.txt file, a WebSite schema node with potentialAction entries, or an MCP server itemizing out there instruments. The format issues lower than the existence. If there may be nothing for an agent to question, the agent has to guess, and guessing is how conversions die.
2. Expose actions as structured knowledge. Schema.org has supported Actions for over a decade, together with BuyAction, OrderAction, ReserveAction, SubscribeAction, and SearchAction. Virtually no web sites use them. UCP’s POST /classes endpoint is successfully a BuyAction goal given a secure API contract, which is what schema.org Actions have wanted for a decade to really work. Any web site can do the identical by itself actions: declare the motion sort, identify the endpoint, doc the payload. The how AI brokers see your web site submit lined the Construction pillar aspect of this query. Schema.org Actions are the Interplay pillar aspect.
3. Return machine-readable state at each step. Each response to an agent ought to carry structured state the agent can parse: what occurred, what modified, what’s subsequent. HTML affirmation pages aren’t machine state. A redirect to /thank-you shouldn’t be machine state. JSON with named fields and specific flags is machine state. Returning JSON state as an alternative of HTML affirmation pages is the only greatest architectural shift from human-first design to agent-ready design.
4. Design for classes, not pageviews. Brokers don’t restart after they get distracted. They arrive again to a workflow in progress and count on the state to nonetheless be there. Periods with secure IDs, safe-to-retry updates, and swish resume paths aren’t non-obligatory for brokers; they’re the bottom layer. Pageview analytics educated a era of product groups to suppose in discrete hits. Brokers suppose in transactions.
5. Declare your agent coverage explicitly. An agent coverage defines three issues: what brokers can do with out asking a human, what requires human affirmation, and what’s off-limits totally. UCP solutions these questions via functionality declarations. Your web site can reply them via an AGENTS.md file, a /.well-known/ coverage endpoint, or structured annotations. Choose one. Publish it. Guessing a coverage is how brokers find yourself taking actions their customers didn’t intend.
None of those ideas require Google’s participation. None require UCP’s adoption. They require a choice to deal with an internet site as an API floor for brokers along with a display screen for people.
Quotation Will get You Into The Reply. Actions Get You Into The Income
A lot of the AXO dialog immediately continues to be in regards to the Content material pillar: learn how to get cited in ChatGPT solutions, learn how to rank in Google AI Overviews, learn how to change into the supply AI surfaces quote. That work issues. Quotation drives consciousness, and consciousness is the highest of the funnel. The search engine optimisation to AAIO and Reply Engine Optimization articles lined learn how to win it.
UCP demonstrates the Interplay pillar, which is the opposite half of the agent-ready web site stack that AEO and GEO don’t cowl. The Interplay pillar is about being transacted via by an AI agent, not quoted in its reply. The distinction between a cited web site and a transactable web site is the Interplay pillar. Quotation will get you into the AI’s reply. Discoverable actions get you into the AI’s income.
On the Cheeky Pint podcast, Sundar Pichai described a future the place an AI person has “many threads working” on the similar time, analysis, comparability, reserving, buy, all executing in parallel on behalf of a single human. In that mannequin, the web site that lets the agent resolve its thread quickest wins the thread. Decision means finishing an motion, not loading a web page. Dell has the site visitors and loses the thread. A UCP-enabled service provider resolves the identical thread in three API calls.
UCP is the primary manufacturing artifact that will get the Interplay pillar proper. UCP is not going to be the final. Each web site that wishes to take part in agent-mediated income will finally have to ship its personal model of the identical structure, via an open protocol, a schema.org functionality layer, a WebMCP endpoint, or a customized MCP server. The spec can range even when the ideas can’t.
UCP is the working reference implementation of the Interplay pillar, constructed by Google and working in manufacturing inside Google Buying immediately. Each different web site nonetheless owes its personal reply. Dell’s Breanna Fowler stated discoverability is what issues. For an agent, discoverability is a protocol.
Extra Sources:
This submit was initially revealed on No Hacks.
Featured Picture: Natalya Kosarevich/Shutterstock
