Sato Hub
Measured daily

The Onchain Agent Economy

See how many agents register and how much x402 payment activity happens, chain by chain.

Take the data
  • Updated2026-10-16
  • Free to reuseCC-BY
Registered agentsRegistered agentsAgent IDs in the ERC-8004 registry on the largest chain, read from the chain itself. Every chain keeps its own count; the page never adds chains together.
3,919,209
0G · largest chainas of
New registrationsNew registrationsAgent IDs added to the ERC-8004 registry in one full UTC day: the newest day with a reading, on the chain that added the most among the chains read that day. That day can trail Latest day below when a chain's read lands late. Today's partial day never counts.
23,106
Base · one UTC dayas of
x402 transactionsx402 transactionsTransactions sent by known x402 payment processors in one UTC day, on the busiest of the chains read that day. An upper bound: it counts every transaction those keys send, and not each one is an agent paying for something.
6
Sei · one UTC dayas of
Chains trackedChains trackedChains with at least one reading in the latest weekly collection. Each chain's numbers stay separate.
13
Each read on its ownas of

One full UTC day

Latest day

Latest dayA day counts once it is over in UTC and our daily read has finished it. Today's partial readings never appear here.
UTC

New agent registrations

+23,106

Base

  • 0G+10,428
  • BNB Chain+878

Agent IDs added that day, per chain.

x402 transactions

52,530

Solana

  • Avalanche2
  • Sei2

Sent by x402 payment processors. An upper bound.

x402 endpoints asking to be paid

83.3%

Basen=60 · 36,387 listed

  • Solana66.7%n=60 · 636 listed

Share of sampled listings that answered with a payment request.

How we measureShowHide

New ERC-8004 agent identities. Registrations on 2026-10-15, per chain — top 4 of 26 chains read. Chains are never added together.

x402 facilitator throughput. Transactions sent by known facilitator keys — an upper bound, not screened for self-payments. Not every such transaction is an agent paying for something. Held from these figures: Pieverse on BNB Chain; Polygon Facilitator on Polygon; Figment on Solana; FluxA on Base; three.ws on Solana — the readings are exact but are not shown as x402 activity while the evidence behind each hold stands. Some shown readings carry a note about what the sample could not see. An operator is held for a day automatically when, on at least 50 sampled settlements, we are 95% confident that 90% or more of them paid one address — and when a new or sudden reading of 50 or more transactions could not be sampled at all, until it is checked. Reasons and evidence are on /numbers/x402-facilitator-throughput.

Listed x402 resources that answer HTTP 402. A sample of Bazaar listings probed that day; answering 402 means the endpoint asks for payment, not that anyone paid.

A day counts once it is over in UTC and our daily read has finished it; today's partial readings never appear here. Each figure is one chain or one operator. None is a total.

Weekly read

Chain by chain

What the x402 payment rail moved, chain by chain.

Transactions · one day

Transactions · one dayTransactions sent by known x402 payment-processor keys on one UTC day. An upper bound: not screened for self-payments or test traffic.
  • Solana52,530on 2026-10-14
  • Sei6on 2026-10-15
  • Avalanche6on 2026-10-15
  • Robinhood Chain1on 2026-10-15
  • Abstract0on 2026-10-15

Settlements to listed sellers · 7 days

