Cloudflare Monetization Gateway: Selling APIs, Data, and Pages to Software Buyers
Cloudflare today announced its Monetization Gateway, an engine that lets customers charge for any asset on the edge — web pages, datasets, APIs, or MCP tools. The service provides a single control plane for payment policies and access controls, while moving payment verification and enforcement off your origin. At launch, settlement happens in stablecoins over x402, the open protocol Cloudflare has been building with the x402 Foundation.
The attention economy breaks under agents
For three decades the web ran on a simple trade: content for attention, monetized by ads, subscriptions, and e-commerce. That model is coming apart as AI agents become the dominant users. Agents don’t look at ads, and they won’t maintain monthly subscriptions. They make a single call, take what they need, and move on. Cloudflare notes that AI crawlers already request content anywhere from a hundred to tens of thousands of times for every visitor they send back.
That reality points to usage-based pricing: requests, tokens, or outcomes as the unit of payment, not seats or months. Examples run from a few cents per search call, to a $0.001 base plus $0.01 per MB upload fee, to $0.99 per successfully resolved support escalation.
Cloud and APIs have sold by the call for years, but only to known buyers: a user signs up, gets a key, and is metered. Content skipped payment entirely and ran on advertising. Neither model could ever serve unverified buyers for sub-cent transactions because payment rails cost too much and settled too slowly. Collecting the money cost more than the money was worth.
Agents flip the equation backward. A single agent works around the clock like a whole team, so a flat fee grows disconnected from actual consumption. Yet an agent can plausibly make thousands of micropayments without friction, while a person approving each one is impossible. Stablecoins—such as Open USD and USDC—allow tiny transfers with negligible fees and sub-second settlement. By acting as the proxy between buyers and sellers, Cloudflare can fold the evidence of payment into the request itself, merging the payment validation path with the request path.
x402 in practice
Last year Cloudflare launched Content Independence Day, giving site owners one-click control over AI crawler access, and Pay Per Crawl to charge those crawlers. The Monetization Gateway goes further: any caller can be charged for any resource, from an API to a data feed to an MCP tool call, without building the payment machinery yourself.
x402 is an open HTTP protocol named for the 402 status code it finally uses. In the simplest exchange, a client requests a gated resource. The server responds 402 Payment Required with a payload stating price, accepted asset, and where to pay. The client pays and repeats the request with proof of payment. A facilitator verifies; the server returns the resource. There’s no redirect to a checkout page, no separate payment API. Settlement is peer-to-peer, depositing directly to the seller’s wallet. Cloudflare is aiming for sub-second payment settlement.
x402 is built for machine payments. Amounts can be fractions of a cent because the overhead is minimal, and the buyer needs no account with the seller—the payment itself is the credential. The protocol is rail agnostic but pairs naturally with stablecoins: sub-second settlement, sub-cent fees, zero chargebacks.
Rules at the edge, metering off your origin
The Monetization Gateway offers a flexible payment rules API. Tokens, API calls, MCP tool invocations, and data already flow through Cloudflare’s edge; you decide which traffic pays and express that in rule expressions familiar from other Cloudflare products. The handshake happens across Cloudflare’s 330+ city network, near the buyer, cutting latency and protecting your origin.
Planned capabilities include:
- Verb-level charging: Require $0.01 for every GET or POST to
/api/premium/*. - Variable pricing: Charge up to $2 for image generation based on compute used.
- Unauthenticated caller upsell: Intercept your origin’s
401 Unauthorizedand return402 Payment Requiredwith pricing and instructions.
When a request matches, the Gateway verifies payment before it passes. You manage rules in the dashboard, via the Cloudflare API, or through Terraform as part of infrastructure config.
Initially, sellers receive stablecoin payments and can either use them for their own transactions or redeem for fiat. For the buyer, no signup, key, or prior relationship is required: an agent requests the resource, learns the price, pays, and gets the response. The Gateway also allows you to verify agent identity with Web Bot Auth and apply usage-based pricing against an account the agent already holds if you need to know who is buying.
Toward an agent-first Internet
The near-term value—turning a request into a payment—matters less than where the industry is heading. Agents carry wallets and buy what they need: datasets, API calls, tools, compute. Many transactions will cost money, and many will require verified agent identity. Cloudflare’s position lets it handle both in a single request: verify the agent, apply the rule, check payment, and leave the origin to serve traffic. The agent becomes the primary buyer, and the request itself becomes the transaction.
There is significant value crossing the Internet today that no one is charging for. Every useful API call, every answer, every tool invocation has worth, and almost none of it is paid. The Monetization Gateway is Cloudflare’s answer: an agent-first Internet with settlement built in, where creators, API builders, and data owners get paid by the software that consumes their work—automatically, at any scale, without needing to become payments companies.
