Reference
Commerce Agent names a single composition pattern across Better Data surfaces. It is not a workspace module, not a product SKU, not a billable “agent” tier, and not primary navigation.
Do not ship “Commerce Agent” as a standalone product, pricing line, or Core Modules card. Use this page and @repo/analytics/taxonomy (COMMERCE_AGENT_PATTERN_*) as the only definition.
Commerce Agent =
| Phase | Surface | Role |
| ----- | ------- | ---- |
| Discover | Registry MCP | Resolve brands, GTINs, @shop — discovery protocol and tools |
| Execute | Commerce Gateway | Tool calls against org-scoped commerce data (MCP / SSE) |
| Govern | Loop Engine | Policies, guards, audit, loop completion |
| Surface (experience) | Demo | Gateway Demo or Commerce Demo — reference experiences only |
| Outcome | Recorded state | Evidence, audit trail, loop outcome — not a separate “agent database product” |
The Commerce Registry workspace is where listing and verification connect to discovery; Registry MCP is what remote MCP clients use for protocol-level discovery — see MCP surfaces.
1Agent2 ↓3Registry MCP (discover)4 ↓5Commerce Gateway (execute)6 ↓7Loop Engine (govern decisions)8 ↓9Recorded outcome / stateExperience layer (optional, reference only): after governance is understood, Gateway Demo and Commerce Demo illustrate the same stack for humans — they are not an extra runtime hop for every request.
commerce_agentsThe onboarding intent commerce_agents (see sign-up) emphasizes Commerce Gateway and related protocol work. It aligns with the execute step of this pattern — it does not introduce a separate “Commerce Agent product.”
