Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Cloudflare’s Monetization Gateway lets participating sites charge for selected requests using HTTP 402, but it does not put a paywall on every domain. As of September 30, 2026, the service is in closed beta, access requires a request, and both buyers and sellers must be based in the United States. The larger change is not a new payment rail: Cloudflare is combining request rules, access enforcement, payment verification, settlement, and retries at its network edge.
What Cloudflare’s 402 paywall does
Cloudflare announced Monetization Gateway on July 1, 2026, as a way for customers to charge for digital resources crossing its network, including pages, datasets, APIs, and MCP tools. It is configurable access control, not an automatic fee on all traffic. A seller defines which requests qualify and what they cost. The September 30, 2026 beta documentation describes matching on request details such as URLs, headers, query parameters, and caller attributes; verified bots are one example of a caller distinction. Cloudflare’s announcement and Gateway documentation describe the scope and rules.
That makes “behind every domain” an overstatement. A domain owner must choose to configure rules, and those rules can target particular resources or callers rather than every visitor. Cloudflare says the design avoids a checkout redirect or a separate payment API call: payment terms and authorization travel through the resource request. That is the company’s product description, not proof that every site can integrate without origin-side work or that the experience is frictionless in every case.
How does Cloudflare’s HTTP 402 paywall work?
- A buyer requests a protected resource. The request reaches the seller’s configured Cloudflare Gateway rules.
- The Gateway returns payment requirements. The response uses HTTP 402, “Payment Required,” to tell a compatible client what payment is required.
- The buyer authorizes payment and retries. The client signs an authorization and repeats the request with that payment information.
- The Gateway verifies the authorization. Cloudflare’s documented flow uses Coinbase’s x402 Facilitator for verification and settlement.
- The origin supplies the resource and settlement follows. After verification, the origin responds; the buyer receives the resource and payment is settled. With fixed pricing, the signed amount is settled. With variable pricing, the origin reports the actual amount, according to the documentation.
HTTP 402 is the negotiation point; x402 gives the exchange machine-readable payment terms. Cloudflare’s 2025 explanation describes x402 as a way for a client and server that support the protocol to transact without the conventional account, subscription, or API-key setup. That still depends on compatible clients and sellers, valid payment authorization, and an available settlement route. Cloudflare’s x402 Foundation post explains the protocol framing.
Why the payment rail is only part of the system
A rail moves or settles money. A usable pay-per-request service also has to decide which request is chargeable, communicate the price, enforce access, verify the buyer’s authorization, deliver the right resource, handle failures and retries, and give the seller useful records. Cloudflare’s pitch is that its edge Gateway packages these tasks around an HTTP request, while the seller controls matching rules and prices. Its announcement argues that conventional usage billing assumes a known buyer, signup, credentials, and backend metering; a 402 challenge lets payment evidence accompany the request instead.
That is a product thesis, not evidence that payment infrastructure was historically the only obstacle or that the Gateway has solved every adoption problem. A client still needs to understand the challenge and make a payment decision, the seller must configure the policy and resource delivery, and the payment route must be supported. Cloudflare’s September 2026 documentation identifies Coinbase’s x402 Facilitator; the July 2026 announcement describes USDC settlement on Base and says additional rails are planned. Planned support should not be mistaken for a currently supported Gateway option. Cloudflare’s Agents monetization documentation also distinguishes x402 from MPP: MPP is a separate protocol with different HTTP headers and can support cards through Stripe as well as stablecoins. These are protocol and payment-method distinctions, not interchangeable names for the same rail.
Is Cloudflare Monetization Gateway available now?
It is in closed beta, according to documentation last updated September 30, 2026. A seller must request access, and both buyer and seller must be US-based under the stated beta eligibility. The announced settlement arrangement is USDC on Base through Coinbase’s x402 Facilitator. Cloudflare describes the product’s handling of verification, settlement, failures, retries, and analytics, but the available product materials do not establish independent adoption, transaction totals, seller revenue, conversion rates, or latency results.
How is Pay Per Crawl different from Monetization Gateway?
Cloudflare’s earlier Pay Per Crawl announcement focused on selected AI crawlers and content access. The 2026 Gateway is described more broadly, with rules for callers and resources such as sites, APIs, datasets, and MCP tools. The announcements give different payment and configuration details, so they should not be treated as interchangeable versions with proven feature parity.
Recommended Free Tools
| Dimension | Pay Per Crawl | Monetization Gateway |
|---|---|---|
| Scope described | Selected AI crawlers accessing content | Matching callers accessing sites, APIs, MCP tools, and datasets |
| Rules and prices | Site owner sets prices and selects crawlers to charge | Rules can match request fields and caller attributes; fixed and variable pricing are described |
| Payment details in cited announcement or documentation | Stripe payment management in the 2025 private-beta announcement | x402 flow using Coinbase’s facilitator; July 2026 announcement specifies USDC on Base |
| Availability stated | Private beta in the July 1, 2025 announcement | Closed beta in documentation last updated September 30, 2026; access request required |
| What is not established | Whether the product has since been retired or superseded | Independent transaction, revenue, or conversion outcomes |
Cloudflare’s Pay Per Crawl announcement said site owners could select crawlers and set prices, with payments managed through Stripe and successful delivery visible in analytics. It also described crawler owners using HTTP headers to request and accept pricing and receive confirmations. Cloudflare’s 2025 x402 post separately proposed a deferred crawler-payment model: collect audit logs and pay an aggregated fee at day’s end using a connected card or bank account. That proposal is not the same as the Gateway’s documented immediate authorization-and-settlement flow.
Cloudflare calls Gateway a next step beyond crawler-only charging, but the cited material does not establish that Pay Per Crawl has been discontinued or fully folded into Gateway. The product lifecycle remains unstated in those announcements.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What Cloudflare’s 402 volume does—and does not—show
Cloudflare reported in a September 23, 2025 post that its sites sent more than one billion HTTP 402 responses per day to bots and crawlers seeking content and ecommerce stores. That is a company-reported count of responses, not a count of accepted payment challenges, completed purchases, paid crawls, or revenue. It shows that 402 responses are already used at substantial network volume; it does not establish demand for the Gateway or prove that a pay-per-request business model is working. The post reporting the figure also discussed x402’s protocol and the proposed deferred-payment approach.
What this means for sites and agent developers
For a site owner, the central decision is whether a resource and caller can be priced and delivered on a per-use basis, and whether the seller can define reliable matching and pricing rules. The Gateway’s appeal is that payment negotiation can be part of the request path instead of requiring a separate checkout; its current limits are beta access, US-only buyer and seller eligibility, and reliance on compatible clients and the documented payment route.
For agent developers, HTTP 402 offers a standardized place to receive payment terms rather than assuming a human has already created an account or API key. But a client must be built to interpret the challenge, obtain and sign authorization, retry safely, and handle failed or unsupported payment paths. A protocol makes these interactions possible; it does not by itself guarantee that a resource is worth its price or that sellers will adopt the system.
Cloudflare quoted Ceramic.ai founder Dr. Anna Patterson in its September 30, 2026 beta announcement: “The web was built for a human buyer, someone who signs up and enters a card. Agents need to act on their own behalf, and payments are how they do it. Search is one of the first things every agent needs, so it should be one of the first things an agent can buy.” Cloudflare says Ceramic.ai uses the Gateway’s fixed-pricing scheme for paid search without an API key. That is a named product example, not an independent measure of broader usage.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
