← all clusters
one registration document, everyone who points at it

1 agent across 1 wallet

answeredThe document was fetched and read.

the document

record hash
ea6c43f493d6eb2e_70
scheme
http
what it answered
1046 bytes read from http
asked at
2026-11-06 03:38:59Z
size
1,046 bytes
name it gives itself
forge
first registered
block 55,657,222

check it yourself

curl -sS -o /dev/null -w '%{http_code}\n' 'http://claw.tormund.io/.well-known/agent-registration.json?agent=forge'

who registered against it

Every agent here was registered by a different wallet.

Counted at registration time, not from who holds the token now. An agent is an ERC-721 and ownership moves, so a live aggregate would answer "who holds these today" when the claim being made is about who registered them.

showing 0 of 1 wallets

re-derive this

$2 = ea6c43f493d6eb2e_70

SELECT owner, "agentCount", "firstSeenBlock"
FROM "AgentRecordOwner"
WHERE "chainId" = $1 AND record_id = $2
ORDER BY "agentCount" DESC, "firstSeenBlock" ASC
LIMIT $3

who funded these wallets, from Nansen

unknown: No wallet in this cluster has been sampled for its first funder yet.

the agents

1 agents point at this one document.

Brighter means the agent carries at least one feedback. Faint means nothing has ever been said about it.

re-derive this

$2 = ea6c43f493d6eb2e_70

SELECT a.id, a."agentId", a.owner, a."agentWallet", a."registeredAtBlock",
       coalesce(fb.total, 0) AS feedback_count
FROM "Agent" a
LEFT JOIN (SELECT agent_id, count(*) AS total FROM "Feedback" WHERE "chainId" = $1 GROUP BY agent_id) fb
  ON fb.agent_id = a.id
WHERE a."chainId" = $1 AND a."uriHash" = $2
ORDER BY a."agentId" ASC
LIMIT $3 OFFSET $4