Agentic Payment Data API and data.json Schema

agentic payment data API
173,790,718
events available in data.json
173,790,718
combinedEvents
144,008,894
x402.totalTxs
210,211
erc8004Registry.totalAgents
12,297,239
virtualsAcp.totalMemos

What does the data API expose?

EXPLAINER173.8M events · public JSON · daily refresh

Agent Economy exposes the same dataset that powers the dashboard at `/data.json`. It is machine-readable JSON intended for researchers, builders, journalists, and AI/search systems that need protocol-level agent economy data without scraping the UI.

`data.json` includes aggregate x402, ERC-8004, Virtuals ACP, Tempo MPP, and Olas fields. Tempo also has a raw summary endpoint at `/tempo-data.json` for the RPC-indexed MPP source.

The dataset refreshes through the daily GitHub Actions pipeline. Vercel rebuilds after data changes, so route HTML and JSON stay aligned with the latest committed data.

Current data.json fields

LIVEUpdated May 20, 02:36 AM UTC
MetricValueUnitdata.json fieldSource
combinedEvents173,790,718computed countcomputed aggregateAgent Economy aggregate logic
x402.totalTxs144,008,894transactionsx402.totalTxsdata.json
erc8004Registry.totalAgents210,211agentserc8004Registry.totalAgentsdata.json
virtualsAcp.totalMemos12,297,239memosvirtualsAcp.totalMemosdata.json
tempoMpp.totalEvents26,457eventstempoMpp.totalEventsdata.json
olas.totalTxs16,449,330transactionsolas.totalTxsdata.json
updatedAt2026-05-20T02:36:31.998ZISO datetimeupdatedAtdata.json
Last updated
. This route was prerendered with the same `data.json` values used by the dashboard.

How this data is tracked

METHODOLOGY
ProtocolUnitFieldsSourceCaveat
x402count, USD, facilitator share, chain rowsx402.totalTxs, x402.totalVolume, x402.protocols, x402.chains/data.jsonSettlement activity, not audited organic commerce.
ERC-8004agent count and chain rowserc8004Registry.totalAgents, erc8004Registry.chainsTracked, erc8004Registry.chains/data.jsonIdentity supply metric, not a payment count.
Virtuals ACPmemo count and daily rowsvirtualsAcp.totalMemos, virtualsAcp.daily/data.jsonLifecycle memos, not necessarily completed purchases.
Tempo MPPevent count, addresses, event typestempoMpp.totalEvents, tempoMpp.uniquePayers, tempoMpp.uniquePayees, tempoMpp.byType/data.json and /tempo-data.jsonTempo-specific RPC indexer coverage.
Olastransaction count, chain rows, weekly rowsolas.totalTxs, olas.chains, olas.weekly/data.jsonAutonomous agent activity tracked separately.

Fetch `/data.json` directly for the canonical dashboard dataset. Use `/tempo-data.json` only when you need to inspect the Tempo MPP summary source separately.

Fields are intentionally nested by protocol so consumers can avoid mixing units. Treat `combinedEvents` as a dashboard aggregate, not a universal economic volume metric.

The license for dataset schema in the existing homepage JSON-LD is CC BY 4.0. The repo code remains MIT licensed.

Data sources

SOURCES

FAQ

JSON-LD
Where is the Agent Economy data API?+
The public dataset is available at https://agenteconomy.to/data.json, with a Tempo-specific source summary at https://agenteconomy.to/tempo-data.json.
Can I use data.json without rendering the dashboard?+
Yes. The file is plain JSON and contains the same protocol fields embedded into the prerendered route HTML.
How fresh is the API data?+
The current build embeds data updated at 2026-05-20T02:36:31.998Z. The pipeline is configured for a daily UTC refresh.
What unit should I use for combinedEvents?+
Use count, and label it as an aggregate protocol-event footprint. Do not treat it as USD volume or verified organic commerce.

Related protocols and methodology

LINKS