Better Data

Integrations

Commerce Gateway

Edit this page

Commerce Gateway

Commerce Gateway is controlled operational connectivity: governed access so LLMs and other clients can use tools against your commerce and chain data — with policy, attribution, and Loop Engine decision control where required. Buyers choose safe AI participation and operational integrations, not “MCP infrastructure” as the headline.

Protocols (MCP over SSE, API keys, sessions) and registry discovery are how connectivity works; see MCP surfaces for the canonical deployment map. Narrative and positioning: Commerce Gateway on betterdata.co.

Surfaces: How gateway-console, Registry MCP, and hosted gateway MCP differ is documented in MCP surfaces (canonical system reference).

Commerce Agent (C9): In Better Data messaging, Commerce Agent names the composition pattern — discover (Registry MCP) → execute (Commerce Gateway) → govern (Loop Engine) → recorded outcome; demos are reference experience only. It is not a standalone product. See Commerce Agent pattern.

C12 — Agent language: Always say agents use Registry to discover, Gateway to act, Loop Engine to govern. Never describe agents as an autonomous AI platform, agent product, or a system separate from the gateway. Build a governed commerce agent →

What it is

Commerce Gateway (@commercegateway/commerce-gateway in bd-forge — see OSS overview) is the agent-facing controlled connectivity layer for product search, availability, cart, and order operations, with capability-gated tool access.

Read operations are the default posture. Write-capable tool paths require explicit capability and key scope enablement.

Implementation: federated connectivity

AI agent or integration → MCP client → SSE (or configured transport) → Commerce Gateway → domain backends → your operational data.

Gateway discovery can be registry-assisted; gateway execution remains org-scoped and governed by your policies.

Getting started

  1. Enable gateway access

    Enable your organization gateway and assign API key scopes.

  2. Get your endpoint

    Endpoint format: https://gateway.betterdata.co/gateway/{orgSlug}.

  3. Connect your MCP client

    Configure your client with SSE transport and your scoped API key.

Claude MCP configuration (example)

1{
2  "mcpServers": {
3    "betterdata": {
4      "url": "https://gateway.betterdata.co/gateway/{your-org-slug}",
5      "transport": "sse"
6    }
7  }
8}

Available MCP tools

Verified from packages/commerce-gateway/src/mcp/tools/index.ts:

  • shop
  • search_products
  • get_product_details
  • check_availability
  • check_inventory
  • get_recommendations
  • add_to_cart
  • create_order
  • get_shipment_status
  • get_purchase_order_status
  • get_trace_events
  • get_demand_forecast

Registry discovery

Use registry discovery to resolve gateways before execution where applicable:

Security

  • Authenticate with scoped API keys (x-api-key or gateway auth middleware path).
  • Restrict high-impact scopes to trusted agents and environments.

Hosted vs self-hosted

| | Self-hosted | Better Data hosted | | - | ----------- | ------------------ | | Setup | gateway-console (free operator UI) + your stack | No gateway infrastructure to run | | Multi-tenant | Single-tenant OSS default | Multi-tenant org isolation | | Registry | Optional (Commerce Registry Protocol) | Included in platform discovery flows | | Analytics | Local / self-managed | Full dashboard (hosted product) | | SLA | Self-managed | Target enterprise SLA — see agreement |

Self-hosted docs: commercegateway.io
Hosted: gateway.betterdata.co · hello@betterdata.co

Resources