The Commerce Gateway Registry

An open, protocol-native directory of verified AI commerce gateways. Register your gateway once. Discoverable by any agent that speaks the Commerce Gateway Protocol.

Discovery with proof

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.

Verified registration

Higher trust

Deploy your gateway on a public HTTPS URL you control (e.g. api.brand.com)
POST /api/gateways to a protocol-compliant registry with your brand, apex domain, endpoint, protocol version, and capabilities
Complete domain verification — DNS TXT record or hosted .well-known token — to prove domain control
Your gateway is discoverable as verified via the registry resolution APIs

Setup guide →

.well-known only

Lower trust

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.

.well-known spec →

Proving domain control

The registry issues a verification token when you register. Complete verification using either method.

DNS TXT record

Register your gateway — receive a verification token
Add a DNS TXT record at: _commerce-gateway.{your-domain} with value: {your-token}
Call POST /api/gateways/{id}/verify
DNS propagation is checked automatically

DNS changes may take up to 48 hours to propagate.

Hosted verification file

Register your gateway — receive a verification token
Serve this file at: https://{your-domain}/.well-known/commerce-gateway-verify.json with content: { "token": "{your-token}" }
Call POST /api/gateways/{id}/verify
The registry fetches the file and checks the token

The file must be served over HTTPS on the exact registered domain.

Attach product-line proof

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

GTIN claims →

Self-hosted or public registry

Better Data public registry

The default hosted registry. Free to register during open beta.

REGISTRY_URL: https://registry.betterdata.co

Self-hosted registry

Deploy your own registry using the Commerce Registry Protocol. Full control. Interoperable with any compliant implementation.

Self-host docs →

Protocol spec

The open registry protocol is published and versioned. Build your own compliant registry or resolver.

Read the spec →

At a glance

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