Protocols

One commerce layer. Every agent ecosystem.

We do not build the company around a single AI ecosystem. Capabilities are modelled once and mapped to whichever protocols your channels actually support.

Honest status

We never convert “unknown” into “failed”.

Every protocol surface is reported with one of these labels: Supported, Detected, Connected, Available, Not detected, Requires implementation, Not tested, Unknown. We do not claim official certification or compatibility unless it has actually been validated.

UCP

Universal Commerce Protocol surfaces

Available

Publish structured commerce capabilities so agents can retrieve catalogue, availability and delivery facts through a defined interface.

MCP

Model Context Protocol

Available

Expose merchant tools and resources to assistants through an MCP server built on your normalized commerce data.

ACP

Agentic checkout surfaces

Not detectable

Private or platform-managed checkout integrations are typically not publicly observable, so we report them as unknown rather than failed.

A2A

Agent-to-agent interaction

Requires implementation

Structured request and response contracts between a shopping agent and a merchant-side agent, including negotiation of availability and delivery.

AP2-related

Authorized agent payment flows

Not tested

Payment authorization flows for agent-initiated purchases. We never design or execute unauthorized autonomous payments.

Platform-native

Shopify, WooCommerce, Magento capabilities

Supported

Where your platform already ships agentic or feed capabilities, we configure, validate and monitor them instead of rebuilding them.

Find out what is detectable on your store today.

The free scan reports which agent-facing surfaces are publicly discoverable and which ones would require implementation.