Merchant guide · Updated
The Universal Commerce Protocol (UCP), explained for merchants
The Universal Commerce Protocol (UCP) is Google’s open standard for agentic commerce: it lets AI assistants such as Google AI Mode and Gemini read a merchant’s live catalogue and start a checkout. WatEase implements it per business, with a UCP profile at /.well-known/ucp on the business’s own domain.
Part of WatEase, India’s agentic AI commerce and marketing platform.
- 14-day money-back guarantee in our Terms
- Data hosted in India
- Approvals you set on every agent
- Guided onboarding on every plan
GET /.well-known/ucpProfileCatalogue search, lookup, availability and checkout listedPOST /catalog/searchCatalogue“Linen shirt under ₹2,000” · 6 in stockPOST /catalog/lookupCatalogue₹1,890 · sizes M and L in stock, read livePOST /availabilityDeliveryDelivers to pin code 560001POST /checkout-sessionsSignedRFC 9421 signature verified · priced with delivery and GSTPOST /checkout-sessions/…/completeYour siteBuyer sent to your checkout with the bag filled in
Nothing is charged inside Google: the buyer pays on your own checkout.
Demo businesses, names and figures are fictional and shown for illustration — not customer results.
The standard
What is the Universal Commerce Protocol?
The Universal Commerce Protocol is Google’s open standard for how AI agents and stores work together: how a store describes what it sells, how an agent searches it, and how a checkout is opened. Its specification is published at ucp.dev, and Google’s shopping in AI Mode and the Gemini app uses it.
With UCP, an assistant does not have to guess from your web pages. It asks your store, and your store answers with the live price, stock and delivery, in a shape every UCP agent understands.
For a merchant, UCP comes in three parts:
Discovery
The profile
A JSON document at
/.well-known/ucpon your domain that says which UCP services and capabilities your store offers, and where to call them.Catalogue
Search, lookup and availability
The calls an agent makes while a shopper decides: find products, fetch them by id, and check stock and delivery.
Checkout
Checkout sessions
The order an agent builds with your store and the buyer confirms, priced by your store, with the payment finished where your store says.
Discovery
How does a UCP profile at /.well-known/ucp work?
A UCP profile is a small JSON document at https://your-domain/.well-known/ucp that tells an agent which UCP services and capabilities your store offers and where to call them. An agent reads it first, to learn what it can ask your store for.
On WatEase the profile is published on your own domain only after you switch Google on; for any other address it answers “not found”. It is served without redirects and cached for five minutes, as UCP’s discovery rules expect, and it lists these capabilities:
| Capability | What an agent can ask | Listed when |
|---|---|---|
| dev.ucp.shopping.catalog.search | Search your catalogue in plain words, with the shopper’s country, pin code and language | Google is switched on |
| dev.ucp.shopping.catalog.lookup | Fetch up to 50 products by id, or one product in full | Google is switched on |
| com.watease.availability | Stock and delivery to a pin code; free rooms and rates for dates; free table times for a party | Google is switched on |
| com.watease.checkout_link | A signed, expiring link that opens your own checkout with the bag, or the stay, filled in | Google is switched on |
| dev.ucp.shopping.checkout, with the fulfillment extension | Open, update, complete or cancel a checkout session for a web store | Take orders inside Google is on |
| dev.ucp.lodging.booking (a draft) | Open a booking session for a hotel stay | Take bookings inside Google is on |
The two com.watease capabilities are WatEase’s own, named the way UCP lets a business add capabilities of its own. The profile offers no payment handler: the buyer pays on your own checkout.
Catalogue
How do catalogue search, lookup and availability work?
Google’s agent sends a search, a list of product ids or an availability question, and your store answers from live data at that moment, never from a stored copy. Every answer carries your price, stock for each variant and a link to the product on your website.
- Search. A query in plain words, with the shopper’s country, pin code and language; up to 50 results a page, with a cursor for the next page.
- Lookup. Up to 50 products by id at once, or one product in full: price range, variants and options, images, category, brand, list price, delivery, and the product facts and answers you have approved.
- Availability. Stock and delivery to an Indian pin code for products; free rooms and each rate’s total for check-in and check-out dates, up to 30 nights, for hotels; free table times for a date and party size for restaurants.
- Scope. You choose whether Google sees all your items, or only some categories or room types.
- Checks on every caller. Calls are limited per assistant, and a caller that claims to be a known AI crawler from outside the address ranges its maker publishes is refused.
UCP checkout
How do UCP checkout sessions work?
A checkout session is the order an agent builds with your store: the lines, the buyer and the delivery address, priced by your store with delivery and tax. The agent creates it, updates it as the buyer decides, and completes it when the buyer says yes.
Create
The agent opens a session with the products and quantities. Anything still missing, such as a delivery address, comes back as a plain message.
Update
The agent sends the session again with the buyer’s details and address. Once nothing is missing, your store reads it back with its own prices, delivery and tax.
Complete
The total is checked again just before the buyer confirms. If it has changed, nothing is created and the session shows the new total.
Pay on your page
The session sends the buyer to your own checkout with the bag filled in. When they pay, the order exists in your store and has its own page.
Or cancel
The agent can cancel a session that has not completed, and nothing is ordered.
Hotels: booking sessions
Hotels use UCP’s lodging capability, which is still a draft. One stay per booking session, priced at your public rates by your own booking engine and your deposit rule. The guest pays the deposit on your own deposit page and the room is held until then; if it is not paid in time, the room is released.
Restaurants: your own menu
Menu orders are not taken inside Google. The agent can check free table times and send diners to your own menu page, where they order and pay.
Trust
How are Google’s requests verified with RFC 9421?
Every checkout and booking call from Google must carry an HTTP message signature, the IETF standard RFC 9421, made with a key Google publishes in its own UCP profile. WatEase checks the signature and the request body’s digest before the call is allowed to create or change anything.
- Keys from the caller’s profile. The key is read over HTTPS from the calling platform’s published profile, and only platforms trusted as Google are accepted.
- The body cannot be altered. The request’s Content-Digest (RFC 9530) must match its body, so a signed request cannot be changed on the way.
- Standard algorithms. ES256 signatures, with ES384 and Ed25519 accepted too.
- Refused means nothing happens. A missing, invalid or unknown-key signature is refused with UCP’s own error codes, before anything is created.
Why it matters: a checkout session reads back an order and hands out a payment page, and a hotel booking holds a room. Signatures make sure only Google’s agent can do that in your store’s name.
Payment
Where does the buyer pay?
On your own checkout. Paying inside an AI assistant is not open to Indian shoppers yet, so every completed session hands the buyer to your own payment page with the bag already filled in.
That keeps what matters to you where it is today: your payment gateway (Razorpay, PhonePe, Easebuzz or Breeze 1-click checkout, with Stripe or ICICI Bank switched on when the business needs them), your settlement, your GST invoice and your customer record. Prices are read again on your website, so the buyer always pays your store’s price.
The links Google’s agent hands the buyer are signed, expire, and carry the assistant’s name, so every order or booking they lead to is credited to Google AI Mode and Gemini in your numbers.
On WatEase
How does WatEase implement UCP?
WatEase runs UCP for your store: the profile, the catalogue calls, checkout sessions and signature checks are built in, and it is switched on per business. You choose what Google may see and whether its agent may take orders, and you can switch either off at any time.
Off until you switch it on
Nothing is shared until the store agent is on for your account and you switch Google on. Each switch is per business.
Two switches
“Show my items in Google’s AI answers” lets Google read your catalogue. “Take orders inside Google”, or “Take bookings” for a hotel, lets its agent read orders back.
Live, never stored
Prices, stock and delivery are read from your catalogue at the moment Google asks, and read again on your website at checkout.
Only what you choose
Names, pictures, descriptions, prices, availability and links, for all items or only some categories or room types. Never your customers, orders or costs.
Hotels and restaurants too
Free rooms and each rate’s total for a stay, deposits on your own page, and free table times for a party; menu orders finish on your own menu page.
Your numbers
Visits from Google’s answers, how often it read your items, checkout links tapped, orders or bookings, and what they were worth.
The same catalogue also feeds your own agents and your online store, so a product you change once is changed everywhere. See every AI agent that works from it.
Compared
UCP vs ACP: how do they differ?
UCP is Google’s protocol for AI Mode and Gemini; ACP, the Agentic Commerce Protocol, is OpenAI’s for ChatGPT. UCP has the assistant call your store live, while ACP starts from a product feed you send to OpenAI.
| Question | UCP (Google) | ACP (OpenAI) |
|---|---|---|
| Assistants | Google AI Mode and the Gemini app | ChatGPT |
| How products are found | Your UCP profile at /.well-known/ucp, then live calls to your catalogue | A product feed, one line per item, sent to OpenAI as a full snapshot at least once a day |
| Prices and stock | Read live at every call | As of the last feed, and read again on your website at checkout |
| Checkout | Checkout sessions for a web store; booking sessions for hotels (a draft) | Agentic Checkout sessions for a web store |
| How calls are checked | HTTP message signatures (RFC 9421) against keys Google publishes | A key WatEase issues to OpenAI, with an optional body signature |
| Where an Indian buyer pays today | On your own checkout | On your own website |
| On WatEase | Switched on per business | Ready for ChatGPT (ACP) when switched on |
Most businesses want both. WatEase runs them from the same catalogue, you switch each assistant on separately, and each one’s orders appear on their own line. The wider picture is on agentic commerce, explained.
Getting listed
How do you get listed on Google AI Mode and Gemini?
You need a store Google can buy from, a catalogue Google knows, and the switch that lets its agent call your store. On WatEase that is five steps, and none of them needs code.
Sell on your own website and domain
Put your products, rooms or menu on your WatEase storefront and connect your own domain: your UCP profile is published at /.well-known/ucp on that domain.
Switch on the store agent
WatEase switches the store agent on for your account when you ask; you then turn it on under Store agent, Jobs and limits.
Keep your catalogue in Google Merchant Center
WatEase keeps your products in sync with Merchant Center, which is how Google lists your items in India today.
Switch Google on
On the AI assistants page, switch on “Show my items in Google’s AI answers” and choose all items or only some categories.
Decide on checkout
Switch on “Take orders inside Google” (or “Take bookings” for a hotel) if you want Google’s agent to read back orders. Buyers still pay on your website.
Google decides where and how your items appear in its answers. Switching UCP on makes your store ready for its agent; it does not buy a place in the results.
Questions
Frequently asked questions
Do I need my own domain to use UCP?
Yes. Google’s agent reads the UCP profile at /.well-known/ucp on your store’s own domain, so WatEase publishes it on the custom domain your storefront runs on. A domain that is not connected and working gets no profile.
Can shoppers pay inside Google AI Mode in India?
Not yet. Paying inside an AI assistant is not open to Indian shoppers, so Google’s agent hands the buyer to your own checkout with the bag filled in, and they pay through your own payment gateway: Razorpay, PhonePe, Easebuzz or Breeze 1-click checkout, with Stripe or ICICI Bank switched on when the business needs them. Nothing is charged inside Google.
What does Google see from my store?
Only what you switch on. Google can read your items’ names, pictures, descriptions, prices, availability and links to your website, for all items or the categories you choose. It never sees your customers, orders or costs.
Does UCP replace Google Merchant Center?
No. In India today Google lists your items through Merchant Center, and UCP lets its agent check live price and stock with your store and start a checkout. WatEase keeps Merchant Center in sync and runs the UCP side for you.
What is RFC 9421, and why does UCP use it?
RFC 9421 is the IETF standard for HTTP message signatures: the sender signs parts of a request with a private key, and the receiver checks the signature with the published public key. UCP uses it so a store can be sure a checkout call comes from the platform it names, and WatEase refuses any checkout or booking call without a valid signature.
Can a hotel take bookings through UCP?
Yes, through UCP’s lodging capability, which is still a draft. Google’s agent can check free rooms and rates for dates and open a booking session priced at your public rates; the guest pays the deposit on your own deposit page, and the room is held until then.
How is UCP different from ACP?
UCP is Google’s protocol and has its agent call your store live; ACP, the Agentic Commerce Protocol, is OpenAI’s and starts from a product feed you send. WatEase supports both from one catalogue: UCP is switched on per business, and your store is ready for ChatGPT (ACP) when switched on.
How do I switch UCP off?
Switch Google off on the AI assistants page. From that moment Google can no longer read your items, and taking orders inside Google stops with it; you can switch it on again whenever you like.
Be ready
Be ready when shoppers ask an AI.
Your own storefront, a UCP profile on your domain and a catalogue Google’s agent can read live, with every order finished on your own checkout.
Questions first? Chat on WhatsApp (opens in a new tab) or book a demo.
- 0% markup on WhatsApp messages
- Add modules as you grow
- Set up in minutes
- Guided onboarding included
