Example: Nilgiri Tea House, end to end

Meet Nilgiri Tea House

Nilgiri Tea House is the example merchant we run in production so that you can see OACP working end to end. It sells loose-leaf teas, a gift sampler and a few tea accessories from a (made-up) store in Ooty, in the Nilgiri hills.

Here is what is switched on for it today.

Try it yourself in two minutes

You need no account. Any computer with curl, or just a web browser for the first step, will do.

1. 1Open the shop's profile

   Visit https://nilgiritea.agenticorg.ai/.well-known/ucp in your browser. This is the file every buyer agent reads first. It names the UCP version, where to send requests and what the shop can do.

2. 2Search the catalog

   Send the search below with the word chai. The shop answers with its Masala Chai Blend, its price in paise and whether it is in stock.

3. 3Search for something else

   Try green, kettle or an empty query for all 10 products. One tea, the Blue Mountain Oolong, is sold out on purpose, so you can see how stock is shown.

The profile, shortened:

curl -s https://nilgiritea.agenticorg.ai/.well-known/ucp

{
  "ucp": {
    "version": "2026-04-08",
    "services": {
      "dev.ucp.shopping": [
        { "transport": "rest", "endpoint": "https://nilgiritea.agenticorg.ai/ucp" }
      ]
    },
    "capabilities": {
      "dev.ucp.shopping.catalog.search": [ ... ],
      "dev.ucp.shopping.checkout": [ ... ],
      "dev.ucp.shopping.ap2_mandate": [ ... ]
    }
  },
  "signing_keys": [ { "kty": "EC", "crv": "P-256", ... } ]
}

The search:

curl -s -X POST https://nilgiritea.agenticorg.ai/ucp/catalog/search \
  -H 'Content-Type: application/json' \
  -d '{"query":"chai","context":{"currency":"INR"}}'

{
  "products": [
    {
      "title": "Masala Chai Blend",
      "description": { "plain": "Synthetic demo product. Black tea with cardamom, ginger, clove and cinnamon." },
      "variants": [
        {
          "sku": "NTH-MASALA-250",
          "title": "250 g",
          "price": { "amount": 44900, "currency": "INR" },
          "availability": { "available": true, "status": "in_stock" }
        }
      ]
    }
  ],
  "pagination": { "has_next_page": false, "total_count": 1 }
}

Prices are in the smallest unit of the currency, so 44900 means ₹449.00. The whole shelf looks like this:

Part 1. How the shop was set up

These are the steps behind Nilgiri Tea House, in order. For the demo, a setup script runs them in one go, calling the same AgenticOrg functions the dashboard uses. For your shop, you do them on the Commerce Runtime and Custom Domains pages. The detail of each step is in the Merchant setup checklist.

1. 1
   Create the merchantOwner: Merchant

   The shop got its own tenant, an administrator and a merchant record: merchant ID nilgiri_tea_house and seller agent seller_agent_nilgiri_tea. For you: sign up, then save your merchant settings on Commerce Runtime.

   Blocked / exception

   You need the administrator or merchant role.

2. 2
   Load the catalogOwner: Merchant

   Its 10 products, prices and stock went in, plus one store with opening hours. A real shop connects Shopify read-only and runs a sync instead.

   Blocked / exception

   A missing Shopify credential or a wrong store domain stops the sync and says why.

3. 3
   Set purchase limitsOwner: Merchant

   The largest order, the allowed currency (INR) and the most items per order. For you: the same fields in your merchant settings.

   Blocked / exception

   Without limits the arbiter refuses every purchase with merchant_limits_missing.

4. 4
   Get the facts signedOwner: Platform operator, then merchant

   The operator added the shop to the Grantex allowlist. AgenticOrg then asked Grantex to sign the catalog, prices, stock, policies and capabilities, and got 11 signed artifacts back.

   Blocked / exception

   Grantex answers unavailable until your tenant is on its allowlist.

5. 5
   Check every signatureOwner: AgenticOrg

   AgenticOrg checked each artifact's signature, key, expiry and revocation status before keeping it. All 11 passed.

   Blocked / exception

   A refusal names the reason, for example revocation_status_unavailable; nothing from that batch is kept.

6. 6
   Create the signing keyOwner: Merchant

   One signing key for the shop. Its public half is published in the profile, so agents can check the shop's own answers.

   Blocked / exception

   Publishing is refused with signing_key_missing until the key exists.

Part 2. Its own address

