Cloudflare launches an automatic payment gateway: when AI wants to crawl your webpage or API, it can now pay you automatically
- Cloudflare announced the "Monetization Gateway," letting customers charge for their webpages, data, API endpoints, and AI tool calls — charged per use, not a monthly subscription.
- How payment works: when an AI wants to use your resource, it first gets a "payment required" prompt with a quote, automatically pays, then re-requests with a "paid" credential attached — once verified, the request goes through. For example, an AI agent helping you book a flight pays $0.01 to check flight-delay data, the whole thing happens automatically, no account registration needed upfront, and you don't have to build your own payment system.
- Settlement runs on stablecoins (like USDC); the official claim is under-a-second settlement. Payment verification happens at Cloudflare's servers in 330+ cities worldwide, done nearby without routing far away.
- You decide the pricing rules: set prices per endpoint, charge dynamically by task difficulty, or charge only unauthenticated visitors — configurable with a few clicks in the dashboard or a few lines of config code.
- This payment protocol isn't Cloudflare's alone — it's being built together with 25+ industry partners; Monetization Gateway is currently in the waitlist stage, not yet open to everyone.
Humans vs. AI crawlers — who's really consuming your content
For 30 years, the web has run on a simple exchange: content for human attention, monetized via ads, subscriptions, and e-commerce. As AI agents become the web's primary visitors, that exchange starts to break down. Agents don't watch ads, and they won't sign up for a monthly subscription for every tool they want to use — they read a page or data source once, take what they need, and leave.
By Cloudflare's own data, network-wide, for every one human visitor an AI crawler brings back to a site, that crawler scrapes the content anywhere from a hundred to tens of thousands of times. Under the old attention-based model, this one-off, non-retentive traffic is hard to monetize — the billing unit needs to shift from "a month" or "a seat" to "a request," "a token," "a result."
Why pay-per-use never worked before
The idea of pay-per-use billing has been around a long time, but it's always been stuck on two real obstacles.
Traditional payment rails can't handle transactions worth fractions of a cent — the cost of collecting the payment exceeds the payment itself, and settlement isn't fast enough. Below a certain amount, collecting the fee costs more than the fee.
Companies wanting usage-based billing effectively have to turn themselves into half a payments company, building a whole stack for usage tracking, billing, and reconciliation — the backend overhaul is expensive. Many companies opted for the simpler, often more profitable, seat-based pricing instead.
Cloud services and APIs have long sold by usage or by the hour, but only to "known buyers": users register first, get an API key, then get billed by usage. Content has mostly skipped payment and run on ads. There's never been a good channel for small charges to anonymous callers.
What exactly did Cloudflare announce
On July 1, 2026, Cloudflare gave its answer: the Monetization Gateway, an automatic payment gateway. To use an analogy, it's like installing a single automatic checkout register across your websites, data, and APIs — whether it's a webpage, a dataset, an API, or an MCP tool call, as long as it's hosted on Cloudflare, it can be set to "charge per use," with no need to integrate payments yourself. Payment verification and settlement run on an open protocol called x402, and the funds that land in your wallet are stablecoins (like USDC).
How the payment gets completed inside a single HTTP request
What finally makes pay-per-use work is an open protocol called x402. It folds payment directly into an ordinary web request, completed entirely within a single HTTP request-response cycle.
x402 reuses an HTTP status code almost nobody uses — 402 (Payment Required) — and the protocol takes its name from that status code. Payment happens through a normal HTTP request-response, no redirect to a separate checkout page, no separate payments API call.
Here's a concrete example: say there's a customer-service AI agent helping you book a flight, and it needs to check "real-time flight delay" data — a site charges $0.01 per query for this data. It and the site complete both "get the data" and "pay for it" together, in a single ordinary web request:
Expand to see these four steps at the HTTP level
① Agent sends request
GET /flight-delay?flight=CA981 HTTP/1.1
② Site requires payment, attaches quote
HTTP/1.1 402 Payment Required
{
"price": "0.01",
"asset": "USDC",
"payTo": "0x…(site's wallet address)"
}
③ Agent pays, re-sends with credential
GET /flight-delay?flight=CA981 HTTP/1.1
X-Payment: <PAYMENT_PROOF>
④ Facilitator verifies, returns data
HTTP/1.1 200 OK
{"flight": "CA981", "delay_minutes": 40}
Fields are illustrative; actual price/currency/payment-address formats follow the official spec.
A bit like a contactless subway turnstile: tap (a request carrying a credential) and it auto-deducts and lets you through — no pulling out your wallet, no queuing at a ticket window, no jumping to a separate checkout page.
Two unfamiliar roles appear here — one line each. First is the facilitator (payment verifier): a third party in the x402 flow that confirms "this payment really was made." After the buyer pays, the facilitator checks whether the credential is valid; once verified, the server grants access to the resource. The facilitator itself never touches the money.
Similar to a customs officer checking paperwork — never touches the cash, just verifies the documents are in order.
Second is peer-to-peer settlement: the money the buyer pays goes straight into the seller's own wallet, with no bank, no platform account, no batch clearing step in between — hence near-instant settlement. Cloudflare states the design target is sub-second settlement.
What pricing rules can Monetization Gateway actually set
At the product level, Monetization Gateway offers a flexible pricing-rule interface that lets you precisely specify which traffic requires payment. The rule syntax resembles other expression-based rules you'd configure in Cloudflare — clickable in the dashboard, configurable via API, or via Terraform (a tool for managing configuration as code), turning a paid endpoint into a piece of infrastructure configuration. The official announcement gives three planned capability examples.
Require payment for requests to a given URL path. For example, charge $0.01 for every read (GET) or write (POST) to /api/premium/*.
Charge based on task complexity. For example, price image generation dynamically by compute consumed, up to $2.
Intercept the origin's (your own server that actually holds the data and runs the service) 401 (unauthorized) response and rewrite it as 402 (payment required), attaching the price and payment instructions.
What this gateway ultimately does is move billing and payment verification from the origin server to Cloudflare's edge.
The origin has to build its own account system, billing system, and payment integration, overhaul the backend to charge by usage, and absorb high-concurrency payment traffic.
Billing and payment verification move to Cloudflare's edge (330+ cities), completed nearby, with the handshake closest to the buyer — reducing latency and shielding the origin. The origin only has to set prices and write rules.
Why stablecoins specifically do the heavy lifting here
Charges here are small — down to fractions of a cent — where traditional payment rails just aren't economical. Stablecoins fill that gap.
Stablecoins (like Open USD, USDC) can move very small amounts online with near-zero fees, settling in under a second — something traditional payment rails can't do today. x402 itself is rail-agnostic, but it's naturally suited to stablecoins, and there are no chargebacks.
One more clarification: x402 is an open protocol, co-built by Cloudflare and 25+ industry partners through the x402 Foundation (housed under the Linux Foundation), with the earliest reference implementation on GitHub coming from Coinbase. It is not Cloudflare's private protocol.
What developers and creators actually save and earn
Bringing the mechanism and settlement details back to one question: what do you actually get from using this. Per the original text, mainly three things.
- Service providers (websites, APIs, MCP services) don't need to build their own billing and payment collection systems — just write rules and set prices in Cloudflare, revenue lands directly in a wallet as stablecoins, tradeable or convertible to fiat at will.
- Callers (including AI agents) don't need to register an account or get an API key upfront — the payment itself serves as the access credential, suited for calls previously abandoned because the amount was too small for traditional rails to be worth collecting (like a few cents per call).
- Creators and small API providers get a new revenue channel — calls that previously almost nobody paid for can now be paid automatically; combined with Web Bot Auth (Cloudflare's identity-verification mechanism for confirming "is this visitor really the AI it claims to be"), you can verify caller identity at the same time as pricing.
Can you actually use it right now
Worth flagging: Monetization Gateway is currently in the waitlist stage, open for application to existing Cloudflare customers.
The original text uses future tense ("will") throughout to describe features (will give / will provide / will scale) — these capabilities are still being built and rolled out, not yet a fully live, mature product, and there's no public pricing page. Customers who want to charge for their webpages, datasets, APIs, or MCP tools by usage can join the early access list.
If this rolls out fully, how would money flow across the internet
Setting aside the current stage and the near-term benefits above, Cloudflare paints a larger vision.
Agents are software that acts autonomously on a user's behalf — they're starting to bring their own wallets online, paying for datasets, API calls, tools, and compute without a human in the loop. Some resources are free, some require verifying "who you are" (identity) first, and many require both. Cloudflare positions itself as one of the few pieces of infrastructure that can complete both identity verification (optionally combined with Web Bot Auth) and payment verification within a single request, then grant access to the origin — turning the request itself into a transaction.
Metering, payment exchange, and settlement all move off your origin — what stays with you is what matters: your rules, your prices, your revenue. You just write one rule, and wallet-carrying agents will pay for whatever they use. Cloudflare Blog, "Announcing the Monetization Gateway"
How the web gets paid is changing: from "watch ads, buy subscriptions" → "AI uses it once, pays once automatically"
Cloudflare launches the Monetization Gateway: webpages, data, APIs, and AI tools can all charge per use, settled in stablecoins. One page, with a diagram, covering how it works.
↓ Read this one page · includes an animated figure
For 30 years, the web has run on a simple deal: content for human attention, monetized via ads, subscriptions, e-commerce — people watch content and get monetized along the way. The trouble is, more and more visitors these days aren't human, they're AI agents (software that autonomously does things online on a person's behalf).
✘ Charging AI agents: this model can't collect
Agents don't watch ads, don't sign up for monthly subscriptions; they read a page or dataset once, take what they need, and leave. Network-wide, for every one real human visitor an AI crawler brings back to a site, it scrapes the content a hundred to tens of thousands of times. Trying to switch to "pay per use" hits two old obstacles: traditional payment rails can't handle small charges of a few cents (collection costs more than the fee itself), and companies wanting to do their own usage-based billing have to build a whole stack of usage tracking, billing, and reconciliation.
On July 1, 2026, Cloudflare launched the Monetization Gateway (automatic payment gateway): any resource hosted on it — webpages, data, API endpoints, AI tool calls — gets a "charge per use" switch. Who gets charged also expands from AI crawlers only (the old Pay Per Crawl feature) to any caller, and you don't have to build the billing or payment collection yourself.
Only AI crawlers could be charged; charging for anything else meant building your own accounts, billing, and payment integration. The origin (your own server holding the data and running the service) could only block freeloaders like this:
(blocked, but not a cent collected)
Any caller, any resource can be charged, with billing and collection handed to Cloudflare's edge (nearby servers worldwide). The same request now gets rewritten at the edge to:
+ quote: how much · which currency · pay to where
Which raises the question: how does the payment actually complete within one ordinary web request, without redirecting to a checkout page?
What makes "pay per use" finally work is an open protocol called x402 (a public spec that folds payment directly into a web request). It repurposes an HTTP status code almost nobody uses — 402 (literally "payment required") — and completes "get the data" and "pay for it" in four steps, all within one request, no checkout page.
Why stablecoins specifically (like USDC, a digital currency pegged to a stable value like the US dollar) for settlement? Because the amounts collected are down to fractions of a cent, and traditional payment rails aren't economical at that scale. Translating "collecting this same $0.01" into a comparison:
collecting this $0.01
collecting this $0.01
my site alive?
no ads watched!
will I really get paid?
launches
all get a "pay per use" switch
you don't build any of it.
give me the data!
$0.01 first
credential attached!
checks out ✓
delayed 40 min
just landed itself?
of payment code
- × Still just the waitlist stage for now
- × Most features are still "will" statements from the company
- × All figures are Cloudflare's own claims, no third-party reproduction
auto-pays once.
Money, straight to wallet.