Instrument 01 · Registry checklive

What we found when we checked every ERC-8004 agent on Arbitrum

1,650 agents|block 522,597,310|run 0aa09de2
3.1%

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

44 / 1,437 documents that parsed and reached check 4 (Follows the spec?)

97.3%

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.

1,383 / 1,421 documents that passed check 4 (Follows the spec?) (conformant)

6.6%

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

109 / 1,650 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

arbitrum · 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 §
Arbitrum1819010469

† 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 arbitrum
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 · 1,650

pass
1,650
100.0%
2

Reachable?

resolvable · 1,650

pass
1,580
95.8%
error
32
1.9%
fail
32
1.9%
refused
6
0.4%

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

3

Readable?

parseable · 1,650

pass
1,437
87.1%
fail
143
8.7%
skipped
70
4.2%
4

Follows the spec?

conformant · 1,650

pass
1,421
86.1%
skipped
213
12.9%
fail
16
1.0%
5

Claims its identity?

bound · 1,650

unclaimed
1,383
83.8%
skipped
229
13.9%
pass
35
2.1%
fail
3
0.2%
6

Answers?

live · 1,650

pass
1,041
63.1%
fail
277
16.8%
skipped
229
13.9%
unprobeable
73
4.4%
not checked
30
1.8%

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

7

Has feedback?

attested · 1,650

fail
1,541
93.4%
pass
109
6.6%

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 arbitrum
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
ClawNews#00x89e9…5029
ClawSearch#10x89e9…5029
melyar-konje08#20x22be…6b83
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
0aa09de2-77da-4771-b18d-b8c91ded4552
chain
arbitrum
pinned block
522,597,310
agents
1,650
started
2026-11-09T06:43:55.108660Z
finished
2026-11-10T00:20:25.654366Z
checker
0.7.0 · 9796f5f3bdd4b8bb6c6ac14a68e5fac0ca13114c
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- arbitrum   # at block 522597310

How each check is measured →