Builder evidence, any way you want it.

TypeScript

SDK

@hey-research-lab/sdk is the API as typed calls, with one method per route, cursor and offset helpers, and errors as one code and a sentence. Install it from npm (Node 18 or newer, ESM and CommonJS); its source is in the public repository.

npm install @hey-research-lab/sdk

import { HeyClient } from '@hey-research-lab/sdk';

const hey = new HeyClient();                       // or { apiKey: process.env.HEY_API_KEY }
const snapshot = await hey.projects.snapshot('<slug>');
for await (const page of hey.changes.sync(kept ?? 'c1.0')) {
  apply(page.items);                                // upserts by revision, retracts by id
  kept = page.nextCursor;                           // keep it once the page is applied
}

Open source

Which package for what

MIT-licensed tools for Robinhood Chain (4663 only), each its own repository under github.com/hey-research-lab. The ones that talk to HEY read the same public API as this page; none of them changes what HEY researches.

Assistants

MCP server

An assistant such as Claude can call HEY while it answers you. The hosted endpoint speaks MCP over Streamable HTTP, stateless and read-only; it reads this same public API, so it can say nothing the API does not, and it is metered as you — the same limits, and your key's allowance if you send one as a bearer header.

# Hosted: Claude Code
claude mcp add --transport http hey-research https://heyresearch.xyz/mcp

For a platform that wants builder intelligence first, the research profile at https://heyresearch.xyz/mcp/research offers find_projects, get_changes, get_project_timeline, explain_fact, get_evidence, get_contract, get_v4_hook and research_answer: no market-move, Under the Radar or valuation tool, and the ledger without market events; research_answer still carries the market context of HEY's agent contract (the valuation with its kind, source and reading date, and the market status), labelled context only and never a builder judgement. The same registry, filtered.

Or run it beside your assistant from npm (Node 20 or newer); its source is in HEY's public repository. Set HEY_API_URL to read another instance.

# Claude Code
claude mcp add hey-research -- npx -y @hey-research-lab/mcp

# Claude Desktop (claude_desktop_config.json)
{ "mcpServers": { "hey-research": { "command": "npx", "args": ["-y", "@hey-research-lab/mcp"] } } }

The 14 tools

find_projects

Which project is this name, $TICKER or 0x contract, and is anyone building it? Or browse one of HEY’s surfaces (still building, under the radar, back from dormancy, shipping in silence, accelerating, the Builder Radar) with the catalogue’s filters.

get_project_snapshot

Tell me about this project: the important state of one project in one read, opening on the Research Summary (one tagged line each for build, usage, market, contracts, fundamentals, security, the latest change and what HEY does not know), then identity, build, market with its withholding, on-chain, verification, locks, latest changes, freshness and coverage.

get_changes

What changed on Robinhood Chain today or this week, or on one project? The change ledger: one event per change, with its own time, its precision, when HEY knew and its evidence. Cursor sync.

get_project_timeline

What did this project ship, and when? Its research timeline, every kind of evidence on one axis, paged with a cursor.

explain_fact

Why does HEY say this? For one published figure: the rule, the winning source, the inputs, the lineage and the evidence ids.

get_evidence

What backs this claim? One published record by its typed id (ship:, signal:, abi:, impl:, lock:, source:, claim:, state:), as a receipt.

get_token_market

Does this token still trade? Context beside the building, never advice — one token’s market from HEY’s daily index: current reading with its kind, lifecycle, pools, supply concentration (shares only), contract checks; optionally the day-on-day moves with what shipped before each.

get_contract

Who made this contract, and is it a known project’s? A contract as a research entity — creation, deployer, verified source, proxy and implementation history, interface counts and changes, activity, and for a Uniswap v4 hook HEY stores its callbacks and attribution — by address or for every contract of a project.

get_v4_hook

Who built a Robinhood Chain Uniswap v4 hook: the project HEY ties it to and on what basis (named only while HEY lists it), the callbacks its address declares, its source, pools on tracked tokens by week, and what HEY does not know.

project_diff

What changed for one project between two dates, from persisted points on named clocks. Never a cause.

ask_hey

A free-text question about one project, answered only from HEY’s record, every line tagged with its source.

research_answer

Is this project still being built, what did it ship, what changed? One bounded answer in HEY’s agent contract (AgentIntelligenceResponse v1) for one of six questions: research a project, what changed, builder status with its evidence, whether a contract belongs to a project, a builder comparison, and what HEY does not know (every coverage dimension’s state).

chain_overview

How active is Robinhood Chain? The chain as a whole: day-by-day activity, this week’s rollup, an archived weekly report, scheduled HoodLock unlocks, or Build Momentum beside market attention.

market_integrity

What happened to a project’s tracked token market beside its builder activity, and where the two disagree. Offered only while HEY publishes it.

Folded on 2026-09-30 and still answering, unlisted, until 2026-12-31: lookup_token — use find_projects with query set to the 0x address: the same read and the same answer. compare_projects — use research_answer with capability compare_builders and projects (builder metrics, no winner); each project's market context is get_token_market. get_project_coverage — use research_answer with capability unknowns and project: every coverage dimension's state (measured, not applicable, withheld, and each gap with its coverage state and what not to conclude).

Every answer tags its lines FACT, DERIVED or UNKNOWN, says how many it showed of how many and how to read on, and links the JSON it was rendered from; it also returns that JSON as typed structuredContent with an outputSchema. Resources (hey://project/<slug>, hey://changes/latest, …) and four research prompts come with it. Setup notes are in the MCP document.