Part of Better Data's open operational infrastructure. Use standalone or with Commerce Chain Optimization.
See Commerce Chain Optimization →When an AI agent needs to call commerce operations for a brand — find products, check inventory, start a checkout — it needs to know two things: where the gateway is, and whether it can be trusted. The Commerce Registry answers both.
Commerce Gateway Registry is the verified commerce identity layer for AI agents. Not a general MCP directory. A commerce-specific trust registry where brands prove domain ownership and attach product-line claims — so any AI agent knows it's talking to the real store, not a spoofed endpoint.
Free to register during open beta.
Free during open beta. Registration in the Better Data public registry at registry.betterdata.co is free. No credit card required.
Browse verified commerce gateways at registry.betterdata.co.
Registered gateways show:
The registry is not a walled garden. It implements the open Commerce Registry Protocol — any compliant registry deployment can interoperate. Better Data operates a hosted public registry. You can self-host your own.
The key distinction: a gateway listed in the registry is verified. Verification means you have proven control of the brand domain where the gateway runs — not just that you published a file.
Why verification matters to AI agents
Unverified gateways (.well-known only) are discoverable but flagged as lower trust. Verified gateways have proven domain control — agents and resolvers treat these as authoritative for that brand's commerce operations. For production use, always complete full verification.
| Trust tier | How it works | Agent treatment |
|---|---|---|
| ✅ Verified | Domain proof + registry listing | Authoritative — treated as the brand's canonical gateway |
| ⚠️ Unverified | .well-known file only | Discoverable but not authoritative |
Host /.well-known/commerce-gateway.json on your domain. Resolvers that implement the protocol can find you via well-known fallback. The spec treats this as unverified until you complete registry registration.
Free during open beta. Registration in the Better Data public registry at registry.betterdata.co is free. No credit card required.
The registry issues a verification token when you register. Complete verification using either method.
_commerce-gateway.{your-domain} with value: {your-token}DNS changes may take up to 48 hours to propagate.
https://{your-domain}/.well-known/commerce-gateway-verify.json with content: { "token": "{your-token}" }The file must be served over HTTPS on the exact registered domain.
Without a verified registry, an AI agent connecting to commerce tools has no way to confirm it's reached the legitimate gateway for a brand. The registry provides:
This is the same trust model DNS provides for web browsing — but for AI-accessible commerce infrastructure.
After your gateway is verified, you can attach GS1 / GTIN claims to associate product lines with your gateway. Submit a certificate or proof URL per claim. POST /api/gateways/{id}/gtins
The default hosted registry for the Commerce Gateway ecosystem. Register your gateway, complete domain verification, and appear in the public directory at registry.betterdata.co.
Free to register. No hosting or Better Data account required to list. A Better Data account unlocks the hosted console, analytics, and managed gateway infrastructure.
REGISTRY_URL: https://registry.betterdata.co
Deploy your own registry using the Commerce Registry Protocol. Full control. Interoperable with any compliant implementation.
The open registry protocol is published and versioned. Build your own compliant registry or resolver.
Browse and resolve gateways via the public registry API at registry.betterdata.co. Use the setup guide to register your gateway for verified listing.
| Goal | What to do |
|---|---|
| Verified gateway in a registry | Register + DNS TXT or .well-known token verify |
| Gateway discovery without a registry | Publish /.well-known/commerce-gateway.json |
| Attach product-line proof | POST /api/gateways/{id}/gtins after registration |
| Point at a different registry | Set REGISTRY_URL in your gateway config |
| Run your own registry | Deploy a Commerce Registry Protocol server |