Summary
During Agents Week, Cloudflare announced Cloudflare Wallets and cloudflare.pay on August 4, 2026, letting AI agents identify themselves and pay for APIs, MCP tools, data, and inference autonomously. Wallets run on x402, the open HTTP payment protocol tied to status code 402, with human-set spending limits, and adoption has expanded to 20+ participants.
What changed
Cloudflare shipped a two-tier wallet system: an Account Wallet holds stablecoins funded by bank transfer, and per-agent Virtual Wallets operate through API keys under preset limits. cloudflare.pay gives each account a human-readable identity that can be delegated to individual agents as handles (e.g. research.example.cloudflare.pay). Payments use the x402 open protocol, already being embedded at the edge with partners including AWS.
Why it matters
Autonomous agents need to pay per-use without opening an account at every provider, and they need verifiable identity to be trusted with money. Cloudflare is building the settlement and identity layer for machine-to-machine commerce directly into its network, turning agent payments from a bespoke integration into a protocol-level primitive.
Evidence excerpt
Cloudflare Wallets runs on x402, the open HTTP payment protocol named after status code 402 Payment Required. Agents can pay for API calls, MCP tools, data, and AI inference on a per-use basis without creating an account at each provider.