Agentic Commerce

The Landscape

AI agents need to pay for services autonomously. Not "a human clicks a button inside ChatGPT" but genuinely autonomous: agent discovers service, negotiates price, moves money, consumes result, moves on. Four protocols have emerged in early 2026, each solving a different piece of the puzzle.

No single protocol has won. Each optimizes for a different layer of the problem: authorization, discovery, checkout, or settlement. The protocols partially overlap and partially complement each other. The smart play is not picking a winner. The smart play is supporting all of them through a single integration point.

x402 — Our Foundation

The original. When a server wants payment, it returns HTTP status 402 Payment Required along with a price, a recipient address, and the accepted chains. The client (human or agent) pays in USDC on the specified chain, then retries the request with proof of payment. The server verifies on-chain and serves the content.

x402 moved under the Linux Foundation in April 2026 with founding members including Coinbase, Google, AWS, Visa, Mastercard, Stripe, and Cloudflare. The protocol has processed over 75 million transactions across its supported chains. It is permissionless and direct: no intermediary takes a cut. Settlement goes straight from buyer to seller.

Our gateway is built on x402. Chapters 1 through 7 of this progression are all x402 implementations.

Sources: x402.org, Linux Foundation announcement (April 2026), Coinbase x402 overview.

MPP — Machine Payments Protocol

MPP uses the same HTTP 402 handshake as x402 but adds session-based streaming micropayments. Instead of one payment per request, an agent can open a payment session and stream value continuously as it consumes a service. Think "pay per token" for LLM inference or "pay per minute" for compute.

The protocol supports three settlement rails through a single endpoint: stablecoins on the Tempo blockchain (Stripe's own L2), credit cards through Stripe's existing PaymentIntents API, and Bitcoin via Lightning Network. Backers include Anthropic, OpenAI, DoorDash, Visa, and Mastercard.

The key architectural difference from x402: Stripe sits in the middle as a payment processor. x402 is peer-to-peer (buyer pays seller directly on-chain); MPP routes through Stripe infrastructure. For publishers already using Stripe, this is a feature. For those who want permissionless, no-intermediary settlement, it is a constraint.

Sources: Stripe MPP launch post (March 18, 2026), MPP developer docs.

ACP — Agentic Commerce Protocol

ACP solves a different problem than x402 or MPP. It does not define how money moves. It defines how an AI agent discovers products, understands pricing, adds items to a cart, and completes a purchase. Think of it as "Shopify for agents" — a standardized commerce layer that sits above any payment rail.

The protocol specifies schemas for product catalogs, cart management, checkout flows, and order status. An agent visiting an ACP-enabled storefront gets machine-readable product listings instead of HTML meant for human eyes. It can compare prices, select options, and initiate checkout through a structured API rather than screen-scraping.

ChatGPT Instant Checkout is the first production implementation: a user says "buy me running shoes under $100" and ChatGPT handles discovery, comparison, selection, and checkout through ACP-enabled merchants. The actual payment at the bottom of the stack can use Stripe (cards), x402 (crypto), or any other rail — ACP is agnostic.

Sources: OpenAI ACP announcement (February 2026), ChatGPT Instant Checkout.

AP2 — Agent Payments Protocol

AP2 answers the trust question: how does a seller know that the AI agent trying to buy something is actually authorized to spend money? And how much? And on whose behalf?

The protocol defines an authorization and trust framework for agentic spending. It is deliberately chain-agnostic — it does not specify where the money goes or how it moves. Instead, it specifies how an agent proves its spending authority: delegation chains (Alice delegates $50/day to her shopping agent), spending limits, merchant allowlists, and cryptographic proof of authorization.

AP2 is complementary to x402 and MPP, not competitive. A complete agentic commerce transaction might use AP2 to prove the agent is authorized, ACP to handle the product discovery and checkout, and x402 or MPP to actually move the money. AP2 fills the "who said this agent can spend?" gap that the settlement protocols do not address.

Source: Google AP2 developer documentation (2026).

How They Fit Together

The key insight: these protocols are complementary, not strictly competitive. Each one addresses a different layer of the agentic commerce stack. A complete machine-to-machine transaction might use all three layers.

No single protocol covers all three layers today. x402 and MPP are strong at settlement but say nothing about authorization or discovery. ACP handles discovery and checkout but defers to other protocols for payment. AP2 handles authorization but does not move money or manage products.

Our Position: The Multi-Protocol Gateway

We do not pick winners. Our gateway accepts payment via x402 (direct USDC on any chain), MPP (via Stripe), or traditional rails (card, Venmo, Apple Pay). A publisher integrates once with our gateway; we route to whatever protocol the buyer's agent (or human) uses.

This is the same multi-rail thesis we proved in chapters 1 through 7, extended to the protocol layer:

What multi-protocol means for publishers

• Human buyer with a credit card — routed through Stripe (existing fiat rail)
• Human buyer with Phantom wallet — routed through x402 (direct USDC)
• AI agent with x402 support — standard 402 handshake, USDC settlement
• AI agent with MPP support — 402 handshake, Stripe settlement
• AI agent with AP2 delegation — verify authorization, then settle via x402 or MPP
• AI agent with ACP catalog — serve machine-readable product data, then settle via any rail

The publisher does not need to know which protocol the buyer or agent is using. They set a price and a wallet address. The gateway handles the rest.

Agentic.market

This matters for us because our gateway is being prepared for listing on agentic.market — not as content to be consumed, but as payment infrastructure. Gateway-as-a-Service: any agent that needs to gate content or process payments can use our gateway through a standard x402 interface.

What Gateway-as-a-Service looks like

• An AI agent building a website needs to add paywalls — it calls our gateway API
• A content platform wants to offer micropayments — it integrates our gateway endpoint
• A publisher agent managing a portfolio of sites — it uses our gateway to configure payment rules across all of them

Source: agentic.market — live marketplace stats as of April 2026.

Summary

The agentic commerce landscape in April 2026 has four protocols, each solving a different layer of the machine-to-machine payment problem. None has won. The backers are hedging across all of them. The protocols are converging toward a layered stack where authorization, discovery, and settlement are handled by different but interoperable standards.

Our position is clear: we are the multi-protocol gateway. We built on x402 because it was first, open, and direct. We add MPP because Stripe's distribution is massive. We support ACP and AP2 as they mature because they solve layers that x402 does not. A publisher integrates once. An agent pays however it wants. We route.