Instrument 01 · Registry checklive

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

708 agents|block 97,406,646|run c91d0468
12.9%

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

65 / 505 documents that parsed and reached check 4 (Follows the spec?)

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

95 / 491 documents that passed check 4 (Follows the spec?) (conformant)

24.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 — 76.3% against 83.9%.

173 / 708 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

polygon · 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 §
Polygon600009

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

pass
708
100.0%
2

Reachable?

resolvable · 708

pass
581
82.1%
fail
112
15.8%
error
14
2.0%
refused
1
0.1%

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

3

Readable?

parseable · 708

pass
505
71.3%
skipped
127
17.9%
fail
76
10.7%
4

Follows the spec?

conformant · 708

pass
491
69.4%
skipped
203
28.7%
fail
14
2.0%
5

Claims its identity?

bound · 708

pass
393
55.5%
skipped
217
30.6%
unclaimed
95
13.4%
fail
3
0.4%
6

Answers?

live · 708

pass
430
60.7%
skipped
217
30.6%
not checked
46
6.5%
unprobeable
11
1.6%
fail
4
0.6%

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

7

Has feedback?

attested · 708

fail
535
75.6%
pass
173
24.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 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.
AgentOwnerChecks 1–7
Agent #00xcfe0…d2b0
Arron C.#10x6446…d161
Agent #20x6446…d161
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
c91d0468-7c8d-40b5-8104-b4ec7eab0843
chain
polygon
pinned block
97,406,646
agents
708
started
2026-11-16T07:50:37.833996Z
finished
2026-11-16T08:13:22.036877Z
checker
0.7.0 · 9796f5f3bdd4b8bb6c6ac14a68e5fac0ca13114c
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- polygon   # at block 97406646

How each check is measured →