> ## Documentation Index
> Fetch the complete documentation index at: https://betterdatainc.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Commerce Agent pattern

> Canonical composition pattern — discover via Registry MCP, execute via Commerce Gateway, govern via Loop Engine, experience via reference demos. Not a product or module.

# Commerce Agent pattern (C9)

**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.

<Warning>
  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.
</Warning>

## 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](/reference/mcp-surfaces).

## Required diagram

```
Agent
  ↓
Registry MCP (discover)
  ↓
Commerce Gateway (execute)
  ↓
Loop Engine (govern decisions)
  ↓
Recorded outcome / state
```

**Experience 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.

## Primary intent `commerce_agents`

The 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.”

## Messaging QA (C08 / C12)

* **Agent is never presented as a product** (no “agent SKU,” standalone autonomous platform, or agent system separate from the gateway).
* **Agent flow matches everywhere:** Registry (discover) → Gateway (act) → Loop Engine (govern) → outcome; demos and Agent Starter illustrate the same path.
* **Commerce Demo governed mode** reflects that stack (illustrative Loop step — not a second runtime).
* Required CTA label in product and demo surfaces: **Build a governed commerce agent** → [Build an agent](/guides/build-an-agent).

## Related

* [Build an agent (C11)](/guides/build-an-agent) — Agent Starter CLI + config (developer accelerator, example only)
* [Surface contract (C8)](/reference/surface-contract)
* [MCP surfaces](/reference/mcp-surfaces)
* [Core Concepts — Layered ecosystem](/getting-started/concepts#layered-ecosystem-model-canonical)
* [Developer Accelerators](/integrations/commerce-gateway) context: demos are reference only