AgentCount
Sections

Instrument 01 · Registry checklive

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

85,673 agents|block 51,072,140|run 794d7afd
Findings for
35.4%

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

18,433 / 52,037 documents that parsed and reached check 4 (Follows the spec?)

87.5%

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.

45,207 / 51,664 documents that passed check 4 (Follows the spec?) (conformant)

34.8%

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

29,782 / 85,673 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 §
Base1,5810281041,6333,631

† 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 · 85,673

pass
85,673
100.0%
2

Reachable?

resolvable · 85,673

pass
53,829
62.8%
fail
24,397
28.5%
error
3,752
4.4%
refused
3,695
4.3%

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

3

Readable?

parseable · 85,673

pass
52,037
60.7%
skipped
31,844
37.2%
fail
1,779
2.1%
error
13
0.0%
4

Follows the spec?

conformant · 85,673

pass
51,664
60.3%
skipped
33,636
39.3%
fail
373
0.4%
5

Claims its identity?

bound · 85,673

unclaimed
45,207
52.8%
skipped
34,009
39.7%
pass
5,626
6.6%
fail
831
1.0%
6

Answers?

live · 85,673

skipped
34,009
39.7%
fail
24,233
28.3%
not checked
13,799
16.1%
unprobeable
6,983
8.2%
pass
6,247
7.3%
refused
395
0.5%
error
7
0.0%

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

7

Has feedback?

attested · 85,673

fail
55,891
65.2%
pass
29,782
34.8%

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
794d7afd-90ab-4c17-90c9-57f8b48e7a3d
chain
base
pinned block
51,072,140
agents
85,673
started
2026-09-09T06:00:28.568294Z
finished
2026-09-16T08:47:01.599361Z
checker
0.7.0 · 981910a8f7451ff11d8af05abef0cc7852e25953
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- base   # at block 51072140

How each check is measured →