1 agent across 1 wallet

answeredThe document was fetched and read.

the document

uri: https://claw.tormund.io/.well-known/agent-registration.json?agent=clawbun
record hash: 21ce3ca86d960fbc_73
scheme: http
what it answered: 1202 bytes read from http
asked at: 2026-09-20 11:22:00Z
size: 1,202 bytes
name it gives itself: clawbun
first registered: block 53,771,436

check it yourself

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

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.

0xb1Df…9B051 agent · first at block 53,771,436

re-derive this

$2 = 21ce3ca86d960fbc_73

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

the agents

1 agents point at this one document.

#12

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

re-derive this

$2 = 21ce3ca86d960fbc_73

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