Measured the gap between today’s storefront and what an agent needs to transact.

The Commerce Agent walks every catalog endpoint, every checkout step, every webhook, and scores it against the ACP and UCP specifications. For FieldDay the readout was clean and concrete: catalog feed mostly compliant, checkout missing 4 required surfaces, returns/cancellations entirely undefined for agentic flows.

Simulated agent checkouts against a sandbox endpoint: every flow before any flow goes live.

Before any production credential is issued, the OS runs synthetic agent flows: discover → select variant → add to cart → authenticate as agent → settle → confirm → handle refund/return. Every flow carries the protocol version, the conformance log, and the specific surface that broke.

• Sandbox endpoints provisioned per protocol: ACP and UCP in parallel
• Synthetic agent personas test variants, returns, partial fulfilment, sub-agents
• Conformance log retained per run for the merchant compliance team

Shipped the bindings: feed schema, checkout webhook, agent auth, structured returns.

The Commerce Agent drafts the field-level mapping (live catalog ↔ ACP/UCP fields), the webhook payloads, the agent-auth handshake, and the structured-return contract. The merchant commerce team approves the diff; the OS pushes it through the existing storefront platform integration.

• Catalog feed → ACP product schema mapping (auto-generated, merchant-approved)
• Checkout webhook bound to the protocol settlement event
• Agent-auth handshake + scope tokens shipped with audit log
• Structured returns/cancellations contract: the surface most merchants miss

Compounded: ACP/UCP enablement is now a templated workflow on the platform.

FieldDay was the first. The mapping the Commerce Agent drafted, and the conformance battery the OS ran against the sandbox, is now the same workflow any merchant can trigger when they’re ready. As the protocols evolve the OS holds the spec; the merchant holds the storefront. Two parties, one Loop.