Sato Hub
ERC-8004

How many ERC-8004 agents are registered per day, by chain?

As of 2026-11-10, new ERC-8004 agent ids minted in one UTC day, per chain and never summed: 1,773 on Base, 1,325 on BNB Chain, 164 on X Layer and 20 more chains.data: MCP onchain_agent_get_trend(venue="erc8004", stage="registered_new_1d", grain="daily") · weekly reading of registered ids, JSON (not the daily count)

All numbers
  • As of2026-11-10

Each chain is its own registry, so there is no total. Past registration, from a sample of recent registrants rather than the whole registry: 100% of the owner wallets in the Base sample (22 of 22) sent a transaction beyond their registration in the last 7 days, read 2026-11-09.

ChainNew ids, latest dayDayMedian / dayLast 14 days
Base1,7732026-11-102,139.5(10d)
BNB Chain1,3252026-11-101,344.5(12d)
X Layer1642026-11-1014(13d)
Ethereum382026-11-1017(13d)
Tempo312026-11-1011(13d)
0G132026-11-103(13d)
Polygon22026-11-101(13d)
Abstract02026-11-100(13d)
Avalanche02026-11-100(13d)
Celo02026-11-105(13d)
Gnosis02026-11-101(13d)
Injective02026-11-100(13d)
Linea02026-11-100(13d)
Mantle02026-11-100(13d)
MegaETH02026-11-100(13d)
Metis02026-11-100(13d)
Monad02026-11-100(13d)
Morph02026-11-100(13d)
Optimism02026-11-100(13d)
Scroll02026-11-100(13d)
Shape02026-11-100(13d)
SKALE Base02026-11-100(13d)
Taiko02026-11-100(13d)
Arbitrumunknown——(0d)
GOAT Networkunknown——(0d)
Robinhood Chainunknown——(0d)
Measures
New agent ids the ERC-8004 Identity Registry minted in one UTC day, per chain. Never summed across chains.
Method
_lastId at the last block before 00:00 UTC closing 2026-11-10 minus _lastId at the last block before 00:00 UTC opening it (boundaries found by timestamp binary search; ERC-7201 slot on the singleton Identity Registry) — exact, whole population, no sampling
Unit
One registered agent id. An id is minted by any call to register(); it says nothing about whether the agent is funded, active or distinct.
Unknown
A day whose read failed is drawn as a gap and left out of the median. It is never counted as zero.
Stage
agent_metrics_daily · venue="erc8004" · stage="registered_new_1d"

Why sources disagree

Each tracker counts a different set of chains and decides what an agent is: every registered id, only ids with a registration file, or testnets too. A wider scope or a looser definition gives a bigger figure, so the figures cannot be lined up or added.

  • 8004scan ↗2,038,700

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

    Agents 8004scan indexes in this view.

    read 2026-11-11

  • 8004scan ↗2,098,805

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

    Agents 8004scan indexes in this view.

    read 2026-11-11

  • 8004scan ↗2,367,301

    agents · all networks, testnets included · all time

    Agents 8004scan indexes in this view.

    read 2026-11-11

  • agenteconomy.to ↗2,178,945

    agents · the chains agenteconomy.to tracks · all time

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

    read 2026-11-11 · source date 2026-11-11T03:39:48.319Z

Our own reading is the registry contract's own id counter on each chain, read directly and never summed. ERC-8004 agents by chain →

Figures other trackers publish, quoted with their source and read once a day. They are not Sato Hub's numbers and are never added together; “not read” means we hold no reading, never zero.

Reference

QuestionsShowHide

Questions this page answers

How many ERC-8004 agents are registered per day?
On 2026-11-10, the Identity Registry minted Base 1,773, BNB Chain 1,325, X Layer 164, Ethereum 38, Tempo 31, 0G 13, Polygon 2, Abstract 0, Avalanche 0, Celo 0, Gnosis 0, Injective 0, Linea 0, Mantle 0, MegaETH 0, Metis 0, Monad 0, Morph 0, Optimism 0, Scroll 0, Shape 0, SKALE Base 0, Taiko 0 new agent ids, one figure per chain. Chains read on an earlier day carry their own date in the table.
What is a typical day?
The median over the days actually read in the last 14: Base 2,139.5 (10 days read), BNB Chain 1,344.5 (12 days read), X Layer 14 (13 days read), Ethereum 17 (13 days read), Tempo 11 (13 days read), 0G 3 (13 days read), Polygon 1 (13 days read), Abstract 0 (13 days read), Avalanche 0 (13 days read), Celo 5 (13 days read), Gnosis 1 (13 days read), Injective 0 (13 days read), Linea 0 (13 days read), Mantle 0 (13 days read), MegaETH 0 (13 days read), Metis 0 (13 days read), Monad 0 (13 days read), Morph 0 (13 days read), Optimism 0 (13 days read), Scroll 0 (13 days read), Shape 0 (13 days read), SKALE Base 0 (13 days read), Taiko 0 (13 days read). Days whose read failed are left out rather than counted as zero.
Why is there no total across chains?
ERC-8004 is one contract deployed at the same address on several chains. An id on Base and an id on BNB Chain are two objects on two contracts, and one operator registering the same agent on four chains mints four ids, so a sum counts neither agents nor operators.
Is a new registration a new agent?
No. An id is minted by any call to register(); it says nothing about whether the agent is funded, answers, or differs from the id next to it. Whether registrants go on to transact is a separate page.
SourcesShowHide

Sources — the standard and its reference implementation

Cite this pageShowHide

Cite this

As of 2026-11-10, new ERC-8004 agent ids minted in one UTC day, per chain and never summed: 1,773 on Base, 1,325 on BNB Chain, 164 on X Layer and 20 more chains.

Sato Hub, "How many ERC-8004 agents are registered per day, by chain?", https://satohub.ai/numbers/erc-8004-registrations-per-day, as of 2026-11-10. Data CC-BY.

How this was measured

Method
The ERC-8004 Identity Registry's own agent-id counter (`_lastId`) read on each chain at the last block before the UTC midnight that closes the day, minus the same read at the last block before the midnight that opens it (both blocks found by timestamp), exact over the whole registry with no sampling, and unknown rather than zero on a chain whose node will not serve state that old.
Window
One UTC day, 00:00 to 00:00 UTC.
Data date
MCP call
onchain_agent_get_trend({"venue":"erc8004","chain":"Base","stage":"registered_new_1d","grain":"daily","points":14}) on https://satohub.ai/api/mcp
URL
none — The public exports carry the current weekly reading only; the daily series is served by the MCP call.

Pass another chain for its series; chains are never summed.

Machine source

  • MCP tool: https://satohub.ai/api/mcp → onchain_agent_get_trend({ venue: "erc8004", stage: "registered_new_1d", chain: "Base", grain: "daily", points: 14 })