Loading
Identity & trust
Read 25 minutes agoWho claims to be an agent, who vouched for them, and how much of either turns into anything measurable. A registration is a claim, not activity.Note 23
ERC-8004 identity registry · the 188,269 registrations whose metadata document is held INLINE on chain · pointer cards are not followed
Finding
179,791
registrations whose card we can read
95%
say they are active
6,065
declare a service endpoint
1,275
declare being in another registry
21,689
claim x402 settlement
8,237
inline documents that are not readable JSON
An agent card is the one place a registration says anything about itself. Most of what it says cannot be checked from the registry, but WHETHER it says anything can, and mostly it does not.
How this is counted
Declared against observed. 1,275 registrations name another registry they are in. We observe 20,269 held by an address that also holds identities on another chain, and 133,779 describing themselves with a document used on another network. Agents are far more cross-chain than they say they are, which is what makes the declared field close to useless for finding them and the observed link worth computing.
Only inline cards are read. 261,800 registrations point at a document somewhere else and we do not follow the pointer: a count that depends on somebody else’s server answering is a count that changes when their server is down, and we would have no way to tell that apart from an agent changing its mind.
How many parties are behind those endpoints
A host with hundreds of registrations invites the question a count of hosts cannot answer: hundreds of agents that happen to use the same provider, or one deployment wearing hundreds of identities? The registry cannot tell them apart. The addresses holding the tokens can.
| Host | Registrations | Held by | Each holding | Reads as |
|---|---|---|---|---|
| github.com | 919 | 579 | 1.6 | a service several parties chose |
| chainpulse-mcp-production.up.railway.app | 470 | 124 | 3.8 | a service several parties chose |
| ensoul.ac | 379 | 34 | 11.1 | a handful of parties |
| basescan.org | 340 | 4 | 85.0 | a handful of parties |
| helixa.xyz | 315 | 2 | 157.5 | a handful of parties |
| Analyst | 105 | 1 | 105.0 | one party, many identities |
| Analyst | 102 | 87 | 1.2 | a service several parties chose |
| Analyst | 87 | 69 | 1.3 | a service several parties chose |
| Analyst | 83 | 72 | 1.2 | a service several parties chose |
| Analyst | 79 | 62 | 1.3 | a service several parties chose |
| Analyst | 70 | 1 | 70.0 | one party, many identities |
| Analyst | 58 | 57 | 1.0 | a service several parties chose |
| Analyst | 50 | 50 | 1.0 | a service several parties chose |
| Analyst | 49 | 48 | 1.0 | a service several parties chose |
| Analyst | 48 | 1 | 48.0 | one party, many identities |
| Analyst | 48 | 1 | 48.0 | one party, many identities |
| Analyst | 48 | 1 | 48.0 | one party, many identities |
| Analyst | 47 | 1 | 47.0 | one party, many identities |
| Analyst | 43 | 5 | 8.6 | a service several parties chose |
| Analyst | 39 | 37 | 1.1 | a service several parties chose |
2,176 of 2,311 hosts are named by registrations a single address holds, covering 2,965 of 6,602. None of this is an accusation: running many agents from one deployment is a reasonable thing to do, and the point is only that the registry counts them as many and nothing in it says so.
Where the declared endpoints point
The 20 largest of 2,305 distinct hosts, across 6,065 registrations. An endpoint is a claim like any other: we record that it was declared and do not call it.
| Host | Registrations |
|---|---|
| chainpulse-mcp-production.up.railway.app | 940 |
| github.com | 932 |
| ensoul.ac | 758 |
| basescan.org | 340 |
| helixa.xyz | 315 |
| Analyst | 141 |
| Analyst | 105 |
| Analyst | 103 |
| Analyst | 87 |
| Analyst | 86 |
| Analyst | 77 |
| Analyst | 70 |
| Analyst | 66 |
| Analyst | 58 |
| Analyst | 51 |
| Analyst | 49 |
| Analyst | 48 |
| Analyst | 48 |
| Analyst | 48 |
| Analyst | 43 |
Analyst tier
5 of 20 shown in full. 15 more are listed with the hosts themselves withheld. The count is free because the count is the finding; the detail is what Analyst carries.
Which registries they say they are in
15 distinct registries named, by CAIP chain. A registration naming a chain is not evidence it is registered there; it is evidence it says so.
| Named registry | Registrations |
|---|---|
| Baseeip155:8453 | 774 |
| eip155:360 unrecognised | 179 |
| Ethereumeip155:1 | 177 |
| BSCeip155:56 | 37 |
| eip155:196 unrecognised | 13 |
| Arbitrumeip155:42161 | 13 |
| Avalancheeip155:43114 | 13 |
| 8 | |
| Polygoneip155:137 | 7 |
| Abstracteip155:2741 | 5 |
Counted 2026-09-08 03:42 UTC, from 51,689 distinct documents; 188,269 inline registrations share them, so a claim is counted once per document and once per registration behind it, never weighted by how often it is repeated.