Instrument 01 · Registry checklive

What we found when we checked every ERC-8004 agent on OP Mainnet

22,084 agents|block 159,605,023|run fc39344c
0.1%

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

18 / 21,980 documents that parsed and reached check 4 (Follows the spec?)

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

294 / 21,978 documents that passed check 4 (Follows the spec?) (conformant)

1.0%

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 99.7%.

222 / 22,084 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

op · 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 §
OP Mainnet21,512003104

† 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 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 · 22,084

pass
22,084
100.0%
2

Reachable?

resolvable · 22,084

pass
22,015
99.7%
fail
55
0.2%
error
12
0.1%
refused
2
0.0%

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

3

Readable?

parseable · 22,084

pass
21,980
99.5%
skipped
69
0.3%
fail
35
0.2%
4

Follows the spec?

conformant · 22,084

pass
21,978
99.5%
skipped
104
0.5%
fail
2
0.0%
5

Claims its identity?

bound · 22,084

pass
21,684
98.2%
unclaimed
294
1.3%
skipped
106
0.5%
6

Answers?

live · 22,084

not checked
21,029
95.2%
pass
446
2.0%
fail
256
1.2%
refused
245
1.1%
skipped
106
0.5%
unprobeable
2
0.0%

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

7

Has feedback?

attested · 22,084

fail
21,862
99.0%
pass
222
1.0%

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 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.
AgentOwnerChecks 1–7
Arca#00x1be9…5adb
Arron C.#10x6446…d161
ClawNews#20x89e9…5029
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
fc39344c-6235-4446-a53f-804877be46d4
chain
op
pinned block
159,605,023
agents
22,084
started
2026-11-16T06:00:23.722436Z
finished
2026-11-16T07:46:06.379501Z
checker
0.7.0 · 9796f5f3bdd4b8bb6c6ac14a68e5fac0ca13114c
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- op   # at block 159605023

How each check is measured →