STEP 1
Run the gateway
Self-host or use Better Data hosted — same protocol, one unified system. Configure connectors and auth in your workspace; external MCP endpoints come after setup.
Part of Better Data's open operational infrastructure. Use standalone or with Commerce Chain Optimization.
See Commerce Chain Optimization →Commerce Gateway is an open protocol and self-hostable server that lets any AI agent — Claude, GPT-4o, Grok, Gemini — call typed commerce tools and data through one consistent tool interface. Pair it with Commerce Registry for discovery; both are first-class in the Better Data workspace (self-host and OSS paths use the same protocol).
Commerce Gateway is the operational connectivity layer for Better Data's hosted platform and self-hosted commerce chain deployments.
import { AnthropicAdapter } from "@commerce-gateway/sdk/adapters";
const adapter = new AnthropicAdapter({
apiKey: process.env.ANTHROPIC_API_KEY!,
tools: ["search_products", "get_product_details"],
});
const result = await adapter.handleRequest({
model: "claude-sonnet-4-6",
messages: [{ role: "user", content: "Find running shoes under $100" }],
});
// Same AnthropicAdapter + handleRequest pattern as the quick startCommerce Registry (discovery) is a native platform capability — configure it in Better Data alongside the gateway; docs here describe the open protocol for self-hosted and OSS deployments.
STEP 1
Self-host or use Better Data hosted — same protocol, one unified system. Configure connectors and auth in your workspace; external MCP endpoints come after setup.
STEP 2
Wire Shopify, custom APIs, or any HTTP backend. The gateway normalizes tool schemas so Claude, GPT-4o, Grok, and Gemini all speak one interface.
STEP 3
The Commerce Demo is a developer accelerator — a reference app, not a separate product. Use it to validate flows before you ship your own UI.
STEP 4
Layer Loop Engine on actions executed through the gateway for approvals, guards, and audit — governance as a control layer, not a standalone bot.
Works with
Self-host the gateway, use Better Data hosted, or both — registry and setup stay inside a unified platform experience. External endpoints (MCP URLs, connectors) come after you configure the workspace.
Discovery & identity
Publish and resolve gateways inside the same Better Data system — native capability, not a separate signup elsewhere. Protocol docs cover self-hosted and OSS topologies.
How registry fits →Governance & control
Policy, guards, and audit on actions that flow through the gateway. Loop Engine is the control layer — not a parallel automation product.
Loop Engine →Developer accelerator
A reference experience that shows gateway + tools end-to-end. It illustrates integration patterns — not a second control plane or operator surface.
Try the demo →Developer path: (1) run the gateway → (2) connect tools → (3) build on the demo experience → (4) add governance with Loop Engine.
Adapters handle tool schema translation automatically.
tool_use format, streaming supported, multi-turn tool loops
Open docs →function_calling + parallel tool calls, JSON mode
Open docs →OpenAI-compatible API, function calling
Open docs →function_declarations format, Gemini 1.5+ Pro/Flash
Open docs →One schema. All LLMs. Auto-translated.
The Commerce Gateway tool schema covers discovery, cart, checkout, orders, and returns across the commerce lifecycle.
Full control. Apache-2.0 licensed. Run anywhere Node.js runs.
Production-ready. Multi-tenant. Built for scale.
Hosted by Better Data, the team behind Commerce Gateway.