← all clusters
2 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
- record hash
- b1d4b90a8b9fcacc_102
- scheme
- data
- what it answered
- 50 bytes read from data
- asked at
- 2026-09-20 11:21:53Z
- size
- 50 bytes
- name it gives itself
- ClawdBot Enterprise Pro
- first registered
- block 53,553,985
check it yourself
curl -sS -o /dev/null -w '%{http_code}\n' 'data:application/json,%7B%22name%22%3A%22ClawdBot%20Enterprise%20Pro%22%2C%22version%22%3A%221.0%22%7D'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.
0xcaF2…1F111 agent · first at block 53,553,985
0x166e…9cdf1 agent · first at block 53,554,690
re-derive this
$2 = b1d4b90a8b9fcacc_102
SELECT owner, "agentCount", "firstSeenBlock" FROM "AgentRecordOwner" WHERE "chainId" = $1 AND record_id = $2 ORDER BY "agentCount" DESC, "firstSeenBlock" ASC LIMIT $3
the agents
2 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 = b1d4b90a8b9fcacc_102
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