Skip to main content

Build an agent (C11 / C12)

Agent Starter is the canonical developer accelerator for composing a Commerce Agent in code: define a goal, reach the registry, execute through Commerce Gateway, apply a Loop Engine–style guard, then return a recorded outcome. C12 — Say it this way: agents use Registry to discover, Gateway to act, and Loop Engine to govern. Do not describe agents as an autonomous AI platform, agent product, or a system separate from the gateway.
Agent Starter is an example (CLI + config in the monorepo). It is not a Better Data product feature, billing SKU, or workspace module.

What you get

The same composition is described in Commerce Agent pattern (C9) and shown interactively in Commerce Demo (governed workflow).

Monorepo package

  • Path: packages/agent-starter
  • Copy agent.config.example.jsonagent.config.json, set GATEWAY_API_TOKEN (or the env name in config), then:
Full README lives next to the code.

Configuration (minimal)

  • Registryregistry.endpointUrl + mode: "httpPing" (GET reachability). Production agents should call Registry MCP tools (@shop, gateway resolution).
  • Gatewaygateway.baseUrl, gateway.bearerTokenEnv, optional queryPath (default /api/gateway/query).
  • Loop guardloopGuard.policy, minConfidence, blockWrites (aligned with the governed demo rail, not a live Loop Engine deployment).