Paywall your Cloudflare Worker for AI agents in 5 minutes.
Drop-in x402 starter. Agents pay per call in USDC — no signup, no API keys, no human in the loop. Comes with Coinbase x402 Bazaar discoverability and an MCP manifest pre-wired so Coinbase-connected agents can find your API automatically.
- A Cloudflare Worker that returns HTTP 402 Payment Required for paid routes until the caller settles a USDC micropayment
- Bazaar-discoverable routes (the non-obvious bit — without
discoverable: true+ schemas, even settled payments never list) - A
/mcpmanifest so MCP clients and Coinbase AgentKit auto-discover your tools - One example paid endpoint (
GET /api/echo) you replace with your real API - HTTPS-forced redirects, JSON-or-HTML root discovery, health check
git clone <this repo> my-paid-api
cd my-paid-api
npm install
npm run dev # paywall OFF by default — iterate locallyHit http://localhost:8787/api/echo?msg=hi — you'll get a 200 with the echo. That's your free dev loop.
- Edit
wrangler.jsonc: npm run deploy- Hit
/api/echo— you'll get HTTP 402 with the payment challenge.
base-sepolia uses the default public facilitator. No keys needed. This is the right setup for development and demos.
- Get a Coinbase CDP Secret API key at portal.cdp.coinbase.com.
- Set the two secrets:
npx wrangler secret put CDP_API_KEY_ID # paste the key id when prompted npx wrangler secret put CDP_API_KEY_SECRET # paste the secret when prompted
- Set
X402_NETWORKto"base"inwrangler.jsonc, setPAY_TOto your real Base wallet, and redeploy.
Without the CDP keys on mainnet, the 402 challenge still issues but payments cannot settle. Set both secrets before going live.
Two places to edit src/index.ts:
-
The handler — add a route under
/api/*:app.get("/api/wash", async (c) => { // your logic return c.json({ ... }); });
-
The paywall config — add the same path to
routesinapplyPaywall()so it gets paywalled AND Bazaar-discoverable:"/api/wash": { price: env.PRICE_PER_CALL, network: env.X402_NETWORK, config: { discoverable: true, description: "Wash/sybil screen for any Base address", inputSchema: { queryParams: { address: { type: "string" } } }, outputSchema: { type: "object", properties: { sybil_score: { type: "number" } } }, }, },
-
The MCP manifest — add a
tools[]entry with the samename/endpoint/price_usdso MCP clients see it.
That's it. The middleware path matcher (/api/*) catches everything under /api, so only step 1 is structurally required — but skipping steps 2 and 3 means agents won't find your endpoint, which is most of the value.
This template is intentionally minimal — one example endpoint, no business logic. The patterns it shows (Bazaar config, MCP manifest, free landing + JSON discovery, HTTPS forcing, lazy app build) are the load-bearing parts. Wire in your D1 / KV / Workers AI / Durable Objects as needed.
x402-hono accepts dollar-formatted strings: "$0.01", "$0.05", "$1.00". Internally x402 settles in micro-USDC (six decimals), so "$0.01" becomes 10000 units. Different routes can charge different prices — set them per-route in the routes config.
MIT. Use it, fork it, ship it.