Stacked by source. The agentic economy today is overwhelmingly sub-dollar.
Rough keyword-based categorization across both sources.
Each bar is a single endpoint's best dollar figure — price × transactions (observed on-chain where available). Color = source. A per-endpoint view; see the services table below for provider/actor/domain totals.
On-chain settlement makes demand observable. Unique payers are used (not raw call counts) to blunt memecoin-farming noise.
One row per service (deduped across sources). Per horizon (30-day / all-time) we show Est $ (price × real transactions, our estimate) beside Obs $ (real settled USDC, ⛓ — ties out to x402scan) so you can see where the estimate diverges from what was actually paid. The Σ columns are the median of the available signals — the overall-ranking column. Click a row to filter the endpoint table to that service. Sortable by any column.
The dataset primitive is a priced endpoint (a row); a service (provider / actor / domain) is the top level. For each service we show, per horizon, an Estimate and an Observation side by side:
stats.overall for the service's recipient wallets. It
ties out to x402scan (e.g. a service showing $152k / 13.15M tx here reads the
same on x402scan). mppscan settlement works the same way. Off-chain sources (Apify) have no
observed $.toolCalls counter is NOT settlement — blockrun reads 0 there despite 13M real
transactions — so it's not used as a spend basis.)Unique buyers counts the distinct wallets/accounts that paid (30-day) — not transactions: one buyer can transact many times, so this is much smaller than the tx count (e.g. a service with 13M transactions but ~1,000 buyers is automated/whale traffic, not a broad user base). It's the wash-resistant demand signal — raw transaction counts are trivially inflated, unique payers are not. Sources differ: on-chain unique payers/buyers (CDP, x402scan, mppscan) vs. Apify platform users. ⛓ marks real on-chain settlement.
| Loading dataset… |