GENERAL

Cloudflare Introduces AI Wallet Compatibility for x402 Payments

On August 4, Cloudflare launched the initial phase of its programmable wallet rollout, allowing customers to secure unique wallet handles for forthcoming stablecoin transactions overseen by AI agents.

Summary

  • Cloudflare users can now reserve wallet handles, with stablecoin funding and payment functionalities expected shortly.
  • Account Wallets will manage funds, while Virtual Wallets enable authenticated agents to make limited online purchases.
  • Wallet owners can establish spending limits, approve merchants, restrict transaction sizes, and require human verification as needed.
  • x402 processed 75.41 million transactions totaling $24.24 million over the past month.
  • Information regarding supported stablecoins, networks, custody partners, fees, and the complete launch timeline is still awaited from Cloudflare.

Cloudflare’s official announcement stated that users can select a handle associated with their Cloudflare account via cloudflare.pay. However, the capabilities for funding wallets and using them for API purchases, data, and online content are anticipated to arrive “soon,” without a specified release date.

This indicates that Cloudflare has opened the identity aspect of the product rather than launching a fully functional payment system. Customers should not assume that the stablecoin storage, withdrawal, or automated spending features advertised by the company are currently available.

Cloudflare Wallets introduce handles before payments

Cloudflare plans to provide two types of wallets. Account Wallets will be operated by individual or organizational users, allowing them to add funds, withdraw balances, and delegate spending to wallets managed by their AI agents.

Virtual Wallets will utilize API keys, enabling agents to purchase services within the permissions set by the Account Wallet owner. Possible purchases include APIs, Model Context Protocol tools, data, AI inference, and online content.

The company is also in the process of creating a human-readable identity framework for these wallets. For instance, a business could assign an agent an address like research.example.cloudflare.pay, linking the software to a specific organization. However, revealing that identity will be optional, allowing merchants to decide whether to cater to anonymous agents or prioritize known ones.

Cloudflare compares this system to how the Domain Name System connects user-friendly website names with less intuitive internet addresses. The wallet handle will link to an agent’s cryptographic key without replacing the core verification process.

Spending controls are designed to reduce risks from autonomous agents

Cloudflare noted that Account Wallet owners can impose spending limits, create approved merchant lists, and set transaction caps to enable agents to test low-cost services without needing human approval for every transaction.

For example, a company might allocate a weekly budget for AI inference to each employee’s agent. When a wallet reaches its limit, the agent can request a manual override from an authorized administrator. Rapidly increasing spending may trigger a review before the owner adds more funds or raises the budget.

Cloudflare presents these restrictions as protections against over-spending. However, it has yet to release technical documentation outlining how lost API keys, compromised agents, disputed payments, or unauthorized transactions will be managed.

The company has worked with Visa and Mastercard to develop systems that assist merchants in distinguishing between authorized shopping agents and malicious bots. Visa’s Trusted Agent Protocol and Mastercard’s Agent Pay utilize Cloudflare’s Web Bot Auth system to verify cryptographic signatures and determine whether an agent intends to browse or complete a payment.

x402 connects agent wallets with paid online resources

The wallets represent the buyer’s segment of Cloudflare’s planned agent commerce system. Its Monetization Gateway will cater to the seller’s side, allowing web owners and developers to charge for pages, datasets, APIs, and MCP tools.

As noted by crypto.news, Cloudflare opened the waitlist for the Monetization Gateway in July. Customers will have the freedom to set fixed or variable pricing and require payment before Cloudflare processes a request to their server.

Payments will employ x402, an open protocol that appends payment instructions to standard HTTP requests. When an agent seeks a paid resource, the server responds with an HTTP 402 “Payment Required” message, including the price and settlement instructions. The agent proceeds to pay and resubmit the request with proof of payment.

Coinbase introduced x402 in 2025 and subsequently founded the x402 Foundation with Cloudflare. The foundation’s mission is to maintain the system as a neutral standard rather than a protocol governed by a single entity or blockchain.

The x402 website reported 75.41 million transactions totaling $24.24 million in volume with 94,060 buyers and 22,000 sellers in the latest 30-day period. These metrics represent live protocol data and are subject to change as new activities occur.

In other news, crypto.news highlighted that Amazon Bedrock AgentCore has integrated x402 payments, enabling agents to acquire services using USDC. This move indicates Cloudflare is entering an evolving market already populated by cloud providers, payment firms, and blockchain developers.

Full wallet access depends on compliance and funding availability

Initially, Cloudflare indicated it would provide traditional funding and withdrawal methods in supported regions. Eligible customers would also have the chance to fund their wallets directly using stablecoins, although the company has yet to disclose which areas will be included in this rollout.

Moreover, the list of supported stablecoins or blockchains remains undisclosed. The announcement did not mention any custodian, banking partner, onramp provider, or entity responsible for identity and compliance verification. Details regarding pricing, transaction fees, and withdrawal limits are also not currently clear.

These specifics will influence how widely companies can adopt the product. Wallet services involving stablecoin custody and fiat conversion must navigate a variety of regulatory requirements across U.S. states and international markets.

The next confirmed update should clarify when Cloudflare customers can fund Account Wallets, create Virtual Wallets, and engage in live x402 transactions. Until then, users may reserve wallet handles, but the core stablecoin payment functionalities remain planned offerings rather than fully available features.

Leave a Reply

Your email address will not be published. Required fields are marked *