Sato Hub
ERC-8004

Which ERC-8004 agent count is which?

As of 2026-10-13, 8004scan indexes 580,804 agents with a registration file on mainnet chains and the registry on 0G has issued 3,897,594 ids (read 2026-10-14), counts of different things that are never added.

All numbers
  • As of2026-10-13

Agents trackers index

Counts from outside trackers. Each is a view with its own chain scope and its own idea of what an agent is.

  • 8004scan ↗580,804

    agents · mainnet chains, agents with a registration file · all time

    Agents 8004scan indexes in this view.

    stage: agents the tracker indexes · read 2026-10-13

  • 8004scan ↗unknown

    agents · mainnet chains, including ids without a registration file · all time

    Agents 8004scan indexes in this view.

    stage: agents the tracker indexes · read 2026-10-13

    the latest read did not return this figure

  • 8004scan ↗903,627

    agents · all networks, testnets included · all time

    Agents 8004scan indexes in this view.

    stage: agents the tracker indexes · read 2026-10-13

  • agenteconomy.to ↗638,452

    agents · the chains agenteconomy.to tracks · all time

    Total agents in agenteconomy.to’s ERC-8004 table, on the chains it tracks.

    stage: agents the tracker indexes · read 2026-10-13 · source date 2026-10-13T04:27:28.886Z

Ids the registry has issued

Our own read of the registry contract on each chain. A registered id is the ceiling on agents, not a count of agents that answer.

Ids issued, one row per chain

The registry contract's own id counter, read on each chain it is deployed to. One row per chain, each with the day it was read. There is no total, because id 41 on one chain and id 41 on another are different agents on different contracts.

ChainIds issuedRead onHow read
0G3,897,5942026-10-14read from the contract each day
BNB Chain373,7072026-10-14read from the contract each day
Base117,1552026-10-14read from the contract each day
Ethereum53,9442026-10-14read from the contract each day
Abstract16,9182026-10-14read from the contract each day
X Layer14,9142026-10-14read from the contract each day
MegaETH12,7272026-10-14read from the contract each day
Monad10,4122026-10-14read from the contract each day
Celo9,9072026-10-14read from the contract each day
Robinhood Chain8,7892026-10-14read from the contract each day
Gnosis4,1602026-10-14read from the contract each day
SKALE Base2,2312026-10-14read from the contract each day
Shape2,0982026-10-14read from the contract each day
Avalanche1,8452026-10-14read from the contract each day
Arbitrum1,6252026-10-14read from the contract each day
Injective9322026-10-14read from the contract each day
Polygon6862026-10-14read from the contract each day
Optimism5652026-10-14read from the contract each day
Tempo3152026-10-14read from the contract each day
Mantle1442026-10-14read from the contract each day
Metis1382026-10-14read from the contract each day
Linea1152026-10-14read from the contract each day
Scroll1082026-10-14read from the contract each day
Taiko942026-10-14read from the contract each day
GOAT Network882026-10-14read from the contract each day
Morph112026-10-14read from the contract each day

Tools in this directory

Tools that say they support the standard. A different object again.

  • Sato Hub directory17

    tools that list ERC-8004 among their standards · live listings in this directory · as listed on the day we read it

    Tools and projects in the Sato Hub directory that say they support ERC-8004. A tool is not an agent and not a registration.

    stage: tools listed · read 2026-10-14

Registered versus answered our probe

Per chain: the ids issued at the top, and below it a floor and a ceiling for the agents that answered our probe, with the sample behind each.

Registered versus answered our probe, per chain

Ids issued is the ceiling on agents. The floor is the share of agents with a probe result that answered our probe on the day shown; the ceiling adds probes that were inconclusive. A chain we do not probe is unknown, and a chain with too few readings says so.

