Instrument 01 · Registry checklive

What we found when we checked every ERC-8004 agent on BNB Chain

364,697 agents|block 126,008,346|run 39c9b855
48.9%

of valid registration documents declare no way to reach the agent — no services entry at all, or one with nothing in it.

165,838 / 339,143 documents that parsed and reached check 4 (Follows the spec?)

62.7%

of registration files never say which on-chain agent they belong to — the spec only recommends the field that would bind them. Check 5 (Claims its identity?) records those as unclaimed: neither a pass nor a fail.

212,175 / 338,576 documents that passed check 4 (Follows the spec?) (conformant)

1.2%

have at least one on-chain feedback entry. Agents with feedback are less likely to have a document that resolves than agents with none — 83.2% against 95.1%.

4,458 / 364,697 agents in this run

—

Whether money reaches a registered agent is read from token transfer logs rather than from the registry, so it is not one of the seven checks and no sweep reports it. What the join asks, and what it is read against.

369,130 agents · outside the seven checks

Read the full report: 4 chains, 369,130 agents →

Changed since the last sweep

bsc · against its previous sweep
Each row compares a chain’s current sweep against the previous one — both pinned to a block, so the comparison itself recomputes. “No longer reachable” is check 2 (Reachable?) moving from pass to not-pass: the quiet decay that registration counts never show.
ChainNewGoneNo longer reachableReachable againDeclined †Errored §
BNB Chain14,33214121469503

† Check 2 (Reachable?) transitions where the origin declined the probe — a rate limit, an auth or payment challenge, a robots.txt that said no. Excluded from both reachability columns by rule: being declined is not the agent having gone away, and getting through after being declined is not the agent having come back.

§ Check 2 transitions where this census’s own probe failed — a timeout, a TLS or DNS failure. Excluded from both reachability columns by the same rule: our failure is never the agent’s, and a checker-side outage must not read as agents going dark.

Every check, every status

base rates on bsc
Population counts, not a score for any one agent. A check’s segments do not sum to the whole population when an earlier failure stopped the pipeline — that gap is drawn as its own “not checked” segment rather than folded into whichever status happens to render widest.
1

Registered?

registered · 364,697

pass
364,697
100.0%
2

Reachable?

resolvable · 364,697

pass
346,355
95.0%
fail
16,442
4.5%
refused
1,319
0.4%
error
581
0.2%

Counts documents stored on-chain, which resolve by construction — this is not a server-uptime rate.

3

Readable?

parseable · 364,697

pass
339,143
93.0%
skipped
18,342
5.0%
fail
7,212
2.0%
4

Follows the spec?

conformant · 364,697

pass
338,576
92.8%
skipped
25,554
7.0%
fail
567
0.2%
5

Claims its identity?

bound · 364,697

unclaimed
212,175
58.2%
pass
125,456
34.4%
skipped
26,121
7.2%
fail
945
0.3%
6

Answers?

live · 364,697

not checked
290,122
79.6%
fail
39,166
10.7%
skipped
26,121
7.2%
pass
7,792
2.1%
unprobeable
1,458
0.4%
refused
34
0.0%
error
4
0.0%

Something answered — not that it works, speaks any protocol, or is the agent.

7

Has feedback?

attested · 364,697

fail
360,239
98.8%
pass
4,458
1.2%

Someone left feedback — not that they were independent of the agent.

Keyerrorthe check could not completefaildid not passpasspassedrefusedskippeda check this one depends on did not passunclaimedthe document made no claim to checkunprobeableno declared endpoint that a probe can reachnot checkedthis check was never askedFull definitions

One agent, seven checks

first three on bsc
Exactly as the directory renders them. Hover or tap any badge for the question it answers. A check with no row was never reached this run — check 6 (Answers?) is not yet implemented, so it reads as not checked for everyone, never as a failure.
AgentOwnerChecks 1–7
dAi#00x8ce2…fdec
ClawNews#10x89e9…5029
Agent #20x6446…d161
Keyerrorthe check could not completefaildid not passpasspassedrefusedskippeda check this one depends on did not passunclaimedthe document made no claim to checkunprobeableno declared endpoint that a probe can reachnot checkedthis check was never askedFull definitions

Search all 485,257 agents →Agents that passed every check →

Provenance

reproducible
Every number on this page comes from one sweep, pinned to one block. A result you cannot recompute is an opinion; this is what recomputes it.
run
39c9b855-a05a-47f7-9857-ac11076a502b
chain
bsc
pinned block
126,008,346
agents
364,697
started
2026-10-06T06:00:16.906244Z
finished
2026-10-06T21:58:01.042309Z
checker
0.7.0 · 10238dd9af44dfa032e6578390569a413a6bb393
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- bsc   # at block 126008346

How each check is measured →