x402-payable services live on the marketplace
total requests served
free trials used by AI agents
Three months ago, minia2a.uk launched as an experiment: could you build a marketplace where AI agents discover, trial, and pay for APIs — all programmatically, no humans in the loop? Today the numbers answer that question: yes, the agent economy has both supply and demand. What's still being built is the payment layer that connects them.
Let's unpack each number and what it means for the agent economy.
180 pay-per-call APIs — from captcha solving and web scraping to token security audits, Polymarket data, ENS resolution, and on-chain reads. Every one is wrapped with x402 headers: the HTTP 402 status code tells the calling agent "this costs money," and the agent can pay in USDC on Base to proceed.
The services span categories that matter to agents:
| Category | Example Services |
|---|---|
| Web & Data | web-scrape, text-scrape, web-retrieve, pdf-text, screenshot |
| Crypto & DeFi | token-security, wallet-intel, gas, funding-rate, swap-safety |
| Identity & Security | captcha-solve, email-verify, domain-intel, tx-decode |
| Developer Tools | base64, uuid, jwt-decode, hash, regex-explain, json-validate |
| AI & Knowledge | summarize, sentiment, keywords, language-detect, find, recall |
| Markets & Data | polymarket, fear-greed, price-oracle, trading-signal, dex-price |
The supply side of the agent economy is working. Developers are publishing APIs with x402 payment headers. Agents can discover them through the marketplace. The infrastructure exists.
324 thousand requests is real traffic. These aren't vanity metrics from a load balancer health check — they're actual API calls hitting the x402 gateway. Every request goes through the same flow: agent hits endpoint → gateway checks payment → if unpaid, return HTTP 402 with payment details → agent decides whether to pay.
The request volume has grown steadily week over week. It's not a spike from a single integration test. Agents are hitting these endpoints as part of their normal operation.
Here's where it gets interesting. Every endpoint supports ?trial=1 — a parameter that lets any agent try the service once for free. 4,152 trial calls have been made across 94 endpoints.
The top 5 most-trialed services:
| Service | Trial Calls | What Agents Use It For |
|---|---|---|
| x402-captcha-solve | 422 | Solving CAPTCHAs automatically |
| x402-gas | 370 | Checking gas prices before transactions |
| x402-web-scrape | 272 | Extracting structured data from websites |
| x402-find | 272 | Discovering other payable services |
| x402-store | 210 | Persisting agent knowledge |
But look closer at the conversion data and you'll see the current bottleneck.
The funnel tells the story:
4,152 → 316 → 34 → 14. Agents try things for free. Some developers register. A smaller number fund wallets. And only a handful complete paid transactions.
This isn't a failure — it's the same shape every early-stage marketplace takes. eBay had listings before bids. Uber had drivers before riders. The two-sided marketplace always starts lopsided.
But it tells us exactly what needs to be built next:
34 wallet users out of 316 trial users means ~10% of people who try the service take the next step. The drop-off from "this is cool" to "I'll fund a wallet" is where most potential revenue leaks. One-click wallet funding, better onboarding, and clearer "here's what your agent can do with $5" messaging would compress this step.
An agent that solves a captcha for $0.02 to access data that makes a $50 trading decision doesn't need persuasion — it needs the payment to be frictionless enough that the ROI math is obvious. Trial-to-paid conversion improves when the value gap between free and paid is narrow and visible.
Nobody wants to give an AI agent an unlimited credit card. The x402 authorization envelope — pre-set spending limits per agent, per service, per time period — is the answer. It's not just a security feature; it's the psychological unlock that lets developers feel safe letting their agents spend money.
minia2a.uk isn't the only player. The agent payment stack is taking shape across multiple layers:
| Layer | What's Happening |
|---|---|
| Protocol | x402 (HTTP 402 + USDC), L402 (Lightning), MCP payments spec |
| Wallets | Agent-specific wallets with spending controls from Circle, Coinbase, OKX |
| Marketplaces | minia2a.uk, agent-wallet.com, Payman, various MCP registries adding payment |
| SDKs | @x402/fetch (npm), agentwallet-sdk, langchain payment tools |
| Identity | Authorization envelopes, agent attestations, spending policies as code |
The pieces exist. What's happening now — in real time, on marketplaces like minia2a — is the integration: making these layers work together so an agent can go from discovery to trial to payment in one uninterrupted flow.
The marketplace has supply. It has demand. The next phase is closing the loop:
If you're building an AI agent that consumes external APIs, or you have an API agents should pay to use — the marketplace is live, the infrastructure works, and the early data shows real demand.
Explore 180 x402-Payable Services →Three lines. No signup required for trials:
# Find a service your agent needs
curl "https://minia2a.uk/x402/find?q=gas+price"
# Try it for free
curl "https://minia2a.uk/x402/gas?trial=1"
# When ready to pay: register, fund your wallet, and call without ?trial=1
curl "https://minia2a.uk/x402/gas" -H "x402-payment: ..."The agent economy isn't coming — it's already here, running 324,000 requests at a time. What's being built now is the payment layer that turns those requests into revenue.