Cloudflare's three-part AI monetization stack explained in plain English
Cloudflare launched three interconnected pieces. First, AI Crawl Control gives site owners visibility and control over AI crawlers — you can see crawler activity, allow certain crawlers, block others, and understand who is accessing your content. Second, Pay Per Crawl is the direct monetization piece: a site owner can now charge AI crawlers when they access content. The crawler either presents payment intent in the request or receives a 402 Payment Required response with pricing. Third, Monetization Gateway is the broadest version — any resource behind Cloudflare could have payment rules applied to it: a webpage, a dataset, an API, an MCP tool call, a premium endpoint, a file, or a search index. The payment rail they're using is called X402, which uses the HTTP 402 Payment Required status code.
Go deeper with Greg Isenberg
Ask anything about this, and Greg Isenberg answers from everything they've shared.
More to learn
See everything in Learn
Small businesses are deploying AI agents faster than 50,000-person companies ever could
In Hyper Agent's early adoption base, small shops have become surprisingly sophisticated very quickly and are running their operations in genuinely game-changing ways. The reason is simple: a 50,000-person company can't pivot on a dime — th
Hyper Agent targets both power users and casual users with the same product
The design philosophy behind Hyper Agent is to serve the full range of users — from power users who want granular control over how the agent is set up, so they can squeeze out maximum bleeding-edge performance, all the way to people who jus
Choosing an agent platform means choosing an ecosystem — pick deliberately
Greg Isenberg frames platform selection as an investment decision: when you pick a platform — whether it's OpenClaw, Hyper Agent, Codex, or something else — you are investing in an ecosystem. That framing matters because the switching costs