How Agentic Payment Data Is Tracked

agentic payment data methodology
173,790,718
aggregate on-chain events
173,790,718
Aggregate events
5
Protocols tracked
11+
Chains tracked
210,211
Registered agents

Overall approach

EXPLAINER173.8M aggregate events · 5 protocols · daily refresh

Agent Economy is a daily-updated static dashboard for measurable on-chain agent activity. The project brief defines its core coverage as x402, ERC-8004, ERC-8183 / Virtuals ACP, Tempo MPP, and Olas across 11+ chains.

The methodology is deliberately conservative: each protocol keeps its native unit. x402 reports settlement transactions and USD volume, ERC-8004 reports registered agents, ACP reports lifecycle memos, MPP reports indexed channel events, and Olas reports autonomous agent transactions.

This avoids pretending that every protocol emits the same kind of economic event. The combined event total is a high-level footprint, while the page-level tables preserve protocol-specific meaning.

Current methodology snapshot

LIVEUpdated May 20, 02:36 AM UTC
MetricValueUnitdata.json fieldSource
Aggregate events173,790,718eventscomputed: x402 + baseAgentic + virtualsAcp + tempoMpp + olasAgent Economy aggregate logic
Protocols tracked5protocol familiescomputeTotals().protocolsAgent Economy README
Chains tracked11+chainscomputeTotals().chainsAgent Economy README
Registered agents210,211agentserc8004Registry.totalAgents@hashed_official / ERC-8004 Registry
Refresh cadenceDailyUTCGitHub Actions cronAgent Economy README
Last updated
. This route was prerendered with the same `data.json` values used by the dashboard.

How this data is tracked

METHODOLOGY
ProtocolUnitFieldsSourceCaveat
x402settlement transactions and USD volumex402.totalTxs, x402.totalVolume, x402.protocols, x402.chains@thechriscen / x402 Payment AnalyticsRaw settlements are not pure verified end-user commerce.
ERC-8004registered agents and registry chain distributionerc8004Registry.totalAgents, erc8004Registry.chains@hashed_official / ERC-8004 RegistryIdentity registration is separate from payment activity.
Virtuals ACPjob lifecycle memosvirtualsAcp.totalMemos, virtualsAcp.daily@hashed_official / Virtuals ACPMemos are workflow events, not necessarily completed purchases.
Tempo MPPRPC-indexed channel eventstempoMpp.totalEvents, tempoMpp.uniquePayers, tempoMpp.uniquePayeesTempo RPC indexerCoverage is Tempo-specific and early.
Olasautonomous agent transactionsolas.totalTxs, olas.chains, olas.weekly@adrian0x / Olas EcosystemKept separate from HTTP payment and registry metrics.

The fetch pipeline reads Dune latest results, optionally executes stale queries, merges Tempo RPC summary data, writes `public/data.json`, and relies on Vercel Git auto-deploy.

Data quality notes from the README apply across routes: raw counts include ecosystem testing, self-dealing, and infrastructure activity; genuine commerce is a subset of totals; off-chain payment protocols are not included.

All Stage 2 pages embed the current `data.json` values at build time so crawlers can read current metrics without executing JavaScript.

Data sources

SOURCES

FAQ

JSON-LD
How is agentic payment data tracked?+
Agent Economy combines public Dune sources and a Tempo RPC summary into data.json, then prerenders each route with those values at build time.
Why are ERC-8004 agents not counted as payment events?+
ERC-8004 measures registered agent identities. The methodology keeps it separate from payment or job-event metrics to avoid mixing units.
How often does the dataset update?+
The pipeline runs daily. This build embeds the dataset updated at 2026-05-20T02:36:31.998Z.
What are the main caveats?+
Raw on-chain activity can include testing, self-dealing, and infrastructure activity. The dataset tracks visible protocol activity, not audited organic commerce.

Related protocols and data

LINKS