Sections

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

608 agents|block 91,757,844|run b8acef9f
Findings for
14.0%

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

62 / 444 documents that parsed and reached check 4 (Follows the spec?)

24.6%

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.

106 / 431 documents that passed check 4 (Follows the spec?) (conformant)

25.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 76.0% against 83.9%.

154 / 608 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 polygon
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 · 608

pass
608
100.0%
2

Reachable?

resolvable · 608

pass
498
81.9%
fail
107
17.6%
error
3
0.5%

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

3

Readable?

parseable · 608

pass
444
73.0%
skipped
110
18.1%
fail
54
8.9%
4

Follows the spec?

conformant · 608

pass
431
70.9%
skipped
164
27.0%
fail
13
2.1%
5

Claims its identity?

bound · 608

pass
322
53.0%
skipped
177
29.1%
unclaimed
106
17.4%
fail
3
0.5%
6

Answers?

live · 608

pass
371
61.0%
skipped
177
29.1%
not checked
45
7.4%
unprobeable
11
1.8%
fail
4
0.7%

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

7

Has feedback?

attested · 608

fail
454
74.7%
pass
154
25.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 polygon
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
Agent #000xcfe0c58d59cbe21598002a09be904a215392d2b0
Arron C.10x6446ad9821021eeb9f85b8a18b0153d58166d161
Agent #220x6446ad9821021eeb9f85b8a18b0153d58166d161
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 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
b8acef9f-d219-4fc8-8aaa-b7ce20d1b168
chain
polygon
pinned block
91,757,844
agents
608
started
2026-08-10T06:03:12.744539Z
finished
2026-08-10T06:04:58.131352Z
checker
0.7.0 · 55deaa9ce71c025a9199311a53cdc2de236eae53
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- polygon   # at block 91757844

How each check is measured →