TL;DR

Cloudflare launched a Monetization Gateway that lets you charge for any digital asset (web pages, datasets, APIs, MCP tools) with usage-based pricing, settled in stablecoins. The thesis: as AI agents become the dominant internet users, the attention economy breaks down. Agents do not view ads or hold subscriptions, so they pay per request. “The request becomes the transaction.”

How it works

  • Built on the x402 open protocol, which repurposes the HTTP 402 Payment Required status code.
  • Flow: client requests a gated resource, server returns 402 plus pricing, client pays via stablecoin, client repeats the request with proof of payment, a facilitator verifies, server returns the resource.
  • Settlement is peer-to-peer over blockchain, targeting sub-second finality.
  • Payment verification runs at Cloudflare’s edge across 330+ cities, shielding origin servers from payment-volume surges.

Key features

  • Express-style rules engine, similar to existing Cloudflare policies.
  • Variable pricing by task complexity (for example 2 for image generation).
  • Granular control: charge specific REST verbs or routes, and intercept 401s to convert them into 402s.
  • Stablecoin settlement, initially Open USD and USDC; sellers can accumulate or convert to fiat.
  • Works with verified agent identity and Web Bot Auth.

Who it is for

Content creators, API providers, dataset owners, MCP tool developers: anyone serving AI agents and autonomous software.

Availability

Waitlist open to Cloudflare customers. Stablecoin-based only at launch.

Actionable takeaways

  1. If you own APIs, datasets, MCP tools, or agent-valuable content, join the waitlist early.
  2. Think in usage pricing (per-call, per-MB, per-outcome), not per-seat.
  3. Decide the auth posture: require verified agent identity, or accept anonymous micropayments.
  4. Manage paid endpoints as infrastructure-as-code alongside existing Terraform/API workflows.

Key quotes

An agent does not look at ads or need to maintain a monthly subscription to all the tools it wants to access.

The request becomes the transaction.

claude-workflows-that-run-unattended