Instrument 01 · Registry checklive

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

679 agents|block 94,580,644|run 31220e2b

Findings for

12.8%

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

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

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

105 / 471 documents that passed check 4 (Follows the spec?) (conformant)

23.9%

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

162 / 679 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.

Chain	New	Gone	No longer reachable	Reachable again	Declined †	Errored §
Polygon	7	0	0	0	0	0

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

Registered?

registered · 679

✓: pass; 679; 100.0%

Reachable?

resolvable · 679

✓: pass; 558; 82.2%
✗: fail; 107; 15.8%
!: error; 14; 2.1%

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

Readable?

parseable · 679

✓: pass; 483; 71.1%
–: skipped; 121; 17.8%
✗: fail; 75; 11.0%

Follows the spec?

conformant · 679

✓: pass; 471; 69.4%
–: skipped; 196; 28.9%
✗: fail; 12; 1.8%

Claims its identity?

bound · 679

✓: pass; 363; 53.5%
–: skipped; 208; 30.6%
○: unclaimed; 105; 15.5%
✗: fail; 3; 0.4%

Answers?

live · 679

✓: pass; 411; 60.5%
–: skipped; 208; 30.6%
·: not checked; 46; 6.8%
⌀: unprobeable; 10; 1.5%
✗: fail; 4; 0.6%

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

Has feedback?

attested · 679

✗: fail; 517; 76.1%
✓: pass; 162; 23.9%

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.

Agent	Owner	Checks 1–7
Agent #0	0xcfe0…d2b0
Arron C.#1	0x6446…d161
Agent #2	0x6446…d161

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: 31220e2b-6324-4343-bbfb-4d38e874318c
chain: polygon
pinned block: 94,580,644
agents: 679
started: 2026-09-28T06:15:06.005172Z
finished: 2026-09-28T06:33:24.707201Z
checker: 0.7.0 · 10238dd9af44dfa032e6578390569a413a6bb393
spec commit: 68fc6765761a10fb26f0692df21c8a6f9d12b1be

Reproduce

cargo run -p sweeper -- polygon   # at block 94580644

How each check is measured →