NewsroomCloudflare launches programmable wallets for the agentic internetAugust 4, 20264 min read

Cloudflare Launches Programmable Wallets to Let AI Agents Pay Their Own Way

The infrastructure giant is rolling out Cloudflare Wallets alongside a persistent identity tool and a service called cloudflare.pay, aiming to give autonomous AI agents a way to prove who they are and spend money on the open web.

A wallet built for bots, not humans

Cloudflare announced Cloudflare Wallets this week, describing the product in its own blog post as "the programmable wallet for the agentic Internet." The framing is deliberate: this isn't a consumer crypto wallet or a checkout widget bolted onto a website, it's infrastructure meant to sit underneath AI agents that act on a person's behalf, whether that's booking a hotel, comparing prices, or completing a purchase without a human clicking a single button.

Fortune's coverage zeroes in on the shopping use case, calling the launch a "permanent ID tool and wallet for AI shopping." That pairing of identity and payment is the core of the pitch: an agent needs to be recognizable across sessions and merchants before anyone will let it hold funds or complete a transaction on someone's behalf.

Business Wire's headline puts it even more plainly: Cloudflare is giving AI agents "an identity and a wallet." Taken together, the coverage points to a two-part system, persistent identity plus programmable spending, rather than a single point tool.

In plain terms

Cloudflare built a wallet made for AI agents, not people. The idea is that an agent needs a reliable ID and a way to spend money before it can shop or book things on your behalf.

cloudflare.pay and the commerce layer

FF News reports the launch also includes cloudflare.pay, described as enabling "secure AI agent commerce." That naming suggests Cloudflare is standing up a dedicated payments surface for agent-initiated transactions, distinct from its existing edge and security products, though the exact mechanics of how cloudflare.pay interoperates with the wallets themselves aren't detailed in this week's coverage.

The commerce angle matters because agentic shopping has a trust problem that predates any specific vendor. A merchant needs some way to know that an incoming purchase request is from a legitimate, authorized agent and not a scripted attack or an impersonation. Pairing a permanent identity credential with a programmable wallet is one answer to that problem, and it's the answer Cloudflare appears to be building toward.

None of the coverage this week goes deep on protocol specifics, token standards, or settlement rails, so the technical reader should treat this as a directional announcement rather than a full spec. What's clear from the headlines is that Cloudflare is positioning itself as the layer that both identifies and authorizes agent-driven spending, rather than leaving that to individual merchants or wallet providers to solve piecemeal.

In plain terms

Cloudflare also launched a payments service called cloudflare.pay, meant to work with the new wallets so an AI agent can actually pay for something once it's been identified. We don't yet know all the technical details of how the pieces connect.

Why Cloudflare is the one doing this

Cloudflare already sits in front of a huge share of the web's traffic, which makes it a natural place to add agent-facing infrastructure. If agents are going to be issued identities and wallets that merchants trust, having that layer live at the same company that already handles bot detection, routing, and security for those sites is a logical extension rather than a leap.

This week's launch reads as Cloudflare extending its existing role, gatekeeper and plumbing for the web, into the money-moving layer of the agentic internet. The company isn't building agents itself; it's building the identity and payment rails those agents need to operate credibly once they leave the browser and start acting on a user's behalf across many different sites and merchants.

In plain terms

Cloudflare already runs a lot of the internet's plumbing behind the scenes. Adding wallets and IDs for AI agents is a natural next step for a company already trusted to handle traffic and security.

Outbound agents versus a receiving end

Cloudflare's wallets and cloudflare.pay are built for the outbound side of the agentic web: giving an AI agent an identity and money so it can go out and transact across the open internet, wherever it lands. That's a real and necessary piece of infrastructure, and it addresses a trust gap that has been genuinely missing.

Our platform sits on the other side of that same interaction. hashtag.space and hashtag.org exist to make a business findable, readable, and transactable by the agents that show up at its door, not to send an agent out into the world. A business claims a #name and gets a geo-pinned, agent-readable portal with structured offerings, hours, booking, and payments, so an incoming agent doesn't have to scrape a page to figure out what's on offer.

Each portal can run a GIGI agent that answers visitors in chat, voice, or video, takes bookings, and captures leads for the owner. BRON and CADE plus structured schemas aim to get that business read and cited by AI engines like ChatGPT and Perplexity rather than just ranked by a search algorithm, and our keyword discovery runs on open, visible stake through an on-chain auction using $SPACE rather than a hidden ranking formula. An MCP server lets any AI agent, including the kind Cloudflare's wallets might be paying on behalf of, connect in and search the network, leave a lead, book, buy, or claim its own presence.

The honest way to frame the two efforts: Cloudflare is arming agents to go out and act. We're building the side of the internet built to receive them, be understood by them, and transact with them once they arrive.

Claim your #nameThe Agentic Internet doc

Sources