Commerce Gateway

MCP for AI agents — connect Claude, Grok, or Gemini to your supply chain.

Commerce Registry vs Registry MCP

Registry MCP is the discovery protocol. Commerce Registry is the product surface.

Why loop constraints matter

The gateway exposes loop state over MCP/SSE. Because loops are finite state machines with explicit transitions and guardrails, AI agents operate inside deterministic boundaries.

AI agents can

Use read scopes to inspect operations and recommend actions.

Query loop state
Surface exceptions
Recommend next actions
Read demand and inventory position

AI agents cannot by default

Write transitions are blocked unless explicit `gateway-write` scope is granted.

Snippet

{ "mcpServers": { "betterdata": { "url": "https://api.betterdata.co/gateway/{org-slug}", "transport": "sse" } } }

Recent Commerce Gateway releases

View Commerce Gateway changelog

Commerce GatewaydocsApr 8, 2026

Commerce Gateway — registry protocol documentation

Commerce Registry Protocol: registration, verification, and discovery documentation updates.

Govern

commerce-gateway

registry

Commerce Gateway0.1.0Mar 28, 2026

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.