How agents use HEY

Distinct external agent clients — by the name they declare (MCP clientInfo, or x-hey-integration on A2A and the REST agent contract) — that made at least one research call in the window: an MCP tool, resource or prompt, an A2A skill or an agent-contract capability. initialize, tools/list and other protocol calls are not research. Registries, probes, health checks, tool sweeps, HEY’s own, test and placeholder clients (the example names HEY’s guides print, `my-agent`) are excluded.

Agent clients active that made research calls on at least two distinct UTC days in the window. An unnamed caller is never a repeat client: its digest is salted per day by design.

Session-days (one day-salted caller digest on one UTC day) with a research call from callers that declared no client name. Counted, never as a client and never as a repeat: the digest is salted per day by design, so one caller on two days is two.

Tool, resource and prompt calls on the hosted MCP endpoints (/mcp, /mcp/research) that were answered, by UTC day and tool. Handshakes (initialize, tools/list, ping), refused calls, registries, probes, health checks, tool sweeps (a client calling eight or more tools at most twice each on a day), HEY’s own clients and test or placeholder names are excluded. A day with no call is absent, not zero.

Requests and research calls per protocol — hosted MCP, the MCP research profile, the npm MCP package (stdio), A2A (/api/a2a) and the REST agent contract (/api/agent/…) — HEY’s own and staff traffic excluded. researchRecordedFrom is the first day that protocol’s rows said which research call they were; a window starting earlier under-counts research before it.

Requests whose user agent names the HEY SDK first, HEY’s own excluded: served (2xx/3xx), refused (4xx) and rate-limited (429) among them, and distinct (UTC day, address digest) pairs — address-days, never people.

Reads of the machine entry points — llms.txt, the A2A Agent Card, OpenAPI, the $HEY profile, the agent guide as Markdown, the receipt schema and validator — crawlers included, HEY’s own excluded. visitorDays are distinct day-salted digests over the window: one caller on two days counts twice.

Requests on the machine entry points (llms.txt, the Agent Card, OpenAPI, /mcp, /api/a2a, /api/agent, …) from the edge log, by the crawler or assistant family the user agent declares (openai, anthropic, perplexity, google, bing). From 2026-09-25 a request the edge cache answered never reaches the origin log, so these are a floor. hoursCovered is how many hours of the window the log holds; null when it holds none.

HEY’s own registration in the ERC-8004 Identity Registry on Robinhood Chain: the agent id, the registry, and the transaction that registered it. Discovery only — HEY claims no reputation or validation through it.

Registrations in the canonical ERC-8004 Identity Registry on Robinhood Chain (chain 4663, contract 0x8004A169FB4a3325136EB29fA0ceB6D2e539a432): one per Registered(uint256 agentId, string agentURI, address owner) event the registry emitted, by the UTC day of its block, read from the chain once a day from block 0 (basis reconstructed_from_chain). total is every registration up to the last block HEY read; last7Days and last30Days are the seven and thirty UTC days ending on the day HEY read through, that day as far as read. Counts only: no owner, agent id or agent URI is stored or shown, and a registration is not a person, a user or an endorsement — HEY’s own is one of them. Null, with its reason, until HEY has read the registry; never 0.