ERC-8004 agents on Celo

Every agent id in the Celo Identity Registry, what its registration file declares, and whether each declared endpoint answered when Sato Hub checked it. Checked daily. Readings of Sato Hub's probes — whether declared endpoints answered. Not a judgement of safety or quality.

Method

Each day Sato Hub reads every agent id from the Identity Registry on Celo (0x8004A169FB4a3325136EB29fA0ceB6D2e539a432): its owner and agentURI. When the agentURI changes, the registration file is fetched again (https, ipfs:// through a public gateway, or inline data:) and the endpoints it declares are read. Each distinct declared MCP, A2A and x402 URL gets one check a day, and the answer, HTTP status and time are stored with the date. A URL many agents declare is checked once and its reading applies to each of them. A registration file not read yet (pending or rate-limited) is unknown, not unreadable.

Caveat

Declaring an endpoint is not running one, and a failed check may be the host, the network or us. “Not checked yet” is unknown, never a failure. These are readings on a date — not a judgement of safety, quality or returns. Figures are for Celo only and are never added to other chains.

Onchain

Where Sato Hub posts a reading to the ERC-8004 Reputation Registry (0x8004BAa17C55a88189AE136b182e5fdA19dE9b63), the agent’s report links the transaction and the evidence document; keccak256 of that document equals the hash on chain.

Dataset

JSON · CSV — every agent id on Celo, one row each. Check one agent before connecting to it: /api/preflight?agent=celo:8004:<id>.