Sections

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

25,974 agents|block 6,713,092|run eb6676e0
Findings for
99.7%

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

25,899 / 25,974 documents that parsed and reached check 4 (Follows the spec?)

100.0%

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.

25,965 / 25,969 documents that passed check 4 (Follows the spec?) (conformant)

0.6%

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

163 / 25,974 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 billions
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 · 25,974

pass
25,974
100.0%
2

Reachable?

resolvable · 25,974

pass
25,974
100.0%

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

3

Readable?

parseable · 25,974

pass
25,974
100.0%
4

Follows the spec?

conformant · 25,974

pass
25,969
100.0%
fail
5
0.0%
5

Claims its identity?

bound · 25,974

unclaimed
25,965
100.0%
skipped
5
0.0%
pass
3
0.0%
fail
1
0.0%
6

Answers?

live · 25,974

not checked
25,862
99.6%
pass
52
0.2%
unprobeable
44
0.2%
fail
11
0.0%
skipped
5
0.0%

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

7

Has feedback?

attested · 25,974

fail
25,811
99.4%
pass
163
0.6%

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

Keyfaildid 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 billions
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
V00xa8cb59b9f8c4281abe4791fdb85443877031bf71
V10xdd4dbce6c52813c1f0f3fc7d9e875a3b02b4baed
V20x470a3f921a8a0328073b7e23cc7c9f4cec6249e7
Keyfaildid 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
eb6676e0-56ea-4a30-b00a-2764edceee12
chain
billions
pinned block
6,713,092
agents
25,974
started
2026-08-10T09:15:07.879147Z
finished
2026-08-10T10:06:01.232660Z
checker
0.7.0 · 55deaa9ce71c025a9199311a53cdc2de236eae53
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- billions   # at block 6713092

How each check is measured →