The Company Between Every AI Agent and the Internet
Cloudflare is trying to turn its position in the flow of Internet traffic into a position in the flow of Internet value.
On November 18, 2025, large parts of the Internet began returning error pages.
Cloudflare’s network had started failing. Websites that depended on it became unreachable. Login systems broke. Applications slowed or disappeared. Even Cloudflare’s own dashboard and support portal were affected. For many people, it felt as if the Internet itself had gone down.
The cause was not a cyberattack. A change to permissions in a database system caused Cloudflare’s bot-management feature file to double in size. That oversized file propagated across the company’s network and crashed the software responsible for routing traffic through several core services.
That outage revealed the company more clearly than any investor presentation could. Cloudflare is one of the Internet’s largely invisible intermediaries. It sits between users and websites, absorbing attacks, filtering bots, terminating encrypted connections, accelerating content, routing traffic, and increasingly running application code. When it works, nobody notices. When it fails, the web suddenly feels smaller.
Now Cloudflare is making a much larger bet. It believes the next Internet will not be used primarily by humans clicking links. It will be used by software agents searching, negotiating, purchasing, and acting on our behalf.
And Cloudflare wants to stand between those agents and almost everything they touch.
Why Cloudflare was already indispensable
Cloudflare began with a straightforward proposition: put its network in front of a website and make that site faster and safer.
Technically, Cloudflare often acts as a reverse proxy. A user trying to reach a Cloudflare-protected site first reaches Cloudflare. Its network decides whether the request is legitimate, blocks malicious traffic, serves cached content when possible, and forwards the remaining request to the customer’s server. The customer’s origin is faster, less exposed, and harder to overwhelm.
That position expanded into a broad portfolio. Cloudflare now sells content delivery, DDoS protection, web application firewalls, bot management, DNS, network routing, Zero Trust access, email security, and developer services such as Workers, R2 object storage, Durable Objects, databases, queues, AI inference, and browser automation.
The unifying asset is not any single product. It is the network underneath them.
Cloudflare’s software runs across more than 330 cities. Its architecture is unusual because the same network can deliver security, performance, and compute services close to the user rather than forcing customers to assemble separate regional products. Cloudflare has described this strategy for years with an old Sun Microsystems phrase: “The Network is the Computer.”
The business is already substantial. Cloudflare reported $2.17 billion in revenue for 2025, up 30% from the previous year. In the first quarter of 2026, revenue reached $639.8 million, up 34% year over year. It ended that quarter with 4,416 large customers generating more than $100,000 in annualized revenue, while its dollar-based net retention rate was 118%.
Those numbers mean Cloudflare’s agentic strategy is not a startup pitch attached to an empty platform. It is an attempt to redirect an existing network, customer base, and developer ecosystem toward a new class of traffic.
The shift also arrives with economic tension. Cloudflare’s first-quarter GAAP gross margin fell to 71%, from 76% a year earlier, partly because of higher third-party technology costs, network expenses, and depreciation. The company remained GAAP unprofitable, although it generated $84.1 million in free cash flow. If AI workloads are more compute-intensive than the web-security traffic Cloudflare historically carried, the agent opportunity may expand revenue while pressuring the economics that make the core business attractive.
The web’s old bargain is breaking
The human web was built around attention.
Google copied pages and sent people back to their creators. Those visitors saw advertisements, bought subscriptions, clicked affiliate links, or purchased products. Search created a tolerable exchange: content in return for traffic.
AI weakens that bargain. An answer engine can crawl a publisher’s work, synthesize it, and satisfy the user without sending that user to the source. Cloudflare’s own measurements have shown enormous gaps between how often some AI crawlers request content and how little referral traffic their platforms return.
An agent makes the problem larger. It does not see display ads. It does not linger on a homepage. It does not want a monthly subscription to every data source or tool it may use once. It requests the information it needs, converts it into an answer or action, and moves on.
This is not merely a new interface. It changes who generates Internet traffic, what that traffic is worth, and how access should be governed.
Cloudflare recognized the supply-side conflict early. In July 2025, it changed the default for new customers so they could block AI crawlers unless those crawlers received permission. It launched AI Crawl Control and a private beta called Pay Per Crawl, giving publishers the ability to allow, block, or charge specific AI crawlers.
That looked like a publisher-protection feature. In retrospect, it was the opening move in a broader strategy.
Cloudflare was learning how to identify machine traffic, determine what it could access, meter what it consumed, and attach a price to the request. Those same capabilities become foundational when the crawler evolves into an agent that can buy data, invoke software tools, reserve a hotel room, send an email, or modify a company’s production systems.
The old Internet asked: Is this request malicious?
The agentic Internet must ask harder questions: Which agent is this? Who authorized it? What is it trying to do? What may it spend? Can its actions be reversed? And who gets paid?
Cloudflare is building an answer to all of them.
What Cloudflare is actually building for agents
During Agents Week in August 2026, Cloudflare gave its many AI products a clearer purpose. The company calls the idea an “Agent Cloud”: a place where software agents can work, remember what they were doing, use the existing web, and operate under human control.
An AI model alone cannot do much of that. Imagine asking an assistant to research a trip, compare prices, email an itinerary, and wait for your approval before booking. The assistant needs to stay active while the job unfolds. It must remember earlier decisions, open websites, handle email, and know when to stop and ask you for help. Today, developers often piece those abilities together from several companies. Cloudflare wants to provide them in one place.
Cloudflare Agents gives the assistant a place to keep working even when a task lasts longer than a single conversation. Cloudflare Computer adds a private workspace where the agent can store files, install software, write code, run it, and inspect the result. The experience resembles giving a digital worker its own computer rather than asking a chatbot to answer one prompt at a time.
The agent also needs to deal with a web designed for people. Browser Run lets it open a website, click through pages, and fill out forms. A person can watch the session and take control if the agent gets stuck. Cloudflare’s email service lets the same agent receive a message, do the requested work, reply later, or bring a person into the conversation.
Then comes permission. A company would never give every employee unlimited access to every account, and it should not give that power to an AI assistant either. Cloudflare’s proposed Agent Access Model would let a business decide which agent may enter a system, what it may see, and what actions it may take. If an agent tries to make a sensitive change, WriteGuard can pause the action until a person approves it.
This fits the business Cloudflare already has. It helps companies control how employees reach internal applications. Now it wants to apply the same discipline to software acting on an employee’s behalf.
Once an agent can work, remember, communicate, and receive permission, one major ability is still missing: it needs a way to buy things.
A wallet is not just a crypto product
On August 4, Cloudflare introduced Cloudflare Wallets, a planned programmable-wallet service for agents.
The obvious reaction is to file it under crypto. That misses the larger point.
A human can encounter a checkout page, compare a price, enter a card, complete two-factor authentication, and decide whether to proceed. An autonomous agent needs a machine-readable equivalent. It needs an account that can hold value, a way to understand payment terms, and enforceable limits on what it may buy.
Cloudflare Wallets is designed around policy. Account owners will be able to create Virtual Wallets for agents, then set allowances, allow lists, and maximum transaction sizes. An agent will be able to spend within those boundaries and request a human override when it reaches a limit.
The connective tissue is x402, an open protocol named after the long-neglected HTTP status code “402 Payment Required.” Cloudflare and Coinbase launched the x402 Foundation in 2025. Under the protocol, a server can respond to a request with a machine-readable price. An agent pays, repeats the request with proof of payment, and receives the resource. No shopping cart, sales contract, subscription, or pre-existing API key is required.
Cloudflare’s Monetization Gateway, announced in July 2026 and still on a waitlist, takes the seller’s side of that exchange. A website owner could place a price on a page, dataset, API endpoint, or MCP tool. Cloudflare would meter the request, verify payment at the edge, and enforce the rule before the request reached the customer’s server.
Put Wallets and the Monetization Gateway together and Cloudflare can potentially serve both sides of a machine transaction. The agent arrives with identity and money. The resource owner arrives with an access policy and price. Cloudflare sees the request, checks the identity, applies the rule, validates payment, and passes the approved call onward.
This extends the thesis explored in The Robot That Holds Its Own Wallet: autonomous machines become economically meaningful when they can not only make decisions, but also acquire resources and settle obligations. Cloudflare is trying to make that capability native to the Internet request itself.
The request becomes the transaction.
Why Cloudflare has a credible right to win
Many companies can build an agent framework. Many can offer model inference, vector search, browser sessions, identity products, or stablecoin wallets. Cloudflare’s advantage is that it may not need to win each category independently.
That begins with position.
Cloudflare already sits in the path between a large population of Internet clients and origins. That gives it direct visibility into how machine traffic behaves, where it comes from, what it requests, and how websites respond. A standalone wallet company sees payment. A model provider sees inference. A security vendor sees policy. Cloudflare can potentially see identity, access, execution, traffic, and settlement inside the same request path.
Then comes distribution.
Millions of Internet properties already use Cloudflare. Developers already deploy Workers. Enterprises already buy its application security and Zero Trust products. Publishers do not need to migrate their websites into a new agent marketplace to control access; Cloudflare can add the control at the network edge. Developers do not need to adopt a new regional cloud to experiment with an agent; they can compose products already available in the Workers ecosystem.
The deeper advantage is the symmetry of the problem.
The agent economy needs infrastructure on both sides. Agents require compute, memory, browsers, tools, identity, and wallets. Websites require bot verification, security, permissioning, metering, and compensation. Cloudflare is one of the few companies deliberately building for the buyer and seller at once.
Cloudflare can also offer neutrality—or at least the possibility of it.
Cloudflare does not own a dominant consumer assistant, search engine, advertising marketplace, or foundation model. That gives it a plausible role as infrastructure shared by competing model companies, publishers, merchants, and enterprises. Open standards such as MCP, Web Bot Auth, and x402 reinforce that posture.
Neutrality must be earned, however. If Cloudflare becomes the identity registry, policy engine, execution environment, and payment checkpoint for agents, customers will reasonably ask how much power one intermediary should hold. The 2025 outage supplied an uncomfortable preview. Consolidating functions can make the system easier to use, but it also concentrates failure.
Finally, the products are composable.
Cloudflare’s network is becoming a set of small services that developers can combine: a Worker for logic, a Durable Object for state, a Queue for asynchronous work, Browser Run for the web, AI Gateway for models, Access for identity, WriteGuard for approvals, and Wallets for payment. The company does not need to predict the winning agent application. It needs to supply useful primitives to whoever builds it.
That is a more durable position if the agent market fragments across many models and applications.
What the Internet looks like if Cloudflare succeeds
Imagine opening a travel assistant and asking it to arrange a three-day business trip.
The agent does not begin by scraping random pages anonymously. It presents a cryptographically verifiable identity stating which service operates it and, where appropriate, which user it represents. Websites can decide whether to admit it, limit it, challenge it, or charge it.
The agent discovers a flight-search tool through a standard interface. The provider quotes a price per query. The agent’s wallet checks that the expense falls within your approved budget and pays automatically. It compares the results with a paid weather feed and a hotel inventory API. Each service receives compensation without forcing the agent to create a permanent account.
When the agent reaches a website that has no machine interface, it opens a cloud browser and navigates the human-facing page. If a login or ambiguous decision appears, it pauses and lets you take control.
Every step is logged. Every payment is attributable. Every consequential action can be governed.
For publishers, this Internet could restore a direct exchange of value. A specialized research site might charge fractions of a cent for a factual lookup, more for a complete document, and much more for proprietary analysis. A small developer could expose a useful software function without building subscriptions, sales infrastructure, and account management. An agent could assemble the best resources for a task from across the web rather than remaining trapped inside one company’s ecosystem.
This would be a profound change in the Internet’s business model. The unit of commerce would move from the advertisement, subscription, or shopping cart toward the authenticated request. The primary customer for many digital services would become software.
Cloudflare would collect revenue not because it owns the final application, but because it operates the roads, checkpoints, workspaces, and toll system the application uses.
What investors should watch now
The most important evidence will not be another product announcement. It will be usage that crosses the boundaries of Cloudflare’s stack.
Standards adoption may be the earliest external signal. If Web Bot Auth becomes a common way for websites to recognize agents, if MCP remains the dominant tool protocol, and if x402 gains support beyond crypto-native applications, Cloudflare’s infrastructure could become more valuable even when the company does not own the standard.
The opposite signals would be equally revealing: private betas that remain private, product launches without disclosed usage, agent developers choosing hyperscaler-native stacks, publishers refusing machine-priced access, or payment activity concentrating inside closed assistant ecosystems.
Cloudflare does not need every agent to run on its network. It needs enough of the interaction between agents and the Internet to pass through services it can secure, meter, or compute.
That is a subtler ambition than building the best model. It may also be a more defensible one.
Cloudflare is trying to turn its place in the flow of Internet traffic into a place in the flow of Internet value.
If it succeeds, the next generation may never think of Cloudflare as the company that made websites faster.
They may think of it as the company that taught the Internet how to do business with machines.
Source notes
Cloudflare, “Cloudflare outage on November 18, 2025”, November 25, 2025.
Cloudflare 2025 Form 10-K, filed February 2026.
Cloudflare Q1 2026 Form 10-Q, filed May 8, 2026.
Cloudflare, “Welcome to Agents Week”, August 2, 2026.
Cloudflare, “Introducing Cloudflare Agents”, August 3, 2026.
Cloudflare, “Cloudflare Computer”, August 3, 2026.
Cloudflare, “Cloudflare Wallets”, August 4, 2026.
Cloudflare, “The Agent Access Model”, August 5, 2026.
Cloudflare, “MCP Portal WriteGuard private beta”, August 5, 2026.
Cloudflare, “Announcing the Monetization Gateway”, July 1, 2026.
Cloudflare, “Launching the x402 Foundation with Coinbase”, September 23, 2025.
Cloudflare, “Content Independence Day: no AI crawl without compensation”, July 1, 2025.
Cloudflare, “Introducing pay per crawl”, July 1, 2025.
Cloudflare, “Browser Run: give your agents a browser”, April 15, 2026.
Cloudflare, “Email for agents”, April 16, 2026.
Cloudflare, “Agents that remember: introducing Agent Memory”, April 17, 2026.
Cloudflare, “Beyond IP lists—a registry format for bots and agents”, October 30, 2025.
Cloudflare, “The Network is the Computer”, July 11, 2019.