Xenarch vs Cloudflare pay-per-crawl
| Xenarch | Cloudflare pay-per-crawl | |
|---|---|---|
| Custody | Non-custodial — USDC settles on-chain via splitter contract | Custodial — Cloudflare holds your earnings |
| Fee | 0% (capped at 0.99% forever) | Cloudflare takes a cut |
| Settlement | USDC on Base L2, every payment on-chain | Fiat payout, off-chain ledger |
| Stack | Any stack (Python, Node, WordPress, Joomla, custom) | Cloudflare Workers required |
| Pricing | Per-page or per-path, publisher-defined | Cloudflare-defined |
Prerequisites
- A USDC wallet on Base (this is where you receive payments)
- Your content served over HTTPS
Step 1: Register
xk_pub_...).
Step 2: Add your site
st_...) and site ID. Save both.
Step 3: Set pricing
Step 4: Install middleware
Choose your integration:- FastAPI (Python)
- WordPress
- Custom server
Step 5: Add pay.json (optional)
Serve apay.json file at /.well-known/pay.json so agents can discover your pricing without hitting a 402 first:
How it works for your users
- Humans: Pass through completely unaffected. The middleware only gates bot traffic.
- AI agents with payment: Pay USDC, get an access token, access your content.
- AI agents without payment: See HTTP 402 with payment instructions.