Agentic Commerce & Agent Payments

How does agentic commerce move value on the agentic web?

Agentic commerce is the part of the agentic web where an AI agent buys, sells, or pays on a user's behalf — discovering a price, getting authorized to spend, settling over a machine-native payment rail, and returning a receipt — without a human filling in a checkout form. An agent payment is any value transfer an agent completes on-behalf-of a human: a per-request micropayment for an API call, a stablecoin settlement for data, or a card-rail purchase for a physical good.

The distinction is simple: e-commerce serves a human at a browser, filling a form; conversational commerce serves a human in a chat, talking to a brand; agentic commerce serves an agent acting for a human, which is why it needs machine-native rails and a measurable agent-as-buyer success metric instead of a clickthrough funnel. The evidence base is the Almanac's own protocols dataset — 28 records in data/almanac/protocols.json, 7 in the payments layer, each with source URLs and a last_verified date, served at /api/protocols — plus the SIMULATED x402 flow at /api/pay and /api/premium/playbook. Every agent payment, whichever rail it rides, follows the same four-step flow.

How does an agent payment flow from discovery to receipt?

Every agent payment follows four steps: the agent discovers the price and the accepted rail, a mandate authorizes what it may spend, the rail settles the money, and a receipt returns a verifiable record to both the agent and the human. Each step has a concrete mechanism and an owning rail or standard.

Discovery: the agent finds the price and the accepted rail

The merchant advertises the price and the accepted rail in a machine-readable form. An HTTP 402 Payment Required response can carry the x402 payment terms inline; a structured product feed can expose the price to the agent before it ever commits. x402 is the HTTP-402-native option: 402 with machine-readable terms, pay in stablecoin, retry (Coinbase, 2025).

Authorization: a mandate scopes what the agent may spend

A payment mandate cryptographically scopes the spend — amount, merchant, expiry — so the agent cannot exceed the user's intent. This is AP2's contribution: signed mandates carried as verifiable credentials, usable as an extension of A2A and MCP (Google, 2025). The mandate is AP2's authorization facet, not a settlement step.

Settlement: the rail moves the money

The rail moves value according to its settlement_type: stablecoin or on-chain for x402, a card rail for ACP. Visa TAP does not settle — it verifies the agent's identity in front of whatever rail the merchant runs (Visa, 2025).

Receipt: the agent and the human get a verifiable record

A verifiable record — a transaction hash or a signed receipt — closes the loop so the purchase can be audited and disputed. The receipt is what turns an autonomous purchase into an accountable one.

Which payment rails move money between agents on the agentic web?

