Sections

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

1,234 agents|block 492,986,716|run 53fbdb9f
Findings for
3.6%

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

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

97.4%

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,088 / 1,117 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 98.8% against 96.1%.

81 / 1,234 agents in this run

not yet measured

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 →

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,234

pass
1,234
100.0%
2

Reachable?

resolvable · 1,234

pass
1,188
96.3%
fail
31
2.5%
error
13
1.1%
refused
2
0.2%

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

3

Readable?

parseable · 1,234

pass
1,132
91.7%
fail
56
4.5%
skipped
46
3.7%
4

Follows the spec?

conformant · 1,234

pass
1,117
90.5%
skipped
102
8.3%
fail
15
1.2%
5

Claims its identity?

bound · 1,234

unclaimed
1,088
88.2%
skipped
117
9.5%
pass
26
2.1%
fail
3
0.2%
6

Answers?

live · 1,234

pass
739
59.9%
fail
277
22.4%
skipped
117
9.5%
unprobeable
72
5.8%
not checked
29
2.4%

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

7

Has feedback?

attested · 1,234

fail
1,153
93.4%
pass
81
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.
AgentIdOwnerChecks 1–7
ClawNews00x89e9e1ab11dd1b138b1dce6d6a4a0926aafd5029
ClawSearch10x89e9e1ab11dd1b138b1dce6d6a4a0926aafd5029
melyar-konje08 by Olas20x22be6fdcd3e29851b29b512f714c328a00a96b83
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 369,665 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
53fbdb9f-7e31-456a-b7a4-4d7cb3e97eed
chain
arbitrum
pinned block
492,986,716
agents
1,234
started
2026-08-10T06:06:43.263270Z
finished
2026-08-10T06:11:28.514872Z
checker
0.7.0 · 55deaa9ce71c025a9199311a53cdc2de236eae53
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- arbitrum   # at block 492986716

How each check is measured →