Make your storefront agent-ready
AI shopping agents — Google AI Mode and Gemini, Microsoft Copilot, ChatGPT, Perplexity, Claude and custom agents — discover and buy from Traide marketplaces through endpoints that Traide hosts for your tenant. You keep building your storefront and checkout exactly as you do today; this page lists the few, optional things that only work on your domain and how to wire them up.
The tenant agent host (https://<your-slug>.agents.thetraide.com) and the /agent/* endpoints described here are being rolled out under SPEC-031. Your Traide representative will confirm when your tenant's host is live. Everything in the Structured data and robots.txt sections works today.
What agents see
| Surface | Where it lives | Who serves it |
|---|---|---|
UCP business profile (/.well-known/ucp) — capabilities, endpoints, payment handlers, signing keys | https://<slug>.agents.thetraide.com/.well-known/ucp | Traide |
| Checkout and order endpoints agents call to buy | https://<slug>.agents.thetraide.com/ucp/v1/… | Traide |
Sitemap and llms.txt for crawlers and LLMs | https://<slug>.agents.thetraide.com/agent/sitemap.xml, …/agent/llms.txt | Traide |
| Product feeds for Google, Microsoft, OpenAI | pushed by Traide (Phase 4) | Traide |
Product pages, structured data, robots.txt, the checkout a buyer lands on when an agent hands off | your storefront | You |
Nothing below is required for agents to buy from you through Traide's endpoints. Each item improves discovery or the hand-off experience.
1. Redirect /.well-known/ucp to your agent host
Agents that start from your website URL look for the profile on your domain. A single redirect points them at Traide:
301 https://www.example.com/.well-known/ucp → https://<slug>.agents.thetraide.com/.well-known/ucp
You can do the same for /llms.txt → …/agent/llms.txt and /sitemap.xml → …/agent/sitemap.xml if you don't already publish your own.
Cloudflare — Rules → Redirect Rules → When URI Path equals /.well-known/ucp → Then Dynamic redirect, expression concat("https://<slug>.agents.thetraide.com", http.request.uri.path), status 301.
Vercel (vercel.json):
{ "redirects": [ { "source": "/.well-known/ucp", "destination": "https://<slug>.agents.thetraide.com/.well-known/ucp", "permanent": true } ] }
Netlify (_redirects):
/.well-known/ucp https://<slug>.agents.thetraide.com/.well-known/ucp 301
nginx:
location = /.well-known/ucp { return 301 https://<slug>.agents.thetraide.com/.well-known/ucp; }
Next.js (next.config.js):
async redirects() {
return [{ source: '/.well-known/ucp', destination: 'https://<slug>.agents.thetraide.com/.well-known/ucp', permanent: true }]
}
Remix / Express (server.js):
app.get('/.well-known/ucp', (_req, res) => res.redirect(301, 'https://<slug>.agents.thetraide.com/.well-known/ucp'))
2. Allow AI agents in robots.txt
Agents identify themselves with their own user agents. Allow the ones you want and point them at a sitemap:
User-agent: GPTBot
User-agent: OAI-SearchBot
User-agent: ChatGPT-User
User-agent: ClaudeBot
User-agent: Claude-User
User-agent: PerplexityBot
User-agent: Google-Extended
User-agent: Amazonbot
User-agent: meta-externalagent
User-agent: Applebot
Allow: /
User-agent: *
Disallow: /cart
Disallow: /checkout
Disallow: /account
Sitemap: https://www.example.com/sitemap.xml
Keep /cart, /checkout and /account disallowed — agents buy through Traide's endpoints, not by crawling your checkout.
3. Structured data on product pages
Agents and crawlers read Schema.org JSON-LD. Traide's own storefront emits it, and yours should too. The fields map onto the same GraphQL data your product page already loads:
| JSON-LD | GraphQL source |
|---|---|
name, description | product.name, product.description |
image (absolute URLs) | product.thumbnail.url, product.images[].url |
sku | variant.sku |
offers.price, offers.priceCurrency | variant.pricing.price.gross.amount (decimal) / .currency — or gross.baseAmount if you already work in minor units |
offers.availability | product.isAvailable → https://schema.org/InStock / OutOfStock |
offers.seller | product.seller.companyName (marketplaces: one Offer per seller, or an AggregateOffer) |
offers.url | the product page URL |
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Handwoven terracotta rug",
"description": "Wool, 8x10, warm tones.",
"image": ["https://www.example.com/media/rug-1.jpg"],
"sku": "RUG-12345",
"offers": {
"@type": "Offer",
"url": "https://www.example.com/product/handwoven-terracotta-rug",
"price": "150.00",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock",
"seller": { "@type": "Organization", "name": "Terracotta Studio" }
}
}
</script>
On collection, category and search pages add an ItemList whose itemListElement entries link to the product pages. Validate with Google's Rich Results Test.
4. Receive an agent checkout (continue_url)
The continue URL template, the sig/exp parameters and the hand-off secret ship with SPEC-031 Phase 1. Nothing to build until your Traide representative confirms they are available for your tenant — the section is here so you can plan the landing page.
When an agent cannot finish a purchase on its own — a promo code that needs review, a compliance disclosure the agent can't render, a payment that needs 3-D Secure — it hands the buyer to a URL you configure in the dashboard, the continue URL template:
https://www.example.com/checkout?token={checkout_token}&sig={sig}&exp={exp}
The agent's checkout is an ordinary Traide checkout, so your page just loads it with the same query it uses today:
query ResumeCheckout($token: NauticalUUID!) {
checkout(token: $token) {
id
email
lines { id quantity variant { id name } }
shippingAddress { firstName lastName streetAddress1 city postalCode country { code } }
totalPrice { gross { amount currency } }
}
}
Verify sig before trusting the token: it is an HMAC-SHA256 of "{checkout_token}|{exp}" using the agent hand-off secret shown in the dashboard, hex-encoded; reject the request if exp (a Unix timestamp) is in the past. Guest checkouts need no login. Completing the checkout on your page closes the agent session and notifies the platform the buyer started from — no extra call is needed.
5. Check your readiness
The readiness check ships with the dashboard's Agentic commerce settings page in SPEC-031 Phase 1.
The dashboard's Agentic commerce page runs a readiness check against your configured storefront URL and reports, for each item above, whether agents will find it — with the fix snippet for anything missing.