More than half of the traffic reaching sites on Cloudflare is now automated, and daily requests from AI agents grew by more than 1,700% in a year. This week's launches for Cloudflare's birthday were about paying for agent traffic: some help sites charge agents, and others help developers spend less on them.

Answer engines read a page and give the reader a summary, so fewer people click through. Cloudflare says that some of the most heavily crawled categories, including Retail, Computer Software and Financial Services, have seen human traffic fall by as much as 40% in under a year, and that AI training rose from 22% of stated crawler purposes in spring 2025 to 52% by June 2026. Pay Per Use is for content: an AI company offers a price for a defined use of a publisher's pages, the publisher accepts or declines in the dashboard under Monetize, the buyer reports each use as a line of JSON, and Cloudflare bills the buyer and pays the publisher monthly. It sits alongside Pay Per Crawl from 2025, which charges for access rather than use.

If your business has a website on Cloudflare, check your AI crawler settings this week; it costs nothing. Since July, every plan, including Free, has had separate switches for search crawlers, agents and AI training. On 15 September Cloudflare added Disallow AI Training, which keeps you in search results while telling a crawler's operator not to train on your pages, and Apple, Google and Microsoft have committed to honour it. Before that, if one crawler did both search and training, refusing one meant refusing the other. On Cloudflare's numbers, about one site in six already blocks AI training and fewer than 1% block search. The settings page shows which bots are reading your site and lets you allow search and refuse training. The settings won't bring back clicks lost to AI summaries; Pay Per Use is meant to pay publishers when AI products use their pages.

If you publish anything an AI product would quote, such as guides, reviews, research or trade news, look at the Pay Per Use offers in your dashboard under Monetize. You don't set the terms. The post says "the buyer proposes the definition of the use being paid for" and the buyer "sets a price"; in the beta you accept or decline, and Cloudflare says counter-offers on price are planned. Accepting means letting that buyer's verified crawler in, and each program's terms set what the buyer may do with your pages, including whether it may train on them, so read those terms before you click. The count of uses you are paid on comes from the buyer; Cloudflare checks that each reported use maps to an enrolled publisher, but the post doesn't say how it checks the count.

If you sell data or a service by the request, such as an API, an MCP tool or a dataset, the Monetization Gateway lets an AI agent pay you for a single request without creating an account. When a request matches a pricing rule you've set, the agent gets an HTTP 402 Payment Required response, pays inline over the x402 protocol, and receives what it asked for. Cloudflare's example is a sports statistics site charging a fraction of a cent each time an agent asks who leads the league in assists. The closed beta is open only to "eligible U.S.-based sellers and buyers," and payment settles in USDC, a stablecoin, on Coinbase's Base network. U.S. sellers can request access in the dashboard. Cloudflare says support for other countries is coming, with no date.

If your developers send AI requests through Cloudflare's AI Gateway and you pay per token, start with User Insights, which is free to AI Gateway users. Its new "model overkill" view flags conversations where the model looks more capable than the task needs, and shows which people, agents or apps are behind them. It does not cover ChatGPT or Claude seat subscriptions; it only sees requests that go through AI Gateway.

The Auto Router works on the same traffic: set the model name to cloudflare/auto and AI Gateway sends each request to a model it judges capable enough for the task, weighing expected quality against price. Cloudflare reports savings of up to 30% in its own OpenCode deployment, compared with using only frontier models. Before switching, read Cloudflare's benchmark table: across 97 knowledge-work tasks, the router passed 86.6% at a total cost of $2.10, and Claude Opus 5.5 passed 96.6% at $5.91. If your team's default is Opus, you would pay about a third as much and pass about one task in ten fewer. Cloudflare's own example of work that doesn't need Opus is summarising an email or a chat thread. For anything a customer sees, test the router on your own tasks first.

If any of your automation makes a pick-one decision, such as whether a ticket is urgent, which team gets an email or whether a domain is phishing, Clef and Clef-flash are worth a test. They are decision models, which return a choice with a probability attached instead of writing text, and Cloudflare released both under the Apache 2.0 licence, hosted on Workers AI and downloadable from Hugging Face to run yourself. They are API-compatible with TypeSafe's Jev, a paid decision model, so a developer already calling Jev can switch without rewriting the calls. On the ten benchmarks Cloudflare published, Clef or Clef-flash scores highest on seven, and Clef-flash's median response time is under a twentieth of a second. On TypeSafe's own workflow tests, Clef and Jev are within about three points of each other. If a large language model does your classifying today, have a developer run a few hundred of your own labelled examples through Clef and compare its accuracy and cost with what you use now.

If you build on Cloudflare, note that AI Search, now generally available with image search and OCR for scanned PDFs, starts billing on 1 November 2026. Ingestion costs $0.75 per million tokens beyond a free 5 million a month, plus charges for storage and queries, so check your volumes if you set it up during the free preview.

The new cf CLI (npm i -g cf, open beta) covers the whole Cloudflare API, where Wrangler covered about 280 operations, so a coding agent can configure DNS, domains, security rules and storage from the terminal. Protected Quick Tunnels add an --allowed-mail flag to cloudflared tunnel --url, so you can send a client a link to a site running on your laptop that only opens for their email address, with no Cloudflare account needed on either side. Containers now start in a median 648 milliseconds, down from just over four seconds, which matters if you give agents their own sandbox per task. The Web Search API lets an agent search the web through AI Gateway using Exa, Linkup or Ceramic.ai, at the providers' list prices with no markup.

If your site runs on WordPress and you are tired of maintaining it, look at EmDash 1.0. It is a stable, free, MIT-licensed CMS built on Astro, with an editing interface for staff, an API and a built-in MCP server so an AI agent can update the site, and plugins that run in a sandbox, isolated from the rest of the site. Cloudflare runs its own blog on it, and the post says Avulux moved a microsite off WordPress in under a day using EmDash's agent skills. Signal Over Noise runs on it too. Your WordPress theme and plugins won't carry over, so try it on a small site before your main one.

The rest of the week matters if you have engineers or a security team. Workers KV Instant makes Cloudflare's key-value store faster. K2 is event streaming and Basin is a data platform, both built on R2 storage. Artifacts is Git hosting for agents, in open beta with a competition attached. Observability got eight updates and request tracing, and Logpush and higher limits moved from Enterprise to every plan. Developers got Rust support, post-quantum cryptography, Vinext 1.0 for running Next.js on Vite, a VoidZero update, Forge for generating SDKs, and Kitesurf WebMCP support. Domain registration now works through the API, so agents can buy domains. Security teams get Threat Signals, free threat intelligence for every account, plus an account-abuse dashboard, an OHTTP Gateway beta, and write-ups of AI-driven WAF testing and Cloudflare's post-quantum migration. Cloudflare also published a network speed update, opened a waitlist for managed Cloudflare OS, launched a startup pitch competition, and passed $100 million in donated services.

Cloudflare's own summary says "pricing and discovery aren't solved yet, which is why both launch as betas." The free settings and the free usage view are the parts to act on this week. Both ways to get paid are betas: on Pay Per Use the buyer sets the price, and the Monetization Gateway is open only to U.S. sellers, so don't plan on income from either yet.

cloudflareeconomicspublishing