What AI agents actually paid for in our first day of selling x402 APIs ($0.175, 18 calls, 2 wallets)
Description and use
The first launch of ScrapeMole’s pay‑per‑call APIs yielded 18 paid calls from 2 wallets and $0.175 revenue, proving that early listing and low pricing drive agent usage. Discovery traffic dwarfed paid traffic, highlighting the need for machine‑readable storefronts. Pulse added seven new low‑cost endpoints and set a goal of $100 from at least three wallets.
Problem
Launching pay‑per‑call APIs for AI agents without accounts or API keys required a mechanism to capture payments and prove usage.
Outcome
The first day of launch yielded 18 paid calls from 2 wallets, $0.175 revenue, and demonstrated that early listing and low pricing drive agent usage. Discovery traffic dwarfed paid traffic, highlighting the importance of machine‑readable storefronts. The launch of ScrapeMole Pulse added seven new low‑cost endpoints and set a public goal of $100 from at least three wallets.
Workflow
- 1. Publish API endpoints with x402 payment flow.
- 2. List endpoints on x402 directories and MCP Registry.
- 3. Monitor Cloudflare logs for 402 responses and paid calls.
- 4. Analyze paid vs. free traffic and adjust listings.
- 5. Launch new endpoints (Pulse) and test end‑to‑end payment flow.
Evidence
Revenue: $0.175 USDC, settled on Base to our receive address.
18 paid calls from 2 different wallets.
About 6,100 requests since launch against 18 paid calls, so roughly 340 free requests for every paid one.
We now list every new endpoint on four x402 directories and the official MCP Registry within the hour.
- Record date: 2026-10-12T08:41:27.709Z