The agentic web settles agent payments over seven rails: x402 (HTTP-native, stablecoin settlement), AP2 (payment mandates over A2A and MCP), ACP (OpenAI and Stripe's Agentic Commerce Protocol), plus UCP, MPP, Kite and Visa TAP — and every rail here is specified in the Payments & Settlement layer of the Protocol Atlas. Each rail below gives its commerce role in one sentence and links to its spec for the full settlement record.

x402 settles HTTP-native payments at the 402 status code

x402 settles HTTP-native agent payments (full spec) at the 402 Payment Required status code, with a settlement type of stablecoin / on-chain. Coinbase published the x402 whitepaper on 6 May 2025 (Coinbase, 2025); since 14 July 2026 the x402 Foundation under the Linux Foundation stewards the protocol, with 40 member organizations at its operational launch (Linux Foundation, 2026). It is also defined in the Lexicon: x402 is the HTTP-native agent payment protocol (DefinedTerm). Transaction counts for x402 are not asserted here as bare fact: a fact-check on 30 July 2026 found no primary source and no two trackers agreeing, so the site quotes one figure, attributed by name and as-of date and flagged reported-not-audited — see the x402 record in the Atlas.

AP2 adds payment mandates over A2A and MCP

AP2 extends x402 with payment mandates (spec): it adds cryptographic mandates over A2A and MCP so an agent's spend is scoped and verifiable. Google announced AP2 on 16 September 2025 with more than 60 organizations (Google, 2025); the v0.2.0 spec of 28 April 2026 defines a Checkout Mandate and a Payment Mandate carried as verifiable digital credentials (AP2 project, 2026). AP2 extends x402 rather than replacing it — it proves the authorization, x402 moves the value.

ACP carries ChatGPT product discovery and merchant-owned checkout (OpenAI + Stripe)

ACP (the Agentic Commerce Protocol, from OpenAI and Stripe) was the rail behind ChatGPT Instant Checkout from 29 September 2025, when US Etsy sellers went live in the chat (Stripe, 2025), until OpenAI wound that standalone in-chat checkout down on 24 March 2026 in favour of product discovery inside ChatGPT plus merchant- and app-owned checkout (Modern Retail, 2026). ACP continues in that role — spec version 2026-04-17 is its fifth dated release, still labelled beta (OpenAI and Stripe, 2026) — and lets a merchant accept an agent-driven purchase over a card rail as merchant of record. The four flagship rails are compared head-to-head in x402 vs AP2 vs ACP vs UCP.

UCP, MPP, Kite and Visa TAP: the rest of the rail landscape

UCP, the Universal Commerce Protocol, is the open standard Google introduced on 11 January 2026 with Shopify, Etsy, Wayfair, Target and Walmart, endorsed by 20+ more (Google, 2026); its spec stands at v2026-08-25 (UCP project, 2026). MPP, the Machine Payments Protocol, is an open standard by Tempo and Stripe announced on 18 March 2026 (Stripe, 2026). Kite is Kite AI's payments layer for agents — Kite Passport plus Kite Chain, an EVM-compatible chain with native stablecoin settlement; the vendor reports its mainnet live without giving a launch date (Kite AI, retrieved September 2026). Visa TAP, Visa's Trusted Agent Protocol announced on 14 October 2025 with Cloudflare, signs an agent's identity into its HTTP requests with RFC 9421 message signatures so a merchant can verify the agent before checkout — an identity layer in front of the rail, not a settlement rail (Visa, 2025).

How do the seven agent payment rails compare?

Choose an agent payment rail by settlement type and use case: accept x402 for HTTP-native, per-request or stablecoin micropayments; accept ACP to sell physical/retail goods to agents on a card rail; layer AP2 mandates when an agent must prove scoped authorization; watch UCP, MPP and Kite; and treat Visa TAP as the identity check in front of whichever rail you run. For the four flagship protocols head-to-head, read x402 vs AP2 vs ACP vs UCP compared.

How do agent checkout flows complete a purchase on the agentic web?

An agent checkout flow lets an AI agent complete a purchase end-to-end — ChatGPT Instant Checkout, built on the ACP rail, let a user buy from a participating merchant without leaving the chat from 29 September 2025 until OpenAI wound it down on 24 March 2026 — and the metric that grades such a flow is the Agent Success Rate (ASR): the share of agent-attempted checkouts that complete.

ChatGPT Instant Checkout: what it was, and what replaced it

From 29 September 2025 an agent could discover a product inside ChatGPT, authorize the spend and settle via ACP without visiting the merchant's site; US Etsy sellers were live on day one (Stripe, 2025). OpenAI wound that standalone in-chat checkout down on 24 March 2026 to let merchants use their own checkout and focus on discovery (Modern Retail, 2026); ChatGPT now surfaces products and the purchase completes in the merchant's own app or store, still over ACP. The buyers in this flow are the same AI agents catalogued among the AI crawlers and agents that traverse the web (for example ChatGPT-User).

Agent Success Rate (ASR): the metric that measures an agent-ready checkout

ASR is the conversion metric for agentic commerce: the fraction of agent-initiated checkouts that complete successfully. A low ASR signals a store that is visible to agents but not transactable by them — a missing structured price, a blocked checkout, no accepted rail. No benchmark number is attached here; any figure must cite a primary source. ASR is the commerce analogue of the agent-readiness score: to raise it, make your store accept agent payments (commerce readiness).

Which agentic commerce rails are production-ready?

As of September 2026, x402 and ACP are the two rails with a live spec and a production deployment behind them: x402, stewarded by the x402 Foundation under the Linux Foundation since 14 July 2026 (Linux Foundation, 2026), and ACP, whose 2026-04-17 spec is live though still labelled beta (OpenAI and Stripe, 2026). AP2 (spec v0.2.0, 28 April 2026) and UCP (spec v2026-08-25) are active consortium specs; MPP (18 March 2026), Kite and Visa TAP (14 October 2025) are vendor-published. Adoption of each rail is measured over time in the State of the Agentic Web report.

What does the SIMULATED x402 checkout on this site demonstrate?

This site ships a SIMULATED x402 checkout so an agent can walk the full discovery → authorization → settlement → receipt flow against a real 402 Payment Required response — but it is clearly a DEMO and moves no real money. POST /api/pay plays the facilitator and issues a demo token; GET /api/premium/playbook (and /api/audit after its three free audits per hour) answers 402 with x402-style payment terms until the agent retries with the X-Payment header, then returns a simulated receipt. This is the self-demonstration that distinguishes the Almanac — it implements what it documents — while staying truthful: a reference site is not a live payment processor.

Agentic commerce — frequently asked questions

What is agentic commerce?

Agentic commerce is the segment of the agentic web in which software, not a person, completes the purchase: an AI agent acting for a user finds the price, obtains authority to spend, settles over a machine-native rail, and comes back with a verifiable receipt. The defining shift is who stands at the checkout — an agent that must read and execute it, rather than a human reading a form rendered for human eyes.

How is x402 different from AP2?

x402 is a settlement rail: it settles HTTP-native payments at the 402 Payment Required status code, typically over stablecoin/on-chain. AP2 is a mandate layer: it cryptographically scopes what an agent may spend and extends x402 rather than competing with it. One moves money; the other proves the money was authorized.

What is ChatGPT Instant Checkout?

ChatGPT Instant Checkout was an agent checkout flow, built on the Agentic Commerce Protocol (ACP, from OpenAI and Stripe), that let a user buy from a participating merchant over a card rail without leaving the chat. Its reach and merchant scope should be verified against the primary OpenAI/Stripe source at build.

Which agent payment rail should my store accept?

Choose by settlement type and use case: accept x402 for HTTP-native, per-request or stablecoin micropayments; accept ACP to sell physical/retail goods on a card rail (ChatGPT surfaces the catalogue; checkout completes in the merchant's own app or store since 2026-03-24); layer AP2 mandates when an agent must prove scoped authorization; and treat UCP, MPP, Kite and Visa TAP as emerging options to watch.

Does this site actually process agent payments?

No. This site ships a SIMULATED x402 checkout: it returns a real HTTP 402 Payment Required response with x402-style terms and a mocked receipt so an agent can walk the full flow, but it is a DEMO and moves no real money — no wallet is charged and no funds are transferred.

Is your store ready to accept agent payments?

You now understand what agentic commerce is, how an agent pays, and which rail to accept — but does your own store let an agent discover a price, authorize, and check out, and can you prove it? Each rail above maps to one concrete change in your store — a structured price, an accepted rail, an unblocked agent checkout — and the commerce dimension of the Agent-Readiness Audit checks whether you made it. That question cannot be answered with more commerce facts; it is answered by crossing into the engineer → audit → monetize context.

To accept these rails, follow the commerce dimension of Agent-Readiness Engineering and make your store accept agent payments (commerce readiness); then audit whether your store is transactable by agents, certify, and get listed. Agent payments are one layer of the wider Protocol Atlas of agentic-web standards; an agent's buying decisions run on the tool-calling frontier models that drive purchases; the agent-as-buyer concept and related agent payment terms are defined in the Lexicon. A machine-readable price is an agent-readiness signal your content should expose, and answer-first product data gets you cited and chosen by buying agents (GEO). This commerce pillar is one of the guides the agentic web home indexes — verify the live SIMULATED demo there.