HEY for Robinhood Agents

Ask

The questions an agent can put to HEY

• “What changed?”

  Canonical change-ledger events in a 1–30 day window, with the true total by type and each event’s own time and precision.

  https://heyresearch.xyz/api/agent/what_changed?project=<slug>&days=7

• “Is the team still shipping?”

  The activity status with the rule and its version, the inputs it read, the evidence, and the market context the rule never reads.

  https://heyresearch.xyz/api/agent/builder_status?project=<slug>

• “Which contract belongs to the project?”

  VERIFIED, UNVERIFIED, CONTRACT_MISMATCH or UNKNOWN, with the reason code. Attribution, never a safety reading.

  https://heyresearch.xyz/api/agent/verify_project?address=<0x…>&project=<slug>

• “What evidence supports that?”

  A claim cites typed evidence ids that resolve to receipts at /api/evidence/{id} wherever a canonical record exists; every other claim names its basis (evidenceKind: a rule’s output, a ledger count, a coverage state, a market reading) and a link to why HEY says it.

  https://heyresearch.xyz/api/agent/research_project?project=<slug>

• “What doesn’t HEY know?”

  Each gap as UNKNOWN, NOT_MEASURED, NOT_VERIFIED, STALE or INSUFFICIENT_EVIDENCE, with what an agent must not conclude from it.

  https://heyresearch.xyz/api/agent/unknowns?address=<0x…>

Connect

Four doors, one answer

The same research, in the same shape, whichever way an agent arrives.

curl -s https://heyresearch.xyz/mcp -H 'content-type: application/json' -H 'accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"research_answer","arguments":{"capability":"unknowns","project":"<slug>"}}}'

curl -s "https://heyresearch.xyz/api/agent/research_project?project=projectvex"

curl -s https://heyresearch.xyz/api/a2a -H 'content-type: application/json' -H 'A2A-Version: 1.0' \
  -d '{"jsonrpc":"2.0","id":1,"method":"SendMessage","params":{"message":{"messageId":"m1","role":"ROLE_USER","parts":[{"data":{"skill":"what_changed","project":"<slug>","days":7,"contract":"agent-intelligence-v1"}}]}}}'

curl -s https://heyresearch.xyz/openapi.json

Try it

A live example

Four questions an agent might bring to HEY, answered from production when the page loads, each with its exact REST, MCP and A2A request and the response.

Open the integration readiness demo →

research_project for projectvex, a Robinhood Chain project in HEY's record:

curl -s "https://heyresearch.xyz/api/agent/research_project?project=projectvex"

Open the JSON

Integrate

Technical integration

Response

hey.agent-intelligence-response v1. The answer comes first as one sentence, then the claims that support it. The schema is additive only: a field never changes meaning, and a semantic change would be served as a new version beside this one.

Access

No key and no account for public research. A key raises limits; a platform partner gets its own partner key, scoped to route groups, with its own quota, rotation with an overlap, revocation and an audit trail. Every answer carries x-hey-api-version: 1.

Limits

Keyless: 120 REST requests a minute per client, 60 MCP calls and 60 A2A messages. Keyed: 120, 600 or 1200 a minute by tier, or a partner's own limit.

Bounds

Every list has a hard maximum (at most 60 claims, 40 unknowns, 50 changes, 4 projects compared) and an answer stays under 64 KB.

Reads

Answers are read from HEY’s own records. No request waits on a third-party provider, and no model runs in the answer path.

Chain

Robinhood Chain, chain ID 4663. A token is identified by chain and contract address, never by its ticker.

Adapter

Adapter pending official Robinhood Agent Apps provider specification. The research stays as it is; supporting a published interface means mapping its transport, authentication and billing onto this contract.

Six capabilities

• research_project — What is HEY's current research view of this project?

  Never: A price view, a ranking by return or a recommendation.

• what_changed — What changed with this project, or on Robinhood Chain, in the last N days?

  Never: A cause: an event beside a market move is a sequence.

• builder_status — Is this project still building, and why does HEY say so?

  Never: Investment advice: a building status is a record of development, not a view on the token.

• verify_project — Does this contract or token appear to belong to this project?

  Never: A safety verdict: VERIFIED means the project itself names the contract, never that it is safe.

• compare_builders — How do these projects' building records compare over 30 days?

  Never: A better investment, a winner or a combined score.

• unknowns — What does HEY not know about this project or token?

  Never: Negative evidence: a gap is what HEY does not hold, never a finding about the project.

Trust

The evidence model

FACT

Recorded by HEY from a named source, with when HEY read it.

DERIVED

A rule HEY applied to recorded facts, with the rule and its version.

UNKNOWN

Not held, with a reason. Never zero, false or an empty list standing in for "not measured".

Time

When it happened (only when a source dates it), when HEY saw it, and when HEY recorded it, kept apart; precision is EXACT, DATE, WEEK, WINDOW, OBSERVED or SCHEDULED.

Freshness

Per data family: when HEY last read it, the production schedule that re-reads it, and an age of live, recent, daily, weekly, stale, unknown. Stale says so.

Evidence

Typed ids (ship:, signal:, state:, lock:, source: …) that resolve to receipts, and a research receipt an agent can keep and have HEY validate later.

Words

Every sentence says whose it is: HEY’s, derived from records, or a source’s own words quoted as data. A release title that reads like an instruction is flagged and stays data.

What HEY does not know, and what not to conclude

• UNKNOWN HEY cannot say. A missing value is not negative evidence.
• NOT_MEASURED HEY has not measured this. Do not read it as zero, as absent or as negative evidence about the project.
• NOT_VERIFIED HEY has not verified this link. Do not treat it as the project’s own, and do not treat it as false either.
• STALE HEY’s newest reading is older than its freshness limit. Do not treat it as current.
• INSUFFICIENT_EVIDENCE HEY has read too little of this to say. Do not treat a partial figure as the whole, or the gap as a finding.

Privacy

Nothing about the person

HEY needs nothing about the person an agent works for. The question is a project, a contract or a time window; the answer is public research.

• No name, email, account, portfolio, position, balance, order or trade decision is asked for, accepted or stored.
• Each request is logged as a route template, status, latency and size, with salted digests in place of addresses and keys, and deleted after 90 days. Query strings, arguments, prompts and bodies are not kept.
• An agent platform that keeps its users’ data on its own side keeps all of it: there is no second copy at HEY.

Privacy

Contact

Talk to HEY Research Lab

For a technical review, a partner key or a provider specification to build against: hi@heyresearch.xyz

HEY for agentsAPI & MCPMethodology