Instrument 01 · Registry checklive

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

98,319 agents|block 52,281,733|run c67de707
38.0%

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

20,129 / 52,997 documents that parsed and reached check 4 (Follows the spec?)

90.1%

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.

47,512 / 52,709 documents that passed check 4 (Follows the spec?) (conformant)

30.4%

have at least one on-chain feedback entry. Agents with feedback are less likely to have a document that resolves than agents with none — 31.3% against 66.5%. A sampled read traces most of Base’s feedback to a handful of client addresses.

29,874 / 98,341 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

base · 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 §
Base12,6735187511,9722,226

† 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 base
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 · 98,341

pass
98,341
100.0%
2

Reachable?

resolvable · 98,341

pass
54,839
55.8%
fail
24,710
25.1%
refused
15,617
15.9%
error
3,175
3.2%

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

3

Readable?

parseable · 98,341

pass
52,997
53.9%
skipped
43,502
44.2%
fail
1,829
1.9%
error
13
0.0%
4

Follows the spec?

conformant · 98,341

pass
52,709
53.6%
skipped
45,344
46.1%
fail
288
0.3%
5

Claims its identity?

bound · 98,341

unclaimed
47,512
48.3%
skipped
45,632
46.4%
pass
4,431
4.5%
fail
766
0.8%
6

Answers?

live · 98,341

skipped
45,632
46.4%
fail
26,517
27.0%
not checked
14,883
15.1%
unprobeable
5,727
5.8%
pass
5,234
5.3%
refused
345
0.4%
error
3
0.0%

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

7

Has feedback?

attested · 98,341

fail
68,467
69.6%
pass
29,874
30.4%

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 base
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
Genesis Agent#00xa1da…bd71
ClawNews#10x89e9…5029
Agent #20x6f0f…c1ac
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
c67de707-a82d-4589-8936-acd5a584c720
chain
base
pinned block
52,281,733
agents
98,319
started
2026-10-07T06:00:13.662398Z
finished
2026-10-07T19:18:37.899751Z
checker
0.7.0 · 10238dd9af44dfa032e6578390569a413a6bb393
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- base   # at block 52281733

How each check is measured →