Sections

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

535 agents|block 155,291,584|run 9a6bee56
Findings for
3.7%

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

18 / 487 documents that parsed and reached check 4 (Follows the spec?)

57.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.

280 / 485 documents that passed check 4 (Follows the spec?) (conformant)

2.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 91.7% against 96.6%.

12 / 535 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 op
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 · 535

pass
535
100.0%
2

Reachable?

resolvable · 535

pass
516
96.4%
fail
17
3.2%
error
2
0.4%

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

3

Readable?

parseable · 535

pass
487
91.0%
fail
29
5.4%
skipped
19
3.6%
4

Follows the spec?

conformant · 535

pass
485
90.7%
skipped
48
9.0%
fail
2
0.4%
5

Claims its identity?

bound · 535

unclaimed
280
52.3%
pass
205
38.3%
skipped
50
9.3%
6

Answers?

live · 535

fail
256
47.9%
pass
210
39.3%
skipped
50
9.3%
not checked
17
3.2%
unprobeable
2
0.4%

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

7

Has feedback?

attested · 535

fail
523
97.8%
pass
12
2.2%

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

Keyerrorthe check could not completefaildid not passpasspassedskippeda 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 op
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
Arca00x1be93c700ddc596d701e8f2106b8f9166c625adb
Arron C.10x6446ad9821021eeb9f85b8a18b0153d58166d161
ClawNews20x89e9e1ab11dd1b138b1dce6d6a4a0926aafd5029
Keyerrorthe check could not completefaildid not passpasspassedskippeda 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
9a6bee56-1594-4980-bafd-5efe49aae6ce
chain
op
pinned block
155,291,584
agents
535
started
2026-08-08T09:39:06.440025Z
finished
2026-08-08T09:40:35.797124Z
checker
0.7.0 · 55deaa9ce71c025a9199311a53cdc2de236eae53
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- op   # at block 155291584

How each check is measured →