x402 x Cloudflare / AWS · the default payment component at the edge layer

Wiki route

This entry sits under AI Agent payment protocols overview · a 7-protocol survey. Read it against x402 · AI agent payment protocol reviving HTTP 402 (overview) for peer / contrast context and payments index for the broader system / regulatory boundary.

Key facts

• 2026-Q1 Cloudflare Workers natively integrated x402 ^•
• 2026-Q2 AWS API Gateway integrated x402 · enabling Bedrock agents to call paid APIs ^•
• Cloudflare handles 20%+ of global HTTP traffic ^•
• Developers can commercialize an API with 5 行 of configuration · Cloudflare collects a 1-2% facilitator fee ^•
• The facilitator model has < 100ms of verification latency (credit-advance · asynchronous on-chain settlement) ^•
• Backed by Cloudflare + AWS, x402 is no longer a crypto-only toy ^•
• Compatible with OpenAI / Anthropic agent SDKs (formal integration not yet announced) ^•

Mechanism / How it works

The edge layer is the path that HTTP traffic must always pass through, and Cloudflare Workers / AWS API Gateway are the largest 2 社 within it. Integrating x402 into the edge layer means developers do not need to write payment logic. They merely declare the endpoint price (e.g., “this API is $0.001 USDC”) · and the edge layer automatically: (1) intercepts requests with no payment → returns HTTP 402 ; (2) verifies requests carrying the X-Payment header (asynchronous on-chain settlement); (3) permits routing → the backend processes it. Via the facilitator model the edge layer performs credit-advance: before the on-chain USDC settlement completes, the facilitator has already released the request · compressing single-shot latency to < 100ms. Cloudflare’s 1-2% is the facilitator fee · which, compared with traditional Stripe’s 2.9% + $0.30 , is extremely advantageous for low-value API calls (for the fee-rate moat, contrast with Embedded Wallet · Fintech Eating Web3 in Reverse as a Trojan Horse (Stripe Five Layers)). The AWS API Gateway + Bedrock path forms a closed loop in which an agent calls paid APIs inside AWS.

Origin & evolution

2025-05 Coinbase announced the x402 spec. 2025 H2 Cloudflare engineers carried out an experimental integration on Workers · validating that the facilitator model’s latency could be compressed to 100ms. 2025-Q4 Cloudflare decided on 2026-Q1 productization. 2026-Q1 the Cloudflare Workers x402 integration was formally released — this became x402 ‘s first enterprise-grade integration. 2026-Q2 AWS API Gateway followed, forming a closed loop with Bedrock AgentCore via x402 (AgentCore’s default wallet is Privy/CDP + billing through API Gateway’s x402 ). In parallel, the Vercel AI SDK also supports x402 client calls. OpenAI / Anthropic have not yet announced formal integration · but the SDKs are compatible with x402 client calls (it only needs the agent to be able to sign with a wallet · the underlying layer depends on ERC-4337 or ERC-7702).

Related

• Wiki Index
• x402 · AI agent payment protocol reviving HTTP 402 (overview)
• Privy x AWS AgentCore
• AI Agent payment protocols overview · a 7-protocol survey
• The Blockchain Industry Has Split at the DNA Level into \"On-Chain Finance\" and \"Crypto\"

Sources

• x402 protocol (Coinbase) — https://github.com/coinbase/x402