x402 Transactions Tracker: Daily Payments and Volume
x402 payments settled per day, the USDC they move, their size and their chains, counted from the settlement transactions themselves.
Multi-chainBaseSolana+2Table · StrataPlanned
ERC-8004 Agent Registry: Registered AI Agents by Chain
How many AI agents are registered under ERC-8004, and which have the most feedback?
Every AI agent registered under ERC-8004, with its owner, chain, registration date and the reputation feedback it has received.
ShareEmail it
Blueprint
What the table will hold.
The table as it will open in Strata. Each figure is named here and arrives with its receipt; until its data is published, its place stays empty.
One row One row per registered agent per chain, on the latest complete daySorted by Feedback, highest first
| Agent id | Agent | Chain | Owner | Registered | Registration file | Feedback | Distinct clients | Last feedback | Receipt |
|---|---|---|---|---|---|---|---|---|---|
- Agent id agent_id Number
- The agent's token id in that chain's identity registry.
- Agent agent_name Text
- The name in the agent's current registration file, or its id where the file gives none.
- Chain chain Chain
- The chain whose identity registry minted this agent.
- Owner owner Address
- The address that owns the agent's identity token at the latest block.
- Registered registered Date
- The date of the agent's Registered event.
- Registration file agent_uri Link
- The agent's current URI, from its latest Registered or URIUpdated event.
- Feedback feedback_count Number
- NewFeedback events for this agent, net of revoked feedback.
- Distinct clients distinct_clients Number
- Distinct client addresses whose feedback for this agent was not revoked.
- Last feedback last_feedback Date
- The date of the agent's most recent feedback.
- Receipt receipt Link
- The blocks, hashes and logs behind the row.
Filter by Chain, Owner.
About
What it answers, and for whom.
ERC-8004, known as Trustless Agents, gives AI agents an on-chain identity and a place to collect reputation. An identity registry mints each agent as an ERC-721 token that points to a registration file describing it, and a reputation registry lets clients leave feedback on the agents they used. This table lists every registered agent from those registries' events, chain by chain.
Registration is cheap and open, so the number of agents says little alone. Feedback, revocations and responses show which agents are actually used and rated, and by how many distinct clients, which is harder to manufacture than registrations.
Sort by feedback received or by registration date, filter by chain or owner and open any row to see the registration, transfer and feedback transactions behind it.
Method
How it will be measured.
Every figure will be read at a block, kept with its source and its exact read, and open a receipt anyone can re-check.
How receipts work →- Agents come from Registered events of each chain's ERC-8004 identity registry, with the agent id, owner and agent URI; ownership then follows the registry's ERC-721 Transfer logs.
- URI and metadata changes are read from URIUpdated and MetadataSet events, so each row shows the agent's current registration file and when it last changed.
- Feedback counts come from the reputation registry's NewFeedback events per agent id, net of FeedbackRevoked events, with distinct client addresses counted separately.
- Registry addresses are confirmed per chain before they are read, and the validation registry is added once an official deployment exists.
- Every row carries a receipt: the block, its hash and the logs behind each figure.
The data it needs
Read from chain state and history
- agent_payments_dailyTo buildAI agents and agent paymentsAgent tokens (supply, holders, trading) and agent payments such as x402 settlements in stablecoins, per day.
- address_labelsTo buildAddress labelsLabels for known addresses: exchanges, bridges, protocols, funds, treasuries, sanctioned addresses and known attackers.
- ERC-8004 identity registry Registered events and ERC-721 Transfer logs, per chain
- URIUpdated and MetadataSet events for agent URI and metadata changes
- Reputation registry NewFeedback, FeedbackRevoked and ResponseAppended events per agent id
- Validation registry request and response events once an official deployment exists
- Registry deployment addresses, confirmed per chain
Questions
Questions people ask.
What is ERC-8004?
ERC-8004, Trustless Agents, is an Ethereum standard for discovering and trusting AI agents across organizations. It defines three registries: identity, where each agent is an ERC-721 token; reputation, where clients post feedback; and validation, where independent checks of an agent's work can be recorded.
When did ERC-8004 launch on mainnet?
Its registries went live on Ethereum mainnet in January 2026 and have been deployed on other chains, including Base, at the same addresses. This table lists each chain where a deployment has been confirmed.
How do I register an AI agent under ERC-8004?
The agent's owner calls the identity registry's register function with an agent URI that points to a registration file listing the agent's name, services, endpoints and supported trust models. The registry mints an ERC-721 token whose id is the agent id.
Does ERC-8004 reputation feedback prove an agent is trustworthy?
No. Anyone can post feedback, so the registry records signals, not verdicts. The table shows feedback counts, distinct clients and revocations, which help separate many independent ratings from a few addresses rating each other.
Is the agent registration file stored on-chain?
Usually not. The registry stores a URI on-chain, which can point to IPFS, a website or a data URI, and the file it points to can change. The table shows the current URI and when it last changed.
- Identity registry
- The ERC-8004 contract that mints each agent as an ERC-721 token, with an agent URI pointing to its registration file.
- Reputation registry
- The ERC-8004 contract where clients post feedback on agents they used; feedback can be revoked and answered.
- Validation registry
- The ERC-8004 contract for recording independent checks of an agent's work, such as re-execution or proofs.
- Agent URI
- The address of an agent's registration file, which lists its name, services, endpoints and the trust models it supports.
Related
More apps like this.
Virtuals Protocol Agents: Launches, Jobs and Payments
How many agents launch on Virtuals and graduate to DEX pools, and the jobs and payments they settle through the Agent Commerce Protocol.
BaseSolanaEthereumAI Agents in Crypto: Monthly On-Chain Report
A dated monthly review of what AI agents did on-chain: payments settled, agents registered, agent tokens launched and jobs paid.
Multi-chainBaseSolana+2x402 Facilitators and Paid Services Ranked
Which facilitators settle the most x402 payments, which paid services receive the most and how each splits across chains, from settlements.
Multi-chainBaseSolana+2EIP-7702 Adoption: Delegated EOAs and Top Contracts
How many accounts have delegated their code under EIP-7702, the contracts they point to and how much of it looks like sweeper scams.
Multi-chainEthereumBase+3AI Agent Tokens Ranked by Holders and DEX Volume
AI agent tokens from Virtuals and other agent launchpads, sorted by holders, on-chain trading volume, supply and DEX-implied value.
Multi-chainBaseSolana+1Build ERC-8004 Agent Registry: Registered AI Agents by Chain on verified data.
Start free in Voltfin Studio: boards, tables and reports where every number opens its receipt. Tell us which data you need first and we will build it next.