Base creator Jesse Pollak announced on May 13 that the x402 payment protocol now supports batched settlement, in an X post.
x402 now supports batched settlement
this unlocks many many tiny tiny payments (
— jesse.base.eth (@jessepollak) May 13, 2026
The update bundles many transactions together before settling them on-chain, spreading the blockchain fee across multiple payments.
Per-transaction settlement on Base already costs fractions of a cent, but batching makes sub-fraction-of-a-cent pricing economically rational for high-frequency AI workloads.
As Cryptopolitan reported last week, Amazon Web Services launched AgentCore Payments using x402, with USDC settling in roughly 200 milliseconds on Base. Batched settlement layers on top of that infrastructure.
Why batched settlement matters for AI workloads
AI services need to charge fractions of a cent per request, query, or inference call. Credit card processing fees and per-transaction blockchain costs both make ultra-small payments uneconomical at scale.
x402 processed over 169 million payments in its first year per AWS, with roughly $48 million in payment volume and 95% flowing through Base.
Pollak’s vision is software paying software: an AI agent pays tiny amounts for APIs, compute, data feeds, or image generation without human involvement.
The Coinbase x402 Bazaar MCP server is the directory layer agents use to discover paid services. AWS, Cloudflare, and others have integrated it into developer tooling.
How x402 turns HTTP requests into payment rails
The x402 protocol repurposes the long-dormant HTTP 402 “Payment Required” status code. A server responds to a paid endpoint request with HTTP 402 plus machine-readable payment instructions (price, token, chain, recipient wallet).
The client signs a payment authorization, retries the request, and the payment settles on-chain. No accounts, API keys, or subscriptions required.
Coinbase developed x402 and now co-governs the protocol with Cloudflare under the x402 Foundation.
The protocol supports stablecoin payments on Base, Ethereum, and Solana, with SDKs for TypeScript, Python, Go, and Java. The reference implementation is on Coinbase’s GitHub.
The competitive landscape closing in around x402
Stripe and Tempo launched the Machine Payments Protocol (MPP) on March 18, 2026, alongside Tempo’s mainnet.
MPP aggregates payments within an agent session and settles in bulk, similar in principle to x402’s new batched settlement but flowing into Stripe’s existing PaymentIntents API.
Per WorkOS analysis, MPP gives merchants Stripe-grade fraud detection, tax handling, and reporting without the crypto compliance burden.
Circle’s Nanopayments launched in March 2026 as an x402-compatible backend for sub-cent transfers using Gateway’s gas-free balance transfer mechanism.
Bitcoin’s Lightning Network has pursued cheap off-chain payments for years. Solana keeps base-layer fees low natively. Polygon and other Ethereum scaling projects have experimented with AI micropayment systems.
What x402 still has on the field is HTTP-native design. Instead of a separate payment app, payment authorization lives inside standard web requests.
Whether that wins the agent-native market depends on developer adoption. Crypto projects have promised practical micropayments for years without breakthrough traction.
AI infrastructure may finally provide the demand.