What we found when we checked every ERC-8004 agent on gnosis
4,108 agents|block 47,649,007|run 46da6f05|no score, no ranking, no per-agent aggregate
016.4%
of valid registration documents declare no way to reach the agent — no services entry at all, or one with nothing in it.
260 / 4,088 documents that parsed and reached check 4 (Follows the spec?)
026.5%
of conforming documents never say which agent they belong to. The registration entry that would bind a document to its on-chain id is only recommended, so most omit it and check 5 (Claims its identity?) records unclaimed — neither a pass nor a fail.
266 / 4,086 documents that passed check 4 (Follows the spec?) (conformant)
0350.7%
have at least one on-chain feedback entry — and those agents are less likely to have a document that resolves than agents with none: 100.0% against 99.1%.
2,081 / 4,108 agents in this run
041
the number of MUST requirements ERC-8004 places on a registration file — and it is conditional, so a document that omits registrations entirely has nothing it must do at all.
spec 68fc6765761a · checker 0.7.0
Read the full report: 4 chains, 354,858 agents →
Every check, every status
base rates on gnosisPopulation 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
of 4,1082
Reachable? resolvable
of 4,108- ✗fail90.2%
- ✓pass4,08899.5%
- •refused110.3%
3
Readable? parseable
of 4,108- ✓pass4,08899.5%
- –skipped200.5%
4
Follows the spec? conformant
of 4,108- ✗fail20.0%
- ✓pass4,08699.5%
- –skipped200.5%
5
Claims its identity? bound
of 4,108- ✗fail150.4%
- ✓pass3,80592.6%
- –skipped220.5%
- ○unclaimed2666.5%
- ✗fail30.1%
- ✓pass53713.1%
- –skipped220.5%
- ⌀unprobeable30.1%
- ·not checked3,54386.2%
7
Has feedback? attested
of 4,108- ✗fail2,02749.3%
- ✓pass2,08150.7%
Key✗faildid not pass✓passpassed•refused–skippeda check this one depends on did not pass○unclaimedthe document made no claim to check⌀unprobeableno declared endpoint that a probe can reach·not checkedthis check was never askedFull definitions One agent, seven checks
first three on gnosisExactly 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 | Id | Owner | Checks 1–7 |
|---|
| ClawNews | 0 | 0x89e9e1ab11dd1b138b1dce6d6a4a0926aafd5029 | 1✓Check 1Registered?The agent exists in the on-chain registry, with an owner and a document URL.passpassed2✓Check 2Reachable?The document URL it declared actually answers when fetched.passpassed3✓Check 3Readable?What came back is valid JSON that a machine can read.passpassed4✗Check 4Follows the spec?The document meets what ERC-8004 requires of it.faildid not pass5–Check 5Claims its identity?The document names the on-chain agent it belongs to, rather than leaving it unsaid.skippedskipped — a check this one depends on did not pass6–Check 6Answers?A declared endpoint responds to a probe. Not implemented yet, so nobody passes or fails it.skippedskipped — a check this one depends on did not pass7✗Check 7Has feedback?At least one on-chain feedback entry names this agent.faildid not pass |
| tuwim-kakon68 by Olas | 1 | 0x6e8f740f23f07ce129daa59786926feca8c2d2f3 | 1✓Check 1Registered?The agent exists in the on-chain registry, with an owner and a document URL.passpassed2✓Check 2Reachable?The document URL it declared actually answers when fetched.passpassed3✓Check 3Readable?What came back is valid JSON that a machine can read.passpassed4✓Check 4Follows the spec?The document meets what ERC-8004 requires of it.passpassed5✓Check 5Claims its identity?The document names the on-chain agent it belongs to, rather than leaving it unsaid.passpassed6·Check 6Answers?A declared endpoint responds to a probe. Not implemented yet, so nobody passes or fails it.not checkednot checked — this check was never asked7✗Check 7Has feedback?At least one on-chain feedback entry names this agent.faildid not pass |
| kipim-wireti32 by Olas | 2 | 0x6e8f740f23f07ce129daa59786926feca8c2d2f3 | 1✓Check 1Registered?The agent exists in the on-chain registry, with an owner and a document URL.passpassed2✓Check 2Reachable?The document URL it declared actually answers when fetched.passpassed3✓Check 3Readable?What came back is valid JSON that a machine can read.passpassed4✓Check 4Follows the spec?The document meets what ERC-8004 requires of it.passpassed5✓Check 5Claims its identity?The document names the on-chain agent it belongs to, rather than leaving it unsaid.passpassed6·Check 6Answers?A declared endpoint responds to a probe. Not implemented yet, so nobody passes or fails it.not checkednot checked — this check was never asked7✗Check 7Has feedback?At least one on-chain feedback entry names this agent.faildid not pass |
Key✗faildid not pass✓passpassed•refused–skippeda check this one depends on did not pass○unclaimedthe document made no claim to check⌀unprobeableno declared endpoint that a probe can reach·not checkedthis check was never askedFull definitions Search all 354,858 agents →Agents that passed every check →
Provenance
reproducibleEvery 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
- 46da6f05-702a-463e-bd61-775b54353e89
- chain
- gnosis
- pinned block
- 47,649,007
- agents
- 4,108
- started
- 2026-08-10T06:12:11.284795Z
- finished
- 2026-08-10T06:37:47.921292Z
- checker
- 0.7.0 · 55deaa9ce71c025a9199311a53cdc2de236eae53
- spec commit
- 68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproducecargo run -p sweeper -- gnosis # at block 47649007
How each check is measured →
Get each census report by email
One message per report. No other mail, ever — not announcements, not anything else this project might do later. Unsubscribe from any of them.
Your address is stored by AgentCount and used for nothing but the census reports. Nothing is sent yet — there is no sending side built, so there is no confirmation email to expect, and you will be asked to confirm before the first report goes anywhere. Email probes@agentcount.ai at any point and it is deleted.