AgentCount
Sections

Instrument 01 · Registry checklive

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

545 agents|block 157,488,232|run 29c7e645
Findings for
3.8%

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

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

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

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

5.3%

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

29 / 545 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 Mainnet305520

† 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 · 545

pass
545
100.0%
2

Reachable?

resolvable · 545

pass
508
93.2%
fail
25
4.6%
error
12
2.2%

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

3

Readable?

parseable · 545

pass
474
87.0%
skipped
37
6.8%
fail
34
6.2%
4

Follows the spec?

conformant · 545

pass
472
86.6%
skipped
71
13.0%
fail
2
0.4%
5

Claims its identity?

bound · 545

unclaimed
280
51.4%
pass
192
35.2%
skipped
73
13.4%
6

Answers?

live · 545

fail
256
47.0%
pass
197
36.1%
skipped
73
13.4%
not checked
17
3.1%
unprobeable
2
0.4%

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

7

Has feedback?

attested · 545

fail
516
94.7%
pass
29
5.3%

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.
AgentOwnerChecks 1–7
Arca#00x1be9…5adb
Arron C.#10x6446…d161
ClawNews#20x89e9…5029
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 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
29c7e645-4c09-46da-9b3a-bddfc23ecfd9
chain
op
pinned block
157,488,232
agents
545
started
2026-09-28T06:00:41.756074Z
finished
2026-09-28T06:13:42.318143Z
checker
0.7.0 · 10238dd9af44dfa032e6578390569a413a6bb393
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- op   # at block 157488232

How each check is measured →