UCP, plainly: the protocol that lets AI assistants buy from your store
For the past year, the question about AI and your store was whether assistants could read it — whether ChatGPT, Perplexity or Gemini could find your products and recommend them. As of January, there is a second question: whether an assistant can complete the purchase. That is what the Universal Commerce Protocol is for, and it is worth understanding now, while almost nobody has set it up.
What UCP actually is
The Universal Commerce Protocol is an open specification co-developed by Google and Shopify, announced at the National Retail Federation conference on January 11, 2026 and released under the Apache 2.0 license. It defines how an AI agent discovers what a store sells, negotiates what the store supports, runs checkout, and hands off post-purchase data — four stages, end to end.
It is not a Google-only or Shopify-only arrangement. The launch coalition included more than twenty retailers, payment networks and processors, and the protocol is already wired into Google AI Mode, the Gemini apps, and Microsoft Copilot Checkout. It is also designed to sit alongside the other agent standards — MCP, Agent2Agent, and the Agent Payments Protocol — rather than compete with them.
How an agent finds out your store speaks it
Discovery starts at a fixed address: yourdomain.com/.well-known/ucp. A store that supports the protocol serves a JSON manifest there — the protocol version, the capabilities it supports, its service endpoints, and its accepted payment handlers. An agent reads that manifest, negotiates what it can handle, and proceeds from browsing to buying.
You can check your own store right now: open /.well-known/ucp on your domain. A page of JSON means the surface is live. An error page means assistants can read your store but cannot transact with it — which today is the normal state for almost every store on the internet.
What this changes for a merchant
Two things, one obvious and one less so.
The obvious one: stores that speak UCP become places an assistant can finish the job. When a shopper tells an agent to find and buy something, the agent can only complete that instruction at a store with a live UCP surface.
The less obvious one: your product content matters more under UCP, not less. When an agent pulls your products into a side-by-side comparison, what it compares is your titles, your descriptions, your variants, your prices and your policy pages. The protocol moves the transaction; the content still decides it. Thin descriptions and vague policies read exactly as badly to an agent mid-purchase as they do to one answering questions.
What to do this week
- Open yourdomain.com/.well-known/ucp and see where you stand. It takes ten seconds.
- If you are on Shopify, support is native: install the official Universal Commerce Agent app from the Shopify App Store, then confirm the manifest answers.
- Make sure the content an agent will transact against is complete — real product descriptions, accurate availability, and finished policy pages. Incomplete policies can keep a store out of agentic surfaces regardless of how good the product data is.
Our free scanner at lunalink.ai/scan now checks the UCP surface as part of every scan, alongside the read-layer checks — robots.txt, your catalogue endpoint, product markup and policies — so one run shows you both whether assistants can read your store and whether they can buy from it.