AgentCount
Sections
Check your agent

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

10,723 agents|block 67,576,783|run ab6e134c|no score, no ranking, no per-agent aggregate
Findings for
48.8%

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

5,067 / 10,390 documents that parsed and reached check 4 (Follows the spec?)

99.8%

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.

10,355 / 10,376 documents that passed check 4 (Follows the spec?) (conformant)

10.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: 99.7% against 96.6%.

1,149 / 10,723 agents in this run

1

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 xlayer
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

of 10,723
  • pass10,723100.0%
2

Reachable? resolvable

of 10,723
  • error30.0%
  • fail3293.1%
  • pass10,39096.9%
  • refused10.0%
3

Readable? parseable

of 10,723
  • pass10,39096.9%
  • skipped3333.1%
4

Follows the spec? conformant

of 10,723
  • fail140.1%
  • pass10,37696.8%
  • skipped3333.1%
5

Claims its identity? bound

of 10,723
  • fail10.0%
  • pass200.2%
  • skipped3473.2%
  • unclaimed10,35596.6%
6

Answers? live

of 10,723
  • error100.1%
  • fail9859.2%
  • pass1,33912.5%
  • refused2102.0%
  • skipped3473.2%
  • unprobeable2,86726.7%
  • not checked4,96546.3%
7

Has feedback? attested

of 10,723
  • fail9,57489.3%
  • pass1,14910.7%
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 xlayer
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 #000x6ba100a250955209b3cad5f06e31895f678425c1
OKX Agent10x6ba100a250955209b3cad5f06e31895f678425c1
Payment Agent20x68047f077ca2c71d6a6c03afaf87e438e07bdf84
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 354,858 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
ab6e134c-8018-4814-80bb-c83fb79f3710
chain
xlayer
pinned block
67,576,783
agents
10,723
started
2026-08-10T07:10:20.176367Z
finished
2026-08-10T08:11:41.005767Z
checker
0.7.0 · 55deaa9ce71c025a9199311a53cdc2de236eae53
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- xlayer   # at block 67576783

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.