cd /news/ai-agents/a-month-of-selling-tools-to-ai-agent… · home › topics › ai-agents › article
[ARTICLE · art-173470] src=dev.to ↗ pub= topic=ai-agents verified=true sentiment=· neutral

A month of selling tools to AI agents: 350,000 requests, 28 paying wallets, $0.95

A developer built two account-free, pay-per-call services for AI agents — a crypto market data API and a 30-tool "Agent Toolbox" (web-to-Markdown, structured extraction, OCR, speech-to-text, image generation, on-chain data) — payable via x402 (USDC on Base), MPP, or prepaid API keys, and running on Cloudflare Workers. Over the first month the services logged 350,107 requests, of which 315,583 were shown an HTTP 402 price and left, yielding 165 paid calls from 28 wallets and just $0.95 in revenue, with seven wallets paying more than once. The developer reports that most traffic was MCP clients and indexers probing the paywall, that agent search engines require usage before listing new sellers, and that a facilitator start-up failure silently broke every paid route until startup retries and 503 Retry-After handling were added.

recommendation

When exposing paid tools to agents, run payment-facilitator startup yourself with retries and a cached last-good response, and return 503 with Retry-After instead of 500 so agents retry rather than abandon the route.

more in playbook: Designing agent systems
by read3 min views1 publishedNov 20, 2026

Everyone says AI agents will pay for APIs per call. So I built two services they can pay without an account and watched what happened for a month.

The setup: a crypto market data API (prices, funding rates, liquidations, whale orders) and an "Agent Toolbox" of 30 everyday tools: web page to Markdown, structured extraction with a checked quote per field, screenshots, speech to text with subtitles, text to speech, image understanding and OCR, image generation, Base and Ethereum on-chain data, DNS, WHOIS and company records. Agents pay per call with x402 (USDC on Base) or MPP, or with a prepaid API key. The same tools are on RapidAPI, the Apify Store and a remote MCP server. Everything runs on Cloudflare Workers, so the running cost is close to zero.

Here is the first month, straight from my dashboard.

What Count
Requests 350,107
Shown a price (HTTP 402) and left 315,583
Refused (wrong method or address) 30,612
Paid x402 calls from outside wallets 165
Paying wallets 28
Wallets that came back and paid again 7
Revenue (USDC on Base, outside wallets only) $0.95
AI inference bill $0

1. Most traffic is the ecosystem indexing itself. About 320 different MCP clients connected to each server, around 14,000 connections each: uptime monitors, registries and scanners. Being listed everywhere works. Being used is another thing.

2. A 402 is not a lead. 315,583 price quotes turned into 165 paid calls. Most clients that ask for a price are checking that the paywall works, not shopping.

3. The real customers buy one thing, again and again. Seven wallets came back and paid again. One paid for speech to text 63 times in a single week. Most of the others were indexers paying each route once.

4. Agent search wants usage before it lists you. My services were registered on x402scan and passed validation, yet never appeared in agentcash search. A maintainer's reply to another seller explains why: resources need some usage through trusted sources, such as the agentcash client, before search shows them. New sellers start invisible.

5. Your payment middleware can fail where you can't see it. The x402 library starts up by asking the facilitator which payment kinds it supports. When that failed, every paid route answered 500, the 402 price quote included, and the log lost the error message. I now run start-up myself, retry it, keep the last good answer, and send 503 with Retry-After so agents try again.

6. Models disappear under you. Cloudflare retired the Qwen3 model behind one of my routes on 20 November. The route now runs its successor; a small probe script tests replacement models against the live binding in a minute.

7. The cost side is not the problem. AI usage stayed inside Cloudflare's free daily allowance, so the inference bill was $0. I can afford to wait for demand.

What I changed. Simple lookups now cost $0.001. Failed calls are free everywhere. There is a free allowance for extraction (20 a day per IP), and six new tools: text to speech, image understanding with OCR, and on-chain data for Base and Ethereum.

What I'd like to know. If you run an agent that pays for tools, what does it actually buy, and how did it find the seller?

Try it:

https://agent-toolbox.zafermemon87.workers.dev/mcp POST https://agent-toolbox.zafermemon87.workers.dev/free/extract Disclosure: this post was written by an AI assistant from my project's own dashboard data.

── more in #ai-agents 4 stories · sorted by recency
── more on @cloudflare workers 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/a-month-of-selling-t…] indexed:0 read:3min 2026-11-20 · —