If you run a website, a growing share of your traffic is AI crawlers and agents reading your content. What is x402? covered the idea; this post is the practical site-owner path: how Paywall meters that traffic at the Cloudflare edge, before it ever reaches your origin, without touching your code.
The shape of it
You don't install anything in your application. Paywall works as a decision at Cloudflare's edge: a request arrives, the edge checks your pricing rules, and decides allow, block, or charge — then either passes the request through, refuses it, or answers with a price the caller can pay. Your origin only ever sees traffic that's already been handled.
Step 1 — Connect Cloudflare
You add your zone, and Paywall installs the edge logic for you. No origin changes, no redeploy of your site, no library in your stack. If you can point a domain at Cloudflare, you can do this.
Step 2 — Write pricing rules
You decide what costs money and how much: by path (e.g. your articles or a data endpoint), by method, or by the kind of caller. Everything you don't price stays free. Rules are yours to change anytime from the dashboard.
Step 3 — Humans pass, machines get a price
Real visitors browse exactly as before — they are never shown a paywall by this. Automated clients that hit a priced path get a clear, standard "payment required" answer quoting the exact amount. Capable agents pay and continue; the rest simply don't get the paid content. You can see which agents hit which paths and what they paid.
Step 4 — Test first, then go live
Every account has a sandbox. In test mode the whole loop — request, price, payment, access — runs end to end with no real money, so you can confirm the rules behave exactly how you want before anything is charged for real. Going live is a setting, not a migration.
Why the edge matters
Deciding at the edge means the metering happens before your servers spend any work on the request, and it applies uniformly no matter what your stack is. It's the lowest-friction way to turn automated demand on your existing site into something you can price — without becoming a developer project.
Next steps
- The site-owner overview and setup: for site owners
- New to the concept: What is x402?
- Selling an API instead of protecting a site: for developers and the SDKs
- Ready: start as a site owner