1 agent across 1 wallet

answeredThe document was fetched and read.

the document

uri: https://grokandmon.com/.well-known/agent-registration.json
record hash: 3e16bbc8e1874674_58
scheme: http
what it answered: 4398 bytes read from http
asked at: 2026-09-20 11:22:00Z
size: 4,398 bytes
name it gives itself: GanjaMon
first registered: block 53,275,238

check it yourself

curl -sS -o /dev/null -w '%{http_code}\n' 'https://grokandmon.com/.well-known/agent-registration.json'

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.

0x734B…F1341 agent · first at block 53,275,238

re-derive this

$2 = 3e16bbc8e1874674_58

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.

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

re-derive this

$2 = 3e16bbc8e1874674_58

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