Agent-Readable Commerce Surface

also known as Agentic Checkout Surface, Machine-Readable Storefront

Expose a service to agent buyers through a machine-readable product feed and an agent-initiated checkout API rather than a human click funnel, so an agent can discover, compare, and buy against a goal.

Context

Shoppers increasingly delegate buying to agents: an agent is told to find and order something and fulfils the whole lifecycle of discovery, comparison, checkout, and payment from a goal rather than a sequence of clicks. A storefront built for humans presents this through rendered pages, search UX, and a checkout flow that assumes a person navigating a browser.

Problem

An agent does not browse a rendered page; it calls APIs, ingests structured feeds, and reasons across results. A catalog exposed only as human-facing HTML, with price and stock buried in scripts and a checkout that needs a person to click through, is effectively invisible to an agent, and a product the agent cannot parse is a product it never surfaces to its user. Yet maintaining a separate agent channel risks drifting out of sync with the human storefront's prices and inventory.

Forces

A human storefront optimises for rendered pages and search-engine visibility; an agent consumer needs structured, queryable data and a programmatic checkout.
A goal-driven agent compares across options and transacts in one flow, so a multi-step click funnel either blocks it or forces brittle page-scraping.
A dedicated agent surface must stay consistent with the human storefront's live price and stock, or the agent transacts on stale data.

Example

An online retailer publishes a structured product feed with live prices and stock and stands up an agent checkout endpoint. When a shopper's agent is asked to find a specific espresso machine under a budget, it ingests the feed, compares options across merchants, and places the order through the API with a one-merchant payment token — a sale the retailer's human-only checkout would never have captured.

Diagram

flowchart LR S[Inventory and pricing source] --> F[Machine-readable product feed] F --> A[Agent ingests and compares] A --> C[Agent-initiated checkout API] C --> T[Scoped payment token] T --> O[Order fulfilled]

Solution

Therefore:

Treat the agent as a first-class consumer of the service. Publish a structured product feed — titles, descriptions, images, price, stock, shipping, and policies — that an agent can ingest and reason over, kept current against the same inventory the human storefront uses. Accept agent-initiated checkout sessions through an API: the agent constructs a cart by calling the endpoint, and the buyer's authorisation arrives as a scoped payment token limited to one merchant, one amount, and a short expiry rather than raw card details. Adopting a shared protocol such as ACP or UCP lets many agents discover and transact against the surface without a bespoke integration per agent.

What this pattern forbids. An agent buyer cannot rely on scraping rendered pages; the merchant must publish structured, current product data and only accept agent checkout through a scoped, authenticated API, never exposing raw card details to the agent.

And the patterns that stand alongside it, or against it —

complementsVerifiable Purchase Mandate★— Anchor agent-initiated payments in a cryptographically signed mandate that captures the user's authorization and travels with the transaction, so a merchant or payment network can independently verify the agent acted on genuine user intent.
complementsTool Discovery★— Let the agent discover available tools at runtime rather than hardcoding the tool list at agent build time.
complementsAgent Capability Manifest★— Let each agent publish a standardized self-description — identity, skills, endpoint, and auth needs — at a well-known location, so others discover it and bind by capability at runtime instead of through hardcoded coupling.