3 agents across 2 wallets

on chainThe document is written into tokenURI itself. There is no host to ask, so it cannot be deleted later.

the document

uri: data:application/json,%7B%22name%22%3A%22ClawdCash%22%2C%22version%22%3A%221.0%22%7D
record hash: 464109d8923fe2ac_84
scheme: data
what it answered: 36 bytes read from data
asked at: 2026-09-20 11:21:53Z
size: 36 bytes
name it gives itself: ClawdCash
first registered: block 54,736,888

check it yourself

curl -sS -o /dev/null -w '%{http_code}\n' 'data:application/json,%7B%22name%22%3A%22ClawdCash%22%2C%22version%22%3A%221.0%22%7D'

who registered against it

1 of these registrations came from a wallet that registered more than one agent against this same document.

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.

0x8c1e…5Cf52 agents · first at block 55,069,752

0xcaF2…1F111 agent · first at block 54,736,888

re-derive this

$2 = 464109d8923fe2ac_84

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

the agents

3 agents point at this one document.

#33 #117 #130

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

re-derive this

$2 = 464109d8923fe2ac_84

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