Which agent services are actually in use
2,428 services, none with a measured call count yet. None has a receipt on record, so revenue stays unknown rather than zero.
Observation window 2026-10-16 → 2026-11-14 (UTC), 30 of 30 days scanned on Base. Calls come from the x402 Bazaar; inflows come from our own transfer scan. They are never added.
Browse by task
| # | Service | Category | Protocol | Calls · 30d | Inflows 24h | 7d | 30d | Growth 7d | Evidence | Price |
|---|---|---|---|---|---|---|---|---|---|---|
| 201 | Dev & Code | MCP | — | — | — | — | — | No payment evidence | — | |
| 202 | Dev & Code | MCP | — | — | — | — | — | No payment evidence | — | |
| 203 | Dev & Code | MCP | — | — | — | — | — | No payment evidence | — | |
| 204 | Dev & Code | MCP | — | — | — | — | — | No payment evidence | — | |
| 205 | Dev & Code | MCP | — | — | — | — | — | No payment evidence | — | |
| 206 | Dev & Code | MCP | — | — | — | — | — | No payment evidence | — | |
| 207 | Dev & Code | MCP | — | — | — | — | — | No payment evidence | — | |
| 208 | Dev & Code | MCP | — | — | — | — | — | No payment evidence | — | |
| 209 | Dev & Code | MCP | — | — | — | — | — | No payment evidence | — | |
| 210 | Dev & Code | MCP | — | — | — | — | — | No payment evidence | — | |
| 211 | Dev & Code | MCP | — | — | — | — | — | No payment evidence | — | |
| 212 | Dev & Code | MCP | — | — | — | — | — | No payment evidence | — | |
| 213 | Dev & Code | MCP | — | — | — | — | — | No payment evidence | — | |
| 214 | Dev & Code | MCP | — | — | — | — | — | No payment evidence | — | |
| 215 | Dev & Code | MCP | — | — | — | — | — | No payment evidence | — | |
| 216 | Dev & Code | MCP | — | — | — | — | — | No payment evidence | — | |
| 217 | Dev & Code | MCP | — | — | — | — | — | No payment evidence | — | |
| 218 | Dev & Code | MCP | — | — | — | — | — | No payment evidence | — | |
| 219 | Dev & Code | MCP | — | — | — | — | — | No payment evidence | — | |
| 220 | Dev & Code | MCP | — | — | — | — | — | No payment evidence | — | |
| 221 | Dev & Code | MCP | — | — | — | — | — | No payment evidence | — | |
| 222 | Dev & Code | MCP | — | — | — | — | — | No payment evidence | — | |
| 223 | Dev & Code | MCP | — | — | — | — | — | No payment evidence | — | |
| 224 | Dev & Code | MCP | — | — | — | — | — | No payment evidence | — | |
| 225 | Dev & Code | MCP | — | — | — | — | — | No payment evidence | — |
Calls · 30d is a rolling count from the x402 Bazaar and the MCP registry indexers — it has no per-day split, so 24h and 7d exist only for money, not for calls. Inflows are USDC transfers on Base to a payout address that this service alone publishes; 30 of the last 30 days are scanned. A transfer is not a purchase: it can be a refund, a treasury move or a payment for something else, so inflows are a lower bound on volume, never revenue. 0 services can be measured this way; the rest share their address with other services or publish none, and are shown as “—” rather than $0.00.
Verified revenue would need a receipt from a payment processor. No such feed is connected, so the column exists and stays empty. Nothing on this page is a profit figure.
Filters combine: every additional chip narrows the set. Counts are computed with the same query that fills the list, so they cannot drift from it. Agents get the identical set over JSON at /api/v1/services — no key, 60 requests per minute.
The same services, ordered by money that actually arrived: 30-day earnings ranking. For the daily series and the coverage behind it, see measured agent-economy activity.
One prompt, and your agent searches 158,286 services itself.
Use https://agentmarketindex.com/api/v1/services to find one service for my task: filter by protocol and price, read each entry's provenance status before trusting a price, and give me the provider's own link — do not pay, sign up or spend anything.
Works in any client that can fetch a URL — Claude, ChatGPT, Cursor, a shell script. The endpoint is read-only and returns JSON; no key, no account.
https://agentmarketindex.com/api/v1/services · API reference