Commerce Gateway
Connect any LLM to any commerce system - with one integration.
Commerce Gateway is an open-source protocol that solves the LLM integration problem for commerce - Claude, ChatGPT, and Grok each require different tool formats and API patterns. Commerce Gateway defines the universal layer so you integrate once and every MCP-compatible agent gets the full commerce tool surface. It was created by Better Data to power AI agent interactions in the Better Data platform, and developed as independent open infrastructure available to anyone.
Commerce Registry vs Registry MCP
Registry MCP is the discovery protocol. Commerce Registry is the product surface.
MCP surfaces (system reference) — gateway-console, Registry MCP, and hosted gateway MCP.
What is Commerce Gateway?
Commerce Gateway gives LLMs a standard tool interface to any commerce backend.
Instead of building bespoke integrations for every LLM and every storefront, Commerce Gateway defines a universal protocol - a set of typed tools (search, inventory, pricing, orders) that any MCP-compatible agent can call, routed through any connector you configure.
LLM (Claude / ChatGPT / Grok)
↓ MCP / SSE
Commerce Gateway (open source)
↓ connector
Shopify / BigCommerce / ERP / custom
↓
Better Data AI OptimizationWhy we built it
For developers: Every LLM integration requires a different tool format and API pattern. Claude, ChatGPT, and Grok do not share a protocol. Commerce Gateway defines one open protocol - integrate once, support every MCP-compatible agent. The integration problem is not the commerce backend - it is the LLM side.
For discovery: Commerce Registry is a native platform capability for verified gateway listing and resolution — configured alongside your gateway in Better Data, with the same open protocol for self-hosted deployments. It is not a separate external signup product.
Three things are true simultaneously:
- We created it - Commerce Gateway was built and is maintained by Better Data.
- It is open infrastructure - The runtime is Apache-2.0. Your connectors and tool configurations are portable and not locked to our platform.
- Our platform builds on it - Every AI agent interaction in the Better Data CCO platform routes through the same open gateway runtime you can inspect and contribute to.
How it fits into our platform
| Layer | What it is |
|---|---|
| Commerce Gateway (open source) | Protocol layer — tool dispatch, MCP/SSE transport, connectors; Commerce Registry integration for discovery (in-product setup) |
| AI Agent Routing | Better Data proprietary - routes agent requests to the right gateway and merchant |
| CCO Platform | Commerce Chain Optimization - Industry Packs, AI optimization, analytics |
The gateway protocol is open. The AI routing and optimization layer built on top of it is where the Better Data commercial platform lives.
Loop Engine governance
Pair Commerce Gateway with Loop Engine to add human approval gates, guard-enforced policy, and full audit trails to any AI-driven commerce workflow.
Open Source at Better Data
| Project | Description |
|---|---|
| Commerce Gateway | Open protocol for LLM-to-commerce system connectivity |
| Loop Engine | Open runtime for AI-operated enterprise processes |
| Signal Tags Schema | Open schema for verifiable physical-product identity |
| @betterdata/scm-* | Open supply chain primitive packages |
The open protocol. Proven in production.
Recent Commerce Gateway releases
View Commerce Gateway changelogCommerce Gateway — registry protocol documentation
Commerce Registry Protocol: registration, verification, and discovery documentation updates.
Commerce Gateway — initial public release
Commerce Gateway is a self-hosted routing layer that gives any LLM a stable, typed tool surface over your commerce stack — product search, cart operations, order management — without rewiring your integration for each provider or storefront. Initial public release.