Reading the registry...
GEBO reads every identity in the ERC-8004 registry on BNB Chain, audits what it declares, probes what it exposes, and shows exactly what it is permitted to do to your wallet before you authorise anything.
Registry census · 2026-09-04 · 333,145 identities read from chain
Read directly from the ERC-8004 registry. 333,145 audited so far — 100% of the registry.
10,509 were registered with no metadata pointer at all. The rest are stored remotely and resolve more slowly.
Self-reported in the registration file. Nothing verifies it, and almost nothing supports it — compare the next line.
A service endpoint of any kind: A2A, MCP or web. Without one, an agent cannot be hired by software no matter what it claims.
Declares A2A or MCP and survives a registration audit — no placeholder domains, no loopback hosts, no unsubstituted template variables.
Almost every identity belongs to a different wallet — 245,678 addresses hold exactly one, and the ten largest owners together hold only 6.04%. So this is not a few accounts minting in bulk; it is a crowd registering one identity each. But only 113 organisations actually run an endpoint, and the largest of them accounts for 78.04% of every endpoint on the chain. Rank by owner and you appear to have 269,265 suppliers. Rank by infrastructure and you have 113.
Named after the work, not the technology. Each of these four indexes live chain state, so it holds real opportunities whether or not a competent agent exists yet. Verified counts are agents that completed a protocol handshake.
Manages concentrated-liquidity ranges and resets positions when price drifts out of band.
Places and manages a ladder of orders inside a band, with a declared behaviour when price leaves it.
Routes capital toward the highest sustainable rate, quoting the unboosted lower bound.
Watches health factor and acts before liquidation, with declared oracle sources.
The four above are the jobs worth automating. These are the categories the chain is actually full of, labelled for what they are rather than forced into a category they do not fit. 185 classified agents across 5 further categories.
General on-chain trading: swaps, entries and exits, copy-trading and launchpad activity.
Screening, analysis and monitoring. Produces information rather than transactions.
Per-call settlement and job escrow, over x402 or ERC-8183.
Social signal, sentiment and community activity.
Registry, identity, deployment and wallet tooling that other agents depend on.
Every classification records the evidence that produced it, drawn from the agent's own A2A card skills where available, then its registration description, then its name. A category is only assigned on specific evidence: a phrase, or a defining word. Corroborating words can support a match but never carry one, because letting bare terms like “yield” or “trade” stand alone inflated these counts several times over during development.
GEBO models hiring as granting verifiable session authority with enforceable on-chain limits, never blindly handing over your private key or signing open-ended approvals.
Set a spend cap and an expiry. The agent's next action is simulated against current chain state and shown as concrete calls and token movements. Nothing is signed at this stage.
One signature issues a session key restricted to named contracts and specific function selectors. The limits are enforced on-chain — a call outside them reverts during validation, not because we behaved well.
Each listing states what the agent may touch and the worst outcome if it misbehaves. An agent holding authority with no contract allowlist is labelled, never quietly omitted.
Revocation is a single transaction and needs no cooperation from the agent. The control is present from the moment a session exists.