ChainIds issuedFloor: answered our probeCeiling: answered or inconclusiveAgents with a resultDesignProbed on
0G3,897,594unknownunknownunknownunknownunknown
BNB Chain373,707unknownunknownunknownunknownunknown
Base117,155unknownunknownunknownunknownunknown
Ethereum53,944unknownunknownunknownunknownunknown
Abstract16,918unknownunknownunknownunknownunknown
X Layer14,914unknownunknownunknownunknownunknown
MegaETH12,727unknownunknownunknownunknownunknown
Monad10,412unknownunknownunknownunknownunknown
Celo9,907unknownunknownunknownunknownunknown
Robinhood Chain8,789unknownunknownunknownunknownunknown
Gnosis4,160unknownunknownunknownunknownunknown
SKALE Base2,231unknownunknownunknownunknownunknown
Shape2,098unknownunknownunknownunknownunknown
Avalanche1,845unknownunknownunknownunknownunknown
Arbitrum1,625unknownunknownunknownunknownunknown
Injective932unknownunknownunknownunknownunknown
Polygon686unknownunknownunknownunknownunknown
Optimism565unknownunknownunknownunknownunknown
Tempo315unknownunknownunknownunknownunknown
Mantle144unknownunknownunknownunknownunknown
Metis138unknownunknownunknownunknownunknown
Linea115unknownunknownunknownunknownunknown
Scroll108unknownunknownunknownunknownunknown
Taiko94unknownunknownunknownunknownunknown
GOAT Network88unknownunknownunknownunknownunknown
Morph11unknownunknownunknownunknownunknown

Our reading

To say how many ids exist on one chain, use the registry's counter for that chain. To compare trackers, compare their views, not their totals: mainnet with a registration file, mainnet with or without one, and every network including testnets are three different questions.

None of these is a count of agents that answer. The range table below shows, per chain we probe, the share that answered our probe on the day shown as a floor and a ceiling; a chain we do not probe is unknown, and a chain with too few readings says so.

The weekly trend of the registry counter, one row per chain and never summed, is on its own page. ERC-8004 registered agents, by chain (weekly) →

Why the numbers differ

  • Scope: some views cover mainnet chains only, others add testnets, and each tracker covers its own list of chains.
  • Definition: a registered id, an id with a registration file and an agent that answers are three different things, and a tracker picks one.
  • Object: the directory counts tools that cite the standard, not registrations.
  • Chains are never summed. A registration on one chain is a different object from a registration on another, and one operator can register the same agent on several.

Source: 8004scan (8004scan.io) · Source: agenteconomy.to

Figures other trackers publish, quoted with their source and read once a day or once a week. They are not Sato Hub's numbers and are never added together; “unknown” means we hold no reading, never zero. Data CC-BY-4.0 — attribution: data by satohub.ai.

Reference

QuestionsShowHide

Questions this page answers

Why do 8004scan's numbers differ from the registry's own count?
Read on 2026-10-13, 8004scan showed 580,804 agents on mainnet chains with a registration file and 903,627 across all networks including testnets. The registry contract counts every id issued on a chain, with or without a file, so the tracker views and the registry count different things and are not added.
How many ERC-8004 agents answered a probe?
Not enough readings yet. The registry count is the ceiling on agents; the share that answered our probe is shown per chain once enough agents have a probe result, and until then it is unknown, never zero.
Is there a single ERC-8004 agent total?
No. A registration on one chain is a different object from one on another, trackers cover different chains and definitions, and the directory counts tools (17 read 2026-10-14). This page publishes no total (latest reading 2026-10-13).
SourcesShowHide

Sources — the standard and where each tracker publishes

Cite this pageShowHide

Cite this

As of 2026-10-13, 8004scan indexes 580,804 agents with a registration file on mainnet chains and the registry on 0G has issued 3,897,594 ids (read 2026-10-14), counts of different things that are never added.

Sato Hub, "Which ERC-8004 agent count is which?", https://satohub.ai/numbers/erc-8004-agent-count-which-number, as of 2026-10-13. Data CC-BY.

How this was measured

Method
Each tracker's own agent count is read once a day from the place it publishes it (8004scan's global stats in three views, agenteconomy.to's data file), set beside the ERC-8004 Identity Registry's own agent-id counter (`_lastId`, one storage read at the chain head) on each chain and the number of directory listings that cite the standard, none of them summed.
Window
The latest daily reading of each source and of each chain's counter, dated per row.
Data date
MCP call
onchain_agent_get_trend({"venue":"erc8004","chain":"Base","stage":"registered","grain":"weekly","points":1}) on https://satohub.ai/api/mcp
URL
https://satohub.ai/api/export/adoption.json?stage=registered&venue=erc8004
Recount
curl -s 'https://api.8004scan.io/api/v1/stats/global?is_testnet=false&is_registered=true'
curl -s https://agenteconomy.to/data.json

The MCP call and the export return the registry counter for one chain; pass another chain for its row. The tracker figures are read from the sources in the recount.