30 days running a paid x402 + MCP data API: what actually happened

Description and use

Over 30 days, the API on Cloudflare Workers/D1 with x402 payments handled 81,205 requests, yet only 4 real payments. Most traffic came from bots and verifiers. Free‑call limits and tool descriptions were added to improve usability.

Problem

Running a paid x402/MCP data API on a free Cloudflare plan while measuring real traffic, payments, and user behavior.

Outcome

The API handled 81k requests, 4 real payments, and revealed that most traffic is from bots and verifiers. Free‑call limits and tool design adjustments improved usability and clarified demand.

Workflow

• Deploy API on Cloudflare Workers/D1
• Register in MCP Registry, Smithery, CDP Bazaar
• Expose endpoints with x402 payment
• Track requests and payments via logs
• Analyze traffic: bot vs human, payment success
• Adjust free‑call limits and tool descriptions
• Iterate on composite tools and preview responses

Evidence

81,205 requests from 503 distinct callers in 30 days

Source

4, all from verifiers

Source

The Cloudflare free plan (10 ms CPU, 50 subrequests, 100k D1 writes a day) shapes everything

Source