Coinbase · x402 · Cloudflare · Stablecoin · HTTP 402
Coinbase x402 and Cloudflare: machine payments over HTTP and AffixIO verification
Coinbase and Cloudflare co-govern the x402 protocol, reviving HTTP 402 Payment Required for AI agent micropayments in stablecoin. Public networks processed over 150 million x402 transactions by early 2026. Cloudflare supports x402 at the edge; Google integrated an A2A x402 extension; Stripe added x402 on Base. The settlement rail works. Teams still need to verify the agent may spend before the wallet signs. AffixIO returns that YES/NO without holding keys or PII.
What x402 is and why it trended
x402 is an open payment standard using HTTP status code 402. A client requests a resource; the server responds with payment requirements; the client pays via stablecoin; the server delivers the resource. No account signup, no redirect checkout, no subscription contract for a single API call.
The x402 Foundation, backed by Coinbase, coordinates spec evolution. V2 shipped December 2025 with improved facilitator abstraction and multi-chain support. Keyword volume for x402 protocol and HTTP 402 payments correlates with agent tool marketplaces and paid MCP servers.
HTTP 402 request cycle
Resource request
Payment terms
Stablecoin
Resource
Facilitators verify onchain payment proofs and notify the origin server. Settlement finality in roughly two seconds on Base and Solana makes per-call billing viable where card interchange would exceed the transaction value.
Cloudflare at the edge
Cloudflare supports x402 transactions on its network, pairing edge delivery with machine payment acceptance. Paid APIs behind Cloudflare Workers can return 402 responses without origin servers handling wallet logic directly.
Cloudflare also partnered with Visa on TAP for agent identity at merchant checkout. Edge x402 and TAP address different layers: x402 settles micropayments; TAP authenticates shopping agents on card rails.
Production traction in 2026
Transaction volume
Over 150 million x402 transactions across Base, Solana, and other supported networks by Q2 2026.
Ecosystem integrations
Google A2A x402 extension, Stripe on Base, AWS Bedrock AgentCore native x402, AP2 stablecoin rail extension.
Use cases
Paid LLM tool access, data API metering, agent-to-agent service fees, MCP server monetisation.
Economics
Sub-cent fees and sub-second finality unlock payments impractical on traditional card networks.
Wallet and agent risks x402 does not solve
x402 moves value efficiently. It does not know whether the agent holding the wallet should pay this endpoint, this amount, or this merchant category today.
- Compromised agent keys signing unlimited 402 responses
- Malicious endpoints returning inflated payment terms
- Revoked user delegation still spending until wallet empty
- No audit trail linking payment to consent policy version
AffixIO verifies before the wallet constructs the payment payload.
Where AffixIO fits in x402 flows
Hook AffixIO into the agent loop before wallet signing:
- Agent receives 402 with payment terms
- Agent calls AffixIO with endpoint allowlist circuit and spend context
- On YES, wallet signs x402 payment; on NO, agent skips or escalates
- Audit hash links verification to onchain tx without storing PII
Works with Coinbase CDP wallets, Privy, MetaMask agent integrations, and custom key management. AffixIO never holds private keys.
Composing x402 with AP2 and A2A
Production autonomous agents often chain protocols:
- A2A: discover and negotiate with service agent
- AP2: present mandate proving delegated spend authority
- AffixIO: live YES/NO against policy
- x402: settle stablecoin payment over HTTP
See agent payment stack 2026 and Google AP2.
Summary. Coinbase x402 and Cloudflare edge support made machine HTTP payments real at scale. AffixIO verifies agent spend permission before wallets sign. Compose x402 settlement with AffixIO authorization for production agent fleets. Contact for x402 hook patterns.
Frequently asked questions
An open standard using HTTP 402 Payment Required for stablecoin micropayments. Developed by Coinbase with Cloudflare and governed by the x402 Foundation.
Agents can pay per API call without accounts or subscriptions. Settlement in seconds with fees small enough for sub-dollar transactions.
x402 verifies onchain payment proof. Agent authorization and policy checks require a separate layer like AffixIO.
Cloudflare enables x402 payment flows on its edge network and Workers platform for paid API and content delivery.
Before the agent wallet signs an x402 payment, AffixIO returns YES or NO on endpoint allowlists, spend limits, and consent state.
Explore AffixIO
What is AffixIO · Agentic payments · Digital assets · Payment stack · Contact
Request API access
Add AffixIO verification before x402 wallet signing in your agent stack.
Contact our team