I built 26 MCP servers in 2 days. Here's what I learned about x402 monetization.
Hey IH,
I've been experimenting with AI-agent monetization over the last week. Today I shipped my 26th MCP server, and I want to share what I learned — especially about x402 (the "pay-per-call" protocol for AI agents).
What I built
26 MCP servers on MCPize, all with x402 monetization:
- 25 utility servers: validators, converters, formatters (VAT, IBAN, SWIFT, LEI, JWT, cron, color, etc.)
- 1 AI server: HS Codes Classifier — takes a product description, returns a customs HS code via GPT-4o-mini
Plus 2 REST APIs on Cloudflare Workers:
- hs-codes-classifier.boring-saas-infra.workers.dev — same HS classifier, but as a REST endpoint
- document-to-json.boring-saas-infra.workers.dev — extracts structured JSON from invoice text
Why x402?
I'm in Ukraine. Stripe doesn't pay out here. PayPal is half-broken. Lemon Squeezy, Gumroad, Dodo — same story.
Crypto (USDC on Base) is the only viable payment path. And x402 makes it native for AI agents:
- No signup
- No API keys
- No OAuth
- AI agent calls your endpoint → gets 402 → pays USDC → gets result
- 0% fees (vs Stripe 2.9% + $0.30)
What worked
-
Cloudflare Workers + Furlpay = perfect stack for stateless x402 APIs
- 7ms cold start
- 100k requests/day free
- No database needed
- One middleware = paywall
-
MCPize = distribution for MCP servers
- Their Marketplace gets organic discovery
- x402 billing built-in
- $0 to list
-
gpt-4o-mini = cheap, reliable AI
- $0.15/1M input tokens
- At $0.01/call, margin is healthy even with heavy use
What didn't work
- Reddit — my account (2 weeks old, 4 karma) got auto-filtered on r/SideProject. Need 10+ karma first.
mcpize devon Windows — broken (port conflict with itself). Usenpm run devinstead.- Express + Cloudflare Workers — incompatible. Use Fetch API (
export default { fetch }).
Numbers (so far)
- 26 MCP servers live
- 2 REST APIs live
- 0 subscribers (just launched)
- $0 revenue (just launched)
- $0 spent on infrastructure
Next: trying to get the first paying customer. Any advice?
Happy to answer questions about MCP, x402, Cloudflare Workers, or the Furlpay gateway.
Advice for the first paying customer: lead with the HS code classifier and park the other 25. An agent can validate an IBAN or parse a cron string itself, so it has little reason to pay even a cent for it. Classifying a product into the right customs code is the one call where it can't easily do the job alone, and a wrong answer costs the buyer real money.
On discovery, your MCP description is doing the job a landing page does. Agents pick tools from descriptions, so write it around the task ("classify a product for customs, returns an HS code with confidence") rather than the stack.
On Reddit, the karma filter is normal. We've found the subreddit matters more than anything we write: all 5 of our removed comments came from one sub, while others left the same style alone.
Who's the buyer you picture for HS codes: Shopify cross-border sellers, or customs brokers?
Shipping 26 servers before chasing the first customer is a useful reality check for AI infrastructure launches. The no signup and pay per call flow sounds compelling, but the zero subscribers shows distribution and a narrow recurring use case still matter more than server count. ByteForward video on it https://youtu.be/eyeaMmJ4gvU
Nice post i love it
Question: I’m curious about the x402 monetization model you mentioned. How does it differ from traditional payment processors in terms of transaction fees and compliance requirements?
With 26 servers live but no paying customers yet, how will you distinguish which use cases have genuine recurring payment potential from those that are simply useful demos?
How does your invoice extractor handle different formats/layouts across vendors, and poor scan quality?