Buyer agents need a web address to find a shop. Nilgiri Tea House uses nilgiritea.agenticorg.ai. Your shop would use a subdomain you own, such as agent.your-store.example.

7. 7
   Ask for the challengeOwner: Merchant

   AgenticOrg issued a one-time code for nilgiritea.agenticorg.ai and showed the TXT record to create. On Custom Domains you see the same thing, with copy buttons.

   Blocked / exception

   An IP address or a one-word host is not accepted.

8. 8
   Add the two DNS recordsOwner: Merchant

   A CNAME from nilgiritea to ghs.googlehosted.com, and the TXT record _agenticorg-ucp.nilgiritea with the code. Your own domain also needs one Search Console owner; see the custom domain guide.

   Blocked / exception

   DNS changes can take up to an hour to show; check again later.

9. 9
   Verify and publishOwner: AgenticOrg and Grantex

   AgenticOrg looked the TXT record up, matched the code and linked the address to the shop. The shop opted in to public discovery, Grantex allowed it, and the profile went live.

   Blocked / exception

   The page lists each failed check with its fix, for example serving_host_not_attested.

10. 10
    CertificateOwner: Google

    Google issued the HTTPS certificate for the address. That usually takes 15 minutes and at most 24 hours.

    Blocked / exception

    After 48 hours without a certificate, check CAA records and that the CNAME is DNS only.

Full instructions for your own domain, including every check and its fix, are in Your own domain for buyer agents.

Part 3. A buyer agent shops

This is what happens when an AI shopping agent buys tea for someone.

11. 11
    DiscoverOwner: Buyer agent

    The agent reads /.well-known/ucp and learns the address of the shop's API and which UCP features it supports.

    Blocked / exception

    A 404 means the profile is not published, or its signed facts have lapsed and could not be renewed.

12. 12
    SearchOwner: Buyer agent

    The agent searches for chai and gets the Masala Chai Blend at ₹449, in stock. The answer comes only from verified facts.

    Blocked / exception

    A catalog_unavailable message means the verified facts lapsed and could not be renewed; nothing is guessed. Try again shortly.

13. 13
    Open a checkoutOwner: Buyer agent

    The agent creates a checkout for NTH-MASALA-250, quantity 1, using the API key the merchant issued to its platform. The shop prices it from the same verified facts.

    Blocked / exception

    Without a valid key the shop answers 401.

14. 14
    Get mandatesOwner: Grantex

    Grantex issues three signed mandates: what the buyer allowed (Intent), this exact cart (Cart) and the amount and payment rail (Payment).

    Blocked / exception

    A mandate is refused when it goes beyond what the buyer allowed.

15. 15
    DecideOwner: AgenticOrg arbiter

    The arbiter applies its fixed rules, such as the shop's limits and the mandates, and answers allow or refuse. The decision is sealed in the ledger.

    Blocked / exception

    A refusal names the first rule that failed; nothing is charged.

16. 16
    PayOwner: Payment provider

    With live payments on, the payment provider would charge once, only on allow. In this demo payments are off: a checkout can be decided, but completing it answers executor_unavailable and nothing is charged.

    Blocked / exception

    Live payment stays off until a payment-provider sandbox run has passed.

For an agent platform, the checkout request looks like this. The key and the platform profile are your own.

curl -s -X POST https://nilgiritea.agenticorg.ai/ucp/checkout-sessions \
  -H "X-API-Key: $PLATFORM_KEY" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H 'UCP-Agent: profile="https://your-agent-platform.example/.well-known/ucp"' \
  -H 'Content-Type: application/json' \
  -d '{"line_items":[{"item":{"id":"NTH-MASALA-250"},"quantity":1}]}'

Every step of the mandates, the passkey and the decision is in A purchase, step by step.

Do the same for your shop

Most steps take a few minutes. Waiting for DNS and the certificate usually takes the longest.

What this demo does not do

• No real products or customers. Every product, price, store and address is synthetic, and each product description starts with "Synthetic demo product".
• No money moves. Live payments are off, and the demo has no payment provider attached.
• No shipping rates. Delivery rates need a real Shopify shop. The demo is for discovery, search and checkout decisions.
• No store-location search yet. Store locations are part of UCP 2026-08-25. The shop serves UCP 2026-04-08, so a location search answers that the feature is not served.

Read next

• Merchant setup checklist
• Your own domain for buyer agents
• A purchase, step by step
• What OACP is and why you need it