Skip to main content

Agentic Commerce

Agentic Commerce connects store data and operational services to controlled agent workflows. The Store Dashboard provides MCP server management, ACP settings, and a visual Commerce Flow Studio.

MCP Servers​

The MCP area shows active and total server configurations installed for the store. An installed server can include:

  • Name, type, status, and endpoint URL.
  • Health state and configuration details.
  • Associated payment provider.
  • Associated ARP endpoint.
  • Marketplace installation or extension information.

Use Marketplace to install an MCP server template, then review the resulting store configuration before activation.

ACP Configuration​

ACP Configuration stores the Agentic Commerce Protocol settings for the selected store. Treat these settings as store-specific integration configuration. Validate them against the channel and ACP environment used for testing or production.

Commerce Flow Studio​

Flow Studio composes store capabilities into an agentic commerce flow. Available node resources can include:

  • MCP server configurations.
  • Payment provider instances.
  • ARP endpoints.
  • Routers.

Use the editor to connect the required components and save the store flow. Runtime statistics shown by an overview depend on the deployment's telemetry support and should not replace API or end-to-end validation.

  1. Complete catalog and integration readiness.
  2. Install the required MCP servers.
  3. Configure ACP settings for the target channel.
  4. Create ARP endpoints and Router controls.
  5. Register payment providers if the flow needs payment operations.
  6. Open Flow Studio and connect the approved components.
  7. Test tool discovery, authorization, success, denial, and failure paths.
  8. Enable the flow for the intended channel.

Usage Scenarios​

  • Expose catalog search and cart creation to an AI shopping assistant.
  • Connect a procurement agent to supplier and inventory tools.
  • Route different agent capabilities through separate ARP policies.
  • Add a payment provider to an approved checkout or procurement flow.
  • Install a marketplace MCP server for a specialized tool set.
  • Maintain separate flows for pilot and production stores.

Production Controls​

  • Keep credentials outside visual flow metadata.
  • Use least-privilege MCP and API scopes.
  • Validate every external endpoint.
  • Require approval before irreversible actions.
  • Test timeouts, partial failures, and retries.
  • Record the version and owner of the active flow.
  • Maintain a rollback path to the last known-good configuration.