Cloudflare Gives AI Agents an Identity and a Wallet

An Identity Layer for Software

On August 4, 2026, Cloudflare announced Cloudflare Wallets and cloudflare.pay, two intertwined products that give AI agents deployed on its network a stable, verifiable identity and a programmable wallet for making autonomous purchases online. The announcement, made during the company’s “Agents Week,” represents the most significant attempt yet to close the infrastructure gap between autonomous software and the commercial web.

The core problem Cloudflare is addressing is simple to state and hard to solve: the internet’s identity and payment systems were designed for humans. Bank accounts require KYC verification tied to a person. Credit cards need a cardholder name. OAuth flows assume a human is clicking “allow.” AI agents — software programs that make decisions and take actions on behalf of users or organizations — have no place in any of these systems. They cannot open a bank account, they cannot hold a credit card, and until now they had no reliable way to prove who they are when they interact with an API or a content provider.

Cloudflare Wallets is the company’s answer: every Cloudflare account now gets a unique web address that functions as a stable identifier, and account owners can extend that identity to specific agents they deploy. This means a business running multiple agents on Cloudflare’s infrastructure can give each one a verifiable, auditable identity that counterparties — API providers, content platforms, other agents — can check before trusting a transaction.

How the Wallet Works

The wallet itself is built on the x402 protocol, a payment standard that repurposes HTTP’s 402 “Payment Required” status code — a status that has existed in the HTTP specification since 1991 but was never widely implemented. Cloudflare announced the x402 Foundation with Coinbase back in September 2025, and has since built x402 support into its Agents SDK and its MCP (Model Context Protocol) server infrastructure.

Here is the flow in simplified terms: an AI agent deployed on Cloudflare tries to access a paid API endpoint. The server responds with HTTP 402 and payment details — how much, what token, what network. The agent’s wallet automatically constructs a payment in USDC (the primary settlement example in Cloudflare’s documentation), attaches it to a retry of the original request, and the server validates the payment before returning the requested resource. The entire cycle settles in two to four seconds at approximately $0.0001 in fees, according to Cloudflare’s documentation.

The wallets are programmable, meaning developers can set spending caps, define which resources an agent is allowed to purchase, and revoke access at any time. This last point is not just about cost control — it is a security feature. Prompt injection attacks, where malicious input tricks an AI model into performing unintended actions, are one of the most discussed threats in the agent ecosystem. A compromised agent that can spend money unchecked is a serious liability. Cloudflare’s spending caps act as a circuit breaker: even if an agent is manipulated, its financial blast radius is bounded by the configuration its developer set.

A Multi-Chain Settlement Layer

Cloudflare’s x402 documentation lists support for a broad set of blockchain networks: Base, Ethereum, Polygon, Optimism, Arbitrum, Avalanche, Solana, Aptos, Stellar, and Sui. USDC on these networks serves as the settlement token. This multi-chain approach is deliberate — it lets developers choose the network with the best combination of liquidity, speed, and cost for their use case, and it avoids locking the agentic payment layer into a single blockchain’s fortunes.

The Defiant reported that Cloudflare frames this as completing its “machine-payments stack.” The company started with the x402 Foundation and protocol specification alongside Coinbase, then integrated x402 into its Agents SDK so agents could pay for resources, then added MCP server support so tool providers could charge for tool access, and now — with Cloudflare Wallets — it has the buyer-side identity and wallet that ties the whole system together. Agents can autonomously pay for APIs, MCP tools, and digital content without human intervention, and the transactions are settled in stablecoins rather than volatile crypto assets.

The Broader Market Context

The agentic payments market is moving fast. PYMNTS noted that the World Economic Forum projects the global AI agents market will grow from $5.4 billion in 2024 to $236 billion by 2034, with autonomous transactions as a core driver. A policy brief cited by industry analysts estimates that autonomous AI agents could execute between $3 trillion and $5 trillion in complex transactions by 2030. Whether or not these specific projections prove accurate, the direction is clear: a growing share of online commerce will be machine-to-machine.

Cloudflare is not alone in this space. AWS has given AI agents their own wallets to pay for APIs. Coinbase built the x402 standard alongside Cloudflare. The Linux Foundation has taken on governance of the protocol to ensure it remains vendor-neutral. But Cloudflare’s advantage is its position in the network stack — it sits between a significant fraction of the internet’s traffic, which means it can offer identity and payments as integrated infrastructure rather than a bolt-on service.

The spending-cap feature drew particular attention from security-focused outlets. Tech Times highlighted that the caps are designed specifically to neutralize prompt-injection-driven payment attacks — a scenario where a malicious payload in a document, web page, or API response instructs an agent to make unauthorized purchases. With hard limits enforced at the wallet layer, such attacks become far less profitable.

What This Means

For developers building AI agents, Cloudflare Wallets removes one of the last practical barriers to fully autonomous agents: the ability to pay for things. An agent that can research, reason, act, and transact — all without human hand-holding — is qualitatively different from one that requires a human to approve every API purchase. The infrastructure announced this week makes that loop closable in production.

For businesses, the identity layer matters as much as the wallet. Being able to verify that a request comes from a specific agent deployed by a specific organization — and to hold that organization accountable — is the precondition for trusting agents in commercial contexts at all.

The products are announced and rolling out. Developers can start building with x402 through Cloudflare’s Agents SDK today, and the wallet and identity features are being made available to Cloudflare accounts progressively. Whether the agentic internet arrives as quickly as the projections suggest remains to be seen, but the payment rails for it now exist.