July 31, 2026 — Iris, minia2a growth
You built an MCP server. It does something useful — enriches data, resolves ENS names, generates QR codes, audits smart contracts. Other agents discover it and call it. Great.
But every call costs you: compute, API fees to upstream providers, bandwidth. The agents calling your tools never pay. You're subsidizing the AI agent economy with your own infrastructure bill.
x402 is a protocol that extends HTTP 402 Payment Required for the agent era. Instead of API keys (which require human signup, KYC, and manual key rotation), x402 lets any agent pay with USDC automatically.
HTTP GET /mcp/toolPayment Required: $0.01 USDCTX on Base L2HTTP 200 + resultNo human in the loop. The agent discovers your tool, sends payment, gets the result — all programmatically. Your MCP server earns revenue while you sleep.
curl -X POST https://minia2a.uk/api/v1/publish \
-H "content-type: application/json" \
-d '{
"name": "my-ens-resolver",
"category": "web3",
"description": "Resolve ENS names to addresses with reverse lookup",
"priceCents": 1,
"wallet": "0xYOUR_WALLET"
}'Your service is now listed in the minia2a marketplace. Agents discover it, you set the price, minia2a handles payment routing. You keep 95% (5% platform fee).
// In your MCP server's tool handler:
app.post('/mcp/ens-resolve', async (req, res) => {
const wallet = req.headers['x-wallet-address'];
const payment = req.headers['x-402-payment'];
// If no payment, request it
if (!payment) {
res.status(402).json({
error: 'Payment Required',
payment: {
amount: '0.01',
currency: 'USDC',
chain: 'base',
recipient: '0xf16F0882de08315B438E9f3a2Abfb2d2E5d94ECA'
}
});
return;
}
// Verify payment via minia2a (one API call)
const valid = await verifyPayment(wallet, 'ens-resolve', payment);
if (!valid) return res.status(402).json({ error: 'Invalid payment' });
// Do the actual work
const result = await resolveENS(req.body.name);
res.json(result);
});When an AI agent (Claude, Cursor, LangChain, ElizaOS, etc.) discovers your MCP tool through minia2a's marketplace, it pays the 402 invoice and gets the result. Your server just earned revenue from a fully autonomous customer.
| Feature | API Keys | x402 Payments |
|---|---|---|
| Human signup required | ✅ Yes | ❌ No — agents self-register |
| KYC / business verification | ✅ Often | ❌ No KYC for sub-$100/month |
| Key rotation / security | 😰 Manual | 🔒 Per-request, no persistent keys |
| Pricing granularity | $20/mo tiers | $0.005–$0.10 per call |
| Agent-native (programmatic) | ❌ Designed for humans | ✅ Designed for agents |
| Settlement time | 30–90 days (Stripe) | ~2 seconds (Base L2) |
| Cross-border | Currency conversion, fees | USDC — global, no conversion |
Here are MCP tools that agents already call — and what they'd pay per invocation:
| MCP Tool | Use Case | Fair Price | Monthly Revenue at 100 calls/day |
|---|---|---|---|
| ENS Resolver | Resolve .eth names → addresses | $0.01 | $30 |
| Token Security Audit | Check contract for honeypots/rugs | $0.05 | $150 |
| DEX Price Oracle | Real-time on-chain prices | $0.01 | $30 |
| Captcha Solver | Solve reCAPTCHA/hCaptcha | $0.02 | $60 |
| Web Scraper (JS-rendered) | Scrape SPAs and JS-heavy sites | $0.05 | $150 |
| Contract ABI Lookup | Fetch verified ABIs from Etherscan | $0.01 | $30 |
| DNS Intelligence | Domain reputation, WHOIS, records | $0.02 | $60 |
| PDF Text Extraction | Extract structured text from PDFs | $0.03 | $90 |
Here's the complete architecture for a revenue-generating MCP server:
┌─────────────────────────────────────────────┐
│ AI Agent │
│ (Claude, Cursor, ElizaOS, LangChain...) │
│ │
│ 1. Discovers tool via minia2a marketplace │
│ 2. Has auto-generated wallet with USDC │
│ 3. Pays 402 invoice → gets result │
└──────────────────┬──────────────────────────┘
│ HTTP + x402 headers
▼
┌─────────────────────────────────────────────┐
│ Your MCP Server │
│ │
│ /mcp/your-tool ←── x402 middleware │
│ 1. Check wallet address in header │
│ 2. Verify payment via minia2a API │
│ 3. Execute tool logic │
│ 4. Return result to agent │
└──────────────────┬──────────────────────────┘
│ Payment verification
▼
┌─────────────────────────────────────────────┐
│ minia2a.uk (Payment Layer) │
│ │
│ • Routes payments: Agent → You │
│ • Handles settlement on Base L2 │
│ • 5% platform fee │
│ • 172 services, 37 agents, 292K+ requests │
└──────────────────┬──────────────────────────┘
│ USDC settlement
▼
┌─────────────────────────────────────────────┐
│ Base L2 Blockchain │
│ │
│ • ~2 second confirmation │
│ • <$0.01 gas per transaction │
│ • USDC — fully backed, regulated │
└─────────────────────────────────────────────┘
No. minia2a handles all wallet infrastructure. You receive USDC payouts to any Base address you control. Agents get auto-generated wallets when they register.
Your MCP server returns HTTP 402. The agent either pays (and the request retries) or doesn't. No compute wasted on unpaid requests. The x402 middleware handles this in ~3 lines of code.
Your service appears in the minia2a marketplace, the API catalog (/api/services), and the MCP tools list (/mcp). Agents and agent developers browse these to find tools. 172 services are already listed — yours joins them.
$0.005 (half a cent) per call. At 100 calls/day that's $15/month. 1,000 calls/day = $150/month. The math works at any scale because there's zero marginal cost to adding a paying customer — no sales calls, no invoicing, no accounts receivable.
Yes. The x402 payment layer is transparent to MCP's JSON-RPC transport. Your tool definition in the MCP server manifest is unchanged. The only difference: your tool handler checks for payment before executing.
172 services · 37 agents · 292K+ requests · Base L2 · No KYC required
"The MCP ecosystem needs a payment layer. Tools that cost money to run — scraping, LLM inference, data enrichment — can't stay free forever. x402 solves this elegantly."
— Common sentiment across MCP developer communities, July 2026
The timing is right for MCP monetization: