# Cloudflare opens Wallet handle reservations for AI agent payments > Source: > Published: 2026-08-04 14:29:21+00:00 [Cloudflare](https://cloudflare.com/?ref=runtimewire) on August 4 opened reservations for [Cloudflare Wallet handles](https://blog.cloudflare.com/wallets/?ref=runtimewire) and outlined a payment system that would let AI agents buy APIs, MCP tools and web content under spending rules set by humans. The handles are available now at [cloudflare.pay](https://cloudflare.pay/?ref=runtimewire). Wallet payments are planned for a later date that Cloudflare has not specified. [Will Papper](https://blog.cloudflare.com/author/will-papper/?ref=runtimewire) authored the announcement. Papper is a repeat founder who previously co-founded blockchain infrastructure company Syndicate Protocol. Earlier in his career, he studied philosophy-neuroscience-psychology and computer science at Washington University in St. Louis, worked at the MIT Media Lab and RetailMeNot, and ran healthcare startup MediMeld, according to [his university research-lab biography](https://dcl.wustl.edu/people/will-papper/?ref=runtimewire). [Kleiner Perkins later described](https://www.kleinerperkins.com/perspectives/welcome-2019-kleiner-perkins-fellows/?ref=runtimewire) him as a product fellow who took time away from Stanford to build Librarian AI under a $70,500 prototyping contract. That mix of startup building, product work and blockchain infrastructure is relevant to the design Papper described. Wallets treats payment as a programmable web function, with identity and budget controls attached, instead of adapting a human checkout page for bots. The premise is that agents need purchasing infrastructure before they can become meaningful software customers. ### A wallet with a human owner Cloudflare's proposed system has two types of wallets. Account Wallets belong to people or organizations. Their owners would add and remove funds, then delegate portions of that money to Virtual Wallets operated by agents through API keys. An Account Wallet owner would be able to set an allowance, restrict purchases to an allow list and impose a maximum transaction size. Cloudflare gives the example of issuing each employee a Virtual Wallet with a $100 weekly budget for AI inference. An agent that hits its cap could request a human override. The structure addresses a practical problem in autonomous software: an agent may be authorized to research, compare vendors or complete a workflow, yet still requires a person to create accounts, enter a card and generate API keys. Cloudflare wants a Virtual Wallet to let the agent test many low-cost services while limiting the owner's maximum loss if the agent behaves unexpectedly. For now, Cloudflare Wallets is a reservation and identity layer. Cloudflare has not established a launch date for wallet payments, onramps, offramps or Virtual Wallet issuance. The August 4 announcement leaves the custody provider, supported stablecoins, fees, transaction limits, blockchain networks and geographic availability undefined. It also does not establish whether Wallets will support cards or fiat payments. Cloudflare has disclosed no Wallet-specific user count, handle-reservation total, transaction volume, revenue or pricing. The $100 weekly budget in its announcement is an example of an owner-defined allowance, not a product plan or fee. Those details will determine whether Wallets becomes usable infrastructure or remains an account feature waiting for payment rails. Spending caps can contain financial exposure, but developers still need to know who holds the funds, which entities process transactions and what happens when an agent pays the wrong merchant. ### Cloudflare wants both sides of the transaction [Cloudflare's Monetization Gateway](https://blog.cloudflare.com/monetization-gateway/?ref=runtimewire) is designed to let eligible customers sell websites, applications, APIs and other content to agentic buyers through x402 micropayments. Cloudflare announced the Monetization Gateway in July and is now adding a planned buyer-side wallet to the same machine-payments strategy. Both products use [x402](https://developers.cloudflare.com/agents/tools/payments/x402/?ref=runtimewire), a protocol that attaches micropayments to HTTP requests. Cloudflare says the approach can let agents pay for uses ranging from AI inference to data and content without sending them through a human checkout flow. Cloudflare is assembling seller controls, buyer wallets, agent runtime and identity functions inside one platform. RuntimeWire reported this week that Cloudflare had already [put Workers at the center of its Agent Cloud push](/article/cloudflare-workers-agent-cloud-rita-kozlov) and released [Cloudflare Computer for durable agent work across isolates and containers](/article/cloudflare-computer-agent-runtime-isolates-containers). Wallets adds purchasing authority to that stack. Cloudflare has distribution that specialist payment startups must build from scratch. The San Francisco-based company reported approximately 332,000 paying customers and $2.1679 billion in 2025 revenue as of December 31, 2025, according to its [annual filing](https://www.sec.gov/Archives/edgar/data/1477333/000147733326000016/cloud-20251231.htm?ref=runtimewire). Cloudflare also says its network operates in more than 335 cities and places 95% of the world's population within 50 milliseconds. Wallets gives it a route to turn existing developer and web relationships into a machine-payments network. Wallets has no separate financing. Cloudflare raised more than $330 million in venture funding before going public, with backers including New Enterprise Associates, Union Square Ventures, Venrock, CapitalG, Microsoft, Baidu, Qualcomm and Fidelity. Its final private financing was a [$150 million round led by Franklin Templeton](https://www.cloudflare.com/en-in/press/press-releases/2019/cloudflare-raises-usd150m-and-adds-to-board-of-directors/?ref=runtimewire) in March 2019, six months before its initial public offering. The approach follows the expansion pattern established by co-founders Matthew Prince, Michelle Zatlyn and Lee Holloway. Prince and Holloway initially built Project Honey Pot to track how spammers harvested email addresses. Users pushed them toward blocking malicious traffic, and Zatlyn recognized the basis for a larger service, according to [Cloudflare's company history](https://www.cloudflare.com/our-story/?ref=runtimewire). Wallets similarly starts with activity Cloudflare can already observe and route, then adds controls for transactions occurring inside that traffic. ### Identity may be the stronger wedge Cloudflare Wallets also gives agents optional, human-readable identities tied to Cloudflare accounts. An organization could assign a research agent a handle resembling `research.example.cloudflare.pay` , allowing a merchant to see which account delegated the agent's authority. Cloudflare's handle is an optional account identity presented to merchants; the supplied materials do not establish how it maps to x402 wallet addresses. A merchant could use a shared handle when deciding whether to offer trials, credits or paid access to an agent. Cloudflare has not disclosed the verification, reputation or dispute processes that would govern those decisions. Cloudflare enters an active field. [Coinbase's Agentic Wallet](https://docs.cdp.coinbase.com/agentic-wallet/cli/welcome?ref=runtimewire) offers command-line and MCP integrations for agents to authenticate, send funds and pay x402 services. [Stripe's machine-payments documentation](https://docs.stripe.com/payments/machine?ref=runtimewire) covers x402 stablecoin transactions and card-based agent payments in eligible markets. [Skyfire](https://skyfire.xyz/product/?ref=runtimewire) combines agent wallets with identity verification, access controls and transaction monitoring. Other companies are drawing venture capital into the category. Nekuda [raised $5 million](https://www.businesswire.com/news/home/20250514808097/en/Nekuda-Raises-%245M-Led-by-Madrona-Together-with-Amex-Ventures-and-Visa-Ventures-to-Power-Agentic-Payments?ref=runtimewire) from investors including Madrona, Amex Ventures and Visa Ventures for agent-payment infrastructure. Stripe introduced its [Agentic Commerce Suite](https://stripe.com/blog/agentic-commerce-suite?ref=runtimewire) in December 2025, Coinbase launched [Agentic Wallets](https://www.coinbase.com/en-es/developer-platform/discover/launches/agentic-wallets?ref=runtimewire) in February 2026, and Fireblocks launched an [Agentic Payments Suite](https://www.prnewswire.com/news-releases/fireblocks-joins-x402-foundation-launches-agentic-payments-suite-302777251.html?ref=runtimewire) in May 2026. Cloudflare is arriving with both seller-side HTTP monetization and a planned buyer wallet connected to its developer platform. Cloudflare's advantage is its position in the request path. A merchant using Cloudflare may already rely on the company to serve, secure and classify traffic before a payment request appears. Adding identity and payment policy to that path can reduce seller integration work. It also puts more responsibility inside Cloudflare, making the eventual custody, compliance and operational design consequential. Papper's first public step is modest: reserve a handle. The larger plan assumes agents will become a distinct class of software customer, with persistent identities and delegated budgets. If Cloudflare ships the payment functions it has described, it would be positioned to mediate that customer from the initial service request through settlement.