# Cloudflare Wallets Cloudflare Wallets gives [[AI Agents]] **native payments and verifiable identity on the web**. A human funds an Account Wallet, then spins up Virtual Wallets for their agents — each with spending caps and guardrails — so agents can buy API access and content autonomously, in stablecoins, over the [[HTTP Payments Protocol (x402)|x402]] micropayment protocol. ## The design - **Account Wallets** (humans) fund and govern **Virtual Wallets** (agents) - Guardrails: allowances, per-transaction limits - Human-readable identity handles like `research.example.cloudflare.pay`, keypair-based, DNS-flavored - Pairs with Cloudflare's Monetization Gateway on the seller side: sites price their APIs/content, agents pay per call - Integrates with Cloudflare's Agents SDK The bet: agents will need to *try many services with low friction and managed risk*, and neither credit cards nor site-specific API keys fit that. Micropayments attached to HTTP requests ([[HTTP Payments Protocol (x402)|x402]]) do. ## Status Early. Handle claiming is live at cloudflare.pay; actual payment flows are "coming soon". No pricing disclosed. ## Reception (HN) - **Name squatting**: handles have no domain validation, and people found their company names already reserved by strangers. Impersonation risk out of the gate. - **Overreach concern**: Cloudflare "inserting itself in between everything, everywhere it can" — this makes them the identity + payment layer of the agentic web. - **Value questioned**: stablecoin adoption is thin, existing payment rails exist, and a persistent agent identity looks a lot like a super-cookie. - The sympathetic read: agent-to-service payments genuinely lack infrastructure, and Cloudflare's position (Workers, Durable Objects, the network itself) makes it a credible builder of it. ## My take Identity without domain validation is the part I'd fix first — trust bootstrapped from squattable handles repeats every mistake of early social platforms. The [[HTTP Payments Protocol (x402)|x402]] direction itself looks right: pay-per-request maps to how agents actually consume services. ## References - [Announcement post](https://blog.cloudflare.com/wallets/) - [HN discussion](https://news.ycombinator.com/item?id=49175461) ## Related - [[Cloudflare]] - [[Cloudflare Workers]] — the platform agents run on - [[Cloudflare Temporary Accounts]] — sibling launch: frictionless agent onboarding - [[AI Agents]] - [[Agentic Resource Discovery Specification (ARD)]] — discovery layer to Wallets' payment layer - [[HTTP Payments Protocol (x402)]] — the payment rails underneath