Settlements to listed sellers · 7 daysUSDC transfers to a seller listed in the Coinbase x402 Bazaar. Repeat sellers only keeps a seller with at least three transfers from at least two different payers in the window (Artemis's rule). The share is two exact counts from the same window, divided, never a sample scaled up.
  • Base7 days to 2026-10-12
    All
    288,034
    Repeat sellers only
    286,787
    Share
    99.6%
All x402 readings (107)ShowHide
ReadingChainValueSampleAs of
facilitator txs 1d — AnySpenddailyBasenot measured2026-10-15
facilitator txs 1d — AurraClouddailyBasenot measured2026-10-15
facilitator txs 1d — BitrefilldailyBasenot measured2026-10-15
facilitator txs 1d — CascadedailyBasenot measured2026-10-15
facilitator txs 1d — CodeNutdailyBasenot measured2026-10-15
facilitator txs 1d — CorbitsdailyBasenot measured2026-10-15
facilitator txs 1d — FluxAdailyBasenot measured2026-10-15
facilitator txs 1d — HeuristdailyBasenot measured2026-10-15
facilitator txs 1d — MeridiandailyBasenot measured2026-10-15
facilitator txs 1d — MogamidailyBasenot measured2026-10-15
facilitator txs 1d — OboldailyBasenot measured2026-10-15
facilitator txs 1d — OpenFacilitatordailyBasenot measured2026-10-15
facilitator txs 1d — OpenmiddailyBasenot measured2026-10-15
facilitator txs 1d — OpenX402dailyBasenot measured2026-10-15
facilitator txs 1d — PolymerdailyBasenot measured2026-10-15
facilitator txs 1d — PrimerdailyBasenot measured2026-10-15
facilitator txs 1d — RelAIdailyBasenot measured2026-10-15
facilitator txs 1d — thirdwebdailyBasenot measured2026-10-15
facilitator txs 1d — TreasuredailyBasenot measured2026-10-15
facilitator txs 1d — Ultravioleta DAOdailyBasenot measured2026-10-15
facilitator txs 1d — CodeNutdailySolana02026-10-15
facilitator txs 1d — Virtuals Protocol (ACPX)dailyBasenot measured2026-10-15
facilitator txs 1d — x402 JobsdailyBasenot measured2026-10-15
facilitator txs 1d — x402.rsdailyBasenot measured2026-10-15
facilitator txs 1d — PayAIdailyAvalanche62026-10-15
facilitator txs 1d — DexterdailyAvalanche02026-10-15
facilitator txs 1d — AnySpenddailyAvalanche02026-10-15
facilitator txs 1d — AnySpenddailyAbstract02026-10-15
facilitator txs 1d — OboldailyEthereum02026-10-15
facilitator txs 1d — AnySpenddailyEthereum02026-10-15
facilitator txs 1d — DaydreamsdailyEthereum02026-10-15
facilitator txs 1d — DexterdailyWorld Chain02026-10-15
facilitator txs 1d — PrimerdailyRobinhood Chain12026-10-15
facilitator txs 1d — DexterdailyRobinhood Chain02026-10-15
facilitator txs 1d — AnySpenddailyOptimism02026-10-15
facilitator txs 1d — DexterdailyOptimism02026-10-15
facilitator txs 1d — OpenX402dailyMonad02026-10-15
facilitator txs 1d — PieversedailyMonad02026-10-15
facilitator txs 1d — DexterdailyMonad02026-10-15
facilitator txs 1d — AnySpenddailyBNB Chain02026-10-15
facilitator txs 1d — DexterdailyBNB Chain02026-10-15
facilitator txs 1d — HeuristdailyX Layer02026-10-15
facilitator txs 1d — PieversedailyX Layer02026-10-15
facilitator txs 1d — PayAIdailyX Layer02026-10-15
facilitator txs 1d — Coinbase CDPdailySolana2,6912026-10-15
facilitator txs 1d — PayAIdailySolana1,1352026-10-15
facilitator txs 1d — three.wsdailySolana02026-10-15
facilitator txs 1d — PayAIdailySei62026-10-15
facilitator txs 1d — PrimerdailySKALE Base02026-10-15
facilitator txs 1d — DexterdailySKALE Base02026-10-15
facilitator txs 1d — PayAIdailySKALE Base02026-10-15
facilitator txs 1d — x402.rsdailyPolygon02026-10-15
facilitator txs 1d — thirdwebdailyPolygon02026-10-15
facilitator txs 1d — CorbitsdailyPolygon02026-10-15
facilitator txs 1d — AnySpenddailyPolygon02026-10-15
facilitator txs 1d — DexterdailyPolygon02026-10-15
facilitator txs 1d — PayAIdailyPolygon22026-10-15
facilitator txs 1d — DexterdailySolana7672026-10-15
facilitator txs 1d — AnySpenddailySolana02026-10-15
facilitator txs 1d — x402 JobsdailySolana02026-10-15
facilitator txs 1d — Ultravioleta DAOdailySolana02026-10-15
facilitator txs 1d — RelAIdailySolana02026-10-15
facilitator txs 1d — OpenX402dailySolana02026-10-15
facilitator txs 1d — OpenFacilitatordailySolana12026-10-15
facilitator txs 1d — DaydreamsdailySolana02026-10-15
facilitator txs 1d — CorbitsdailySolana02026-10-15
facilitator txs 1d — BitrefilldailySolana02026-10-15
facilitator txs 1d knowndailyAbstract02026-10-15
facilitator txs 1d knowndailyEthereum02026-10-15
facilitator txs 1d knowndailyWorld Chain02026-10-15
facilitator txs 1d knowndailyRobinhood Chain12026-10-15
facilitator txs 1d knowndailyOptimism02026-10-15
facilitator txs 1d knowndailyMonad02026-10-15
facilitator txs 1d knowndailyX Layer02026-10-15
facilitator txs 1d knowndailySei62026-10-15
facilitator txs 1d knowndailySKALE Base02026-10-15
facilitator txs 1d knowndailyAvalanche62026-10-15
facilitator txs 1d knowndailyArbitrum02026-10-15
facilitator txs 1d knowndailyBasenot measured2026-10-15
facilitator txs 1d — PayAIdailyArbitrum02026-10-15
facilitator txs 1d — DexterdailyArbitrum02026-10-15
facilitator txs 1d — AnySpenddailyArbitrum02026-10-15
facilitator txs 1d — CascadedailySolana02026-10-15
facilitator txs 1d — AurraClouddailySolana02026-10-15
facilitator txs 1d — Coinbase CDPdailyBasenot measured2026-10-15
facilitator txs 1d — PayAIdailyBasenot measured2026-10-15
facilitator txs 1d — QuestflowdailyBasenot measured2026-10-15
facilitator txs 1d — DexterdailyBasenot measured2026-10-15
facilitator txs 1d — DaydreamsdailyBasenot measured2026-10-15
facilitator txs 1d — PieversedailyBasenot measured2026-10-15
facilitator txs 1d — xEchodailyBasenot measured2026-10-15
facilitator txs 1d — 402104 (Load Network)dailyBasenot measured2026-10-15
facilitator txs 1d — FigmentdailySolana47,0942026-10-14
facilitator txs 1d knowndailySolana52,5302026-10-14
By facilitator (sampled senders) — unknown facilitator (0x0f99…afc2)weeklyBase4n=2002026-10-12
gasless usdc attribution rate artemisweeklyBase48.2%n=51312026-10-12
settlement share passing artemisweeklyBase99.6%n=2880342026-10-12
Sellers actually paid (Artemis rule)weeklyBase902of 1,5302026-10-12
Settlements to catalogued sellers (Artemis rule: ≥3 tx from ≥2 payers)weeklyBase286,7872026-10-12
Sellers actually paid (machine noise excluded)weeklyBase808of 1,5302026-10-12
Settlements to catalogued sellers (machine noise excluded)weeklyBase274,3832026-10-12
Sellers actually paidweeklyBase1,229of 1,5302026-10-12
Settlements to catalogued sellers (nominal)weeklyBase288,0342026-10-12
By facilitator (sampled senders) — Coinbase CDPweeklyBase191n=2002026-10-12
By facilitator (sampled senders) — unknown facilitator (other: 2 addresses, < 3 each)weeklyBase3n=2002026-10-12
By facilitator (sampled senders) — Ultravioleta DAOweeklyBase1n=2002026-10-12
By facilitator (sampled senders) — PayAIweeklyBase1n=2002026-10-12
How we measureShowHide

Settlements are USDC transfers to a seller address listed in the Coinbase x402 Bazaar, read from public logs. The full count includes machine noise; “repeat sellers only” (Artemis's rule) keeps only sellers with at least three transfers from at least two distinct payers. Payment-processor throughput counts transactions sent by keys we can attribute to an x402 payment processor. It counts every such transaction, which is why it is an upper bound.

No row here covers Solana settlement, and by transaction count x402 mostly settles there. A value that could not be read says “not measured” with the reason; it never rounds to zero.

Held from these figures: Pieverse on BNB Chain; Polygon Facilitator on Polygon; Figment on Solana; FluxA on Base; three.ws on Solana — the readings are exact but are not shown as x402 activity while the evidence behind each hold stands. Some shown readings carry a note about what the sample could not see. An operator is held for a day automatically when, on at least 50 sampled settlements, we are 95% confident that 90% or more of them paid one address — and when a new or sudden reading of 50 or more transactions could not be sampled at all, until it is checked. Reasons and evidence are on /numbers/x402-facilitator-throughput.

Reading these numbersShowHide

Sato Hub measures 12 of 13 agent platforms from public chain data on 13 chains, each reported on its own, as of 2026-10-16.

Reading the numbers

  • Nothing here adds up, on purpose. An ERC-8004 registration, an Olas staked service, a Virtuals token launch and a paid Mech task are different objects. There is no total on this page and none in the export.
  • Every number names its step and its chain. Each answer picks the largest single chain and says how many chains were counted separately.
  • A sampled rate is never multiplied by a population. You will not find an “estimated active agents” figure here, because we would be making it up.
  • Missing readings say so. Where a public node prunes its history we say “not measured” and why. A missing reading shows as n/a and never rounds to zero.
  • Thin samples are kept, not quoted. A rate on fewer than 20 observations reads “not enough readings (n=…)”; the detail is on each registry's page.
  • Solana is covered as an upper bound. The Solana identity registries are counted by program account (at most this many), and Tempo's memo-tagged transfers are counted as MPP-shaped settlement. No row here covers Solana payment settlement.

What this data cannot settle

  • Whether a registered agent is an agent. Registration is permissionless and free on most of these registries. It proves an entry exists, not that software runs behind it.
  • What BNB Chain agents do after registering. Its count is exact and daily; its lifecycle is not measurable over a 30-day window from any keyless endpoint we could find. The log archive is roughly two hours deep.
  • Solana payments, and whether a Solana account is an agent. The Solana registries are read by program-account count, an upper bound that includes unused and duplicate accounts. Solana x402 settlement needs an indexer we do not run. Any claim about “the agent economy” built from this page should say both.
  • Whether a smart account is an agent. Only some sampled smart accounts also held an ERC-8004 agent ID or paid a listed x402 seller in the same week, and the share differs by chain. See Wallet providers for each chain's own share.
  • Who runs a wallet. These are observations of public software. No identities, no IPs, no per-caller profiles.

What we cannot attribute

13 of 46 confirmed smart-account contracts have no directory listing to attribute them to. Privy (server and embedded), Turnkey, Coinbase CDP Server Wallets, Dynamic and Fireblocks can't be measured from chain data at all: they mint ordinary EOAs, and when their user deploys a smart account the factory belongs to a different company. So the Wallet providers view covers account-abstraction vendors well and wallet-infrastructure vendors not at all. That follows from how these wallets are built; more effort would not close it.

The two headline numbers

How measured · The ERC-8004 Identity Registry's own agent-id counter (`_lastId`, one storage read at the chain head) on that chain, covering the whole registry with no sampling. The latest daily reading.

How measured · For every catalogued x402 facilitator key, the transactions it sent in the last complete UTC day (on EVM chains its nonce at the last block before each UTC midnight, end minus start; on Solana its fee-payer signatures in that day), summed per chain over the operators not held from public figures — an upper bound on settlements, not screened for self-payments. The last complete UTC day.

Reference

QuestionsShowHide

Questions people ask about the onchain agent economy

How many onchain agents are there?
No single number answers that, and this page refuses to invent one. 12 venues are measured for the week beginning 2026-W42, each counting a different object: an ERC-8004 registration, an Olas staked service, a Virtuals launch and a paid task are four things. Every figure is published with its stage named.
Why is there no total?
Because a total would be wrong in a way that looks right. The same operator can register on four chains and appear four times; a launchpad token and a registry id are not comparable units. There is no total on this page and none in the export.
What cannot be measured?
1 catalogued venue cannot be censused from chain data at all, and each is listed with the architectural reason rather than dropped. An absent fingerprint is a finding.
How current are these figures?
They are collected weekly; this view is the week beginning 2026-W42, and each row carries its own coverage window. A row that banked nothing is null — unknown, never zero.
Can I reuse these numbers?
Yes, under CC-BY, from the adoption export in JSON, CSV and NDJSON. Carry the stage name and the evidence tier with the figure; rates computed on fewer than 20 observations are stored but are not findings.
SourcesShowHide

Sources — the standards these venues implement

Cite this pageShowHide

Cite this page

Sato Hub. "The onchain agent economy." Sato Hub, updated 2026-10-16, accessed 2026-10-16. https://satohub.ai/agent-economy

Data last refreshed 2026-10-16; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.

Join the Sato Hub Briefing

Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.