Configure Cloudflare's x402 edge support so your site participates in the Linux Foundation x402 Foundation network and can charge AI agents per-request via USDC or ERC-20 tokens
domain: blog.cloudflare.com/x402 · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
In the Cloudflare dashboard under Workers & Pages, enable x402 support for your domain; Cloudflare joined the Linux Foundation x402 Foundation (launched April 2, 2026) and ships native x402 handling at the edge.
Define your payment requirements in the Cloudflare x402 configuration: specify accepted tokens (USDC on Base is the dominant settlement token), price per request in token units, and your receiving wallet address.
Cloudflare's edge automatically returns HTTP 402 responses with the X402-Payment-Required header to clients that hit configured paths without a valid payment; no changes to your origin server are required for basic 402 response handling.
For payment verification, Cloudflare acts as the facilitator: it validates the client's X402-Payment header (signed payment payload) against the specified blockchain, then forwards the request to your origin with a verification token on success.
Monitor x402 transactions in the Cloudflare analytics dashboard; track per-path payment volume, accepted vs. rejected payment attempts, and revenue breakdown by token type.
Known gotchas
Customizable 402 response codes are available to all paid Cloudflare customers, but the full x402 facilitator functionality (on-chain verification and payment settlement) requires enrollment in the x402 program — not all paid plans include it by default.
Solana Foundation joined the x402 initiative in April 2026, adding SPL token support as an alternative to ERC-20 USDC; if you want to accept both EVM and Solana-based payments, configure separate payment requirement entries for each token type.
Cloudflare is both an x402 Foundation member and the infrastructure behind Pay Per Crawl; the two products share the 402 mechanism but are configured separately — Pay Per Crawl charges crawlers via Stripe settlement, while x402 edge settles on-chain.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?