canonical: https://jentic.com/apis/heyresearch.xyz/heyresearch # Heyresearch Xyz HEY Research Lab public API The HEY Research Lab API publishes evidence-backed research records for projects building on Robinhood Chain (chain id 4663): project dossiers, ships and releases, contracts, on-chain usage, market context, and a dated change ledger. Every claim it returns is tagged FACT, DERIVED, or UNKNOWN and carries a typed evidence id that resolves to a receipt with its source. Builder views such as the Builder Radar, accelerating builders, comebacks, and weekly and monthly reports sit beside per-project timelines, diffs between two dates, and relationship maps. Token contracts resolve to published projects by chain id and address rather than by symbol. ## For AI agents Research Robinhood Chain projects with sourced evidence: read a project's dossier, ships, contracts, timeline, and change history, resolve a token contract to its project, and fetch evidence receipts for every claim. ## Scope Does not provide wallet analytics, price predictions, investment advice, or trade execution. Use for evidence-backed research on Robinhood Chain projects only. ## Capabilities - Search and browse published Robinhood Chain projects by name, symbol, kind, status, or narrative - Read one project's dossier, snapshot, coverage, and timeline with every claim tagged FACT, DERIVED, or UNKNOWN - Compare what changed for a project between two dates with the diff and change-ledger reads - Resolve a token contract address on chain 4663 to its published project, or up to 30 contracts in one keyed call - List what projects shipped and track builders through the Builder Radar, accelerating builders, and comebacks - Resolve a typed evidence id such as ship: or abi: to the receipt behind a published claim ## Use cases ### Agent research on a Robinhood Chain token An AI agent asked about a token on Robinhood Chain needs sourced facts, not a guess. Through Jentic the agent searches for 'resolve a token contract to a project', loads the HEY lookup operation, and passes chain id 4663 and the contract address. It then reads the project snapshot and coverage, so its answer separates what HEY records as fact from what HEY marks unknown, each with a source. Example prompt: Call GET `/api/token/{chainId}/{address}` with chainId 4663 and a 0x contract address, then call GET `/api/projects/{slug}/snapshot` for the returned project slug and summarise its FACT and UNKNOWN lines ### Builder activity monitoring A research desk tracking who is actually shipping on Robinhood Chain polls the HEY change ledger with a cursor and reads the ships feed by project and date window. Each ship and change carries its source, so a digest can cite the release or contract change rather than restating market moves. The Builder Radar and accelerating-builders reads add a ranked view of shipping momentum. Example prompt: Page GET `/api/changes` with the after cursor from the previous run, then call GET `/api/ships` with project and since filters and list new releases with their evidence ids ### Point-in-time project comparison An analyst writing a project review compares two to four projects side by side and checks what changed for one of them across a date range. HEY returns the diff between two days at most 400 days apart and labels it as a difference, not an explanation, so the review states changes without inventing causes. Example prompt: Call GET `/api/compare` with slugs for two projects, then call GET `/api/projects/{slug}/diff` with from 2026-08-01 and to 2026-11-01 for the first project ### Claim verification with evidence receipts A writer citing HEY data verifies each figure before publishing. Every published claim carries a typed evidence id, and the evidence read resolves it to a receipt with the original source, while the explain read states why HEY publishes a given fact for a project. Example prompt: Call GET `/api/evidence/{id}` for an evidence id taken from a project timeline and report the source and observedAt date in the receipt ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/api/projects` | Search and browse published projects | | GET | `/api/projects/{slug}` | Get one project's dossier | | GET | `/api/projects/{slug}/timeline` | Get a project's evidence timeline | | GET | `/api/projects/{slug}/diff` | Compare a project between two dates | | GET | `/api/changes` | Read the change ledger | | GET | `/api/token/{chainId}/{address}` | Resolve a token contract to a project | | GET | `/api/ships` | List what projects shipped | | GET | `/api/evidence/{id}` | Resolve an evidence id to a receipt | ## Key resources - **Projects** — Search, dossier, snapshot, coverage, timeline, history, diff, contracts, relationships, usage, and market context for published projects - **Ships and changes** — The ships feed and cursor-paged change ledger, with CSV exports - **Contracts and tokens** — Contract research entities and token-to-project resolution by chain id and address - **Chain and builder views** — Chain day-by-day, Builder Radar, accelerating builders, comebacks, unlocks, Uniswap v4 hooks, and weekly and monthly reports - **Agent contract** — Agent capability answers, A2A JSON-RPC, and research receipt validation ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 66 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 79 / 100 - Developer Experience & Jentic Compatibility: 69 / 100 - AI-Readiness & Agent Experience: 56 / 100 - Agent Usability: 93 / 100 - Security: 55 / 100 - AI Discoverability: 54 / 100 - **View full report:** https://jentic.com/apis/heyresearch.xyz/heyresearch/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring HEY by hand means deciding between anonymous reads and a key, choosing the bearer or x-api-key form, and handling 308 redirects for renamed slugs and 429 quota answers. Through Jentic you install once, import HEY Research Lab from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** HEY puts the project slug in the URL path (`/api/projects/{slug}/...`), so a rule can pin your agent to one project's reads. You choose the operations it may call, so bulk reads like CSV exports or the A2A JSON-RPC interface are not included unless you add them. - **Credential handling:** Your HEY API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'research a Robinhood Chain project' or 'what changed for a project', and Jentic returns the matching HEY operation with its input schema, including slug and date parameters, so the agent calls the right endpoint. ## Related APIs - **Dune** — SQL queries over indexed on-chain data across many chains, rather than curated project research - **CoinGecko** — Cross-asset token prices and market data to pair with HEY's builder evidence - **Alchemy** — Blockchain node and data access for reading contracts and transactions directly ## FAQ ### What authentication does the HEY Research Lab API use? Per its OpenAPI spec, a key is optional on most reads: the spec declares a bearer token (Authorization: Bearer) and the same key in the x-api-key header. Two bulk reads, GET `/api/snapshots` and GET `/api/token/{chainId}`, require the key. Through Jentic the key is stored by your own instance and attached at call time, so the agent never sees it. ### What are the rate limits for the HEY Research Lab API? The spec states that calls without a key get 120 requests a minute per client address, with anonymous answers cached for 60 seconds. A free key keeps 120 a minute in its own bucket, and every key carries a monthly allowance that answers 429 quota once spent. See https://heyresearch.xyz/developers for current tiers. ### Can I find out what changed for a project with the HEY Research Lab API? Yes. GET `/api/projects/{slug}/diff` compares a project between two dates at most 400 days apart, and GET `/api/changes` returns the change ledger, filterable by project, contract, type, and date and paged with the after cursor. HEY states a difference, never a cause. ### Is there a HEY Research Lab MCP server? You don't need an MCP server to give your agent the HEY Research Lab API. Jentic connects it directly from the API Directory: import it, store your key once if you use one, and your agent calls the project and change-ledger operations it needs without loading another server's tool definitions into its context. ### Can I limit what my agent is allowed to do with the HEY Research Lab API? Yes. For example, write a rule that allows only the GET operations under `/api/projects/{slug}` for one project slug, plus the evidence read, so the agent can research that project and resolve its receipts but cannot run bulk exports or the A2A interface. Every call it makes is logged. ### How do I look up a token contract through Jentic? Search Jentic for 'resolve a token contract to a project', load the GET `/api/token/{chainId}/{address}` operation, and execute it with chainId 4663 and the 0x contract address. The response names the published project, which you can then read with GET `/api/projects/{slug}.` To run it on your own infrastructure, install Jentic One from its GitHub repo.