Docs
How HEY works, in the same documents the code follows. Each page is the written contract for one part of the product, rendered from the repository so it cannot drift from what runs. Where a document and the product disagree, that is a bug in one of them and worth telling us about.
The whole thing, in one document
- Whitepaper v1.3 · PDFTwenty-three pages: the problem, the Discovery Gap, how building is measured and versioned, what is structurally absent, the coverage figures with the thin parts named, and the $HEY research economy. Updated 17 September 2026, with new sections on the two corrections made that day: the publication gate, and the collapse of restated code-activity ships.
- Deck 18 slides · PDFThe short version, with screenshots of the live product. What HEY answers, what it refuses to do, the numbers as they stood on 17 September 2026, and where the money comes from.
Both carry their date and their figures come from HEY’s own database on that day. Where a number has moved sharply the earlier reading is printed beside it, because the direction is part of the answer.
Both describe the scoring rules as they stood on 17 September 2026. The rules have changed since; the current ones are always on Methodology. The changes since the papers:
- 30 September hbm-v18: the Discovery Gap and Under the Radar are measured only on an active market.
- 30 September hbm-v19: Still Building’s drawdown is measured only on such a market.
- 30 September hbm-v20: a valuation implausible against its own liquidity is withheld, never used.
- 1 October hbm-v21: a market active only through another pool is measured on that pool, and Under the Radar needs a positive gap.
- 2 October hbm-v22: a launch pool is not a measured market, and automated or CI-only commits no longer count as building.
- 3 October hbm-v23: a repository’s releases on one UTC day count once.
- 3 October hbm-v24: a project’s contract deployments in the same second count once.
- 7 October hbm-v25: Resumed building is called only on a gap HEY watched: the comeback’s sources were being read when the gap began.
- 9 October hbm-v26: a valuation HEY’s own chain readings or another source contradict tenfold is no input to the Discovery Gap or Still Building, as it is shown on no surface.
- 12 October hbm-v27: a project whose building HEY cannot read gets no Discovery Gap, as it already got no Still Building.
- 12 October hbm-v28: a project’s contract deployments each within a minute of the one before count once, not only those in the same second.
- 15 October hbm-v29: a commit that only moves dependency versions in a manifest such as package.json, with or without its lockfile, is maintenance and no longer counts as building (commit-substance-v4).
- 16 October hbm-v30: no Discovery Gap on an unverified token whose ticker another published project’s token carries, nor on a market reading older than a day; Under the Radar only at typical market attention or lower.
- 18 October hbm-v31: a market whose reading carries less than $1,000 of 24-hour volume is too thin for a Discovery Gap, Under the Radar or Still Building; Still Building is not measured on a token whose ticker another published project’s token carries, nor when every builder source the project has is unavailable.
- 19 October hbm-v32: a 24-hour volume one source repeated beside the same price for more than 36 hours is unknown to the scorer, as it already was to the market status: it neither makes a market too thin nor counts as a measured volume.
Where to start
- You build something
- The builder guide for getting your page right in one screen, then Narratives for how HEY decides what a project is and Methodology for what counts as shipping. Claiming a page takes a minute and is free.
- You are building on HEY
- Start with the Partner Card if your bot, terminal or app meets a contract address — that is the common case, it is one call, and the page lets you try it on your own token. For a one-line answer in a chat, Putting HEY in your bot is the shorter
/api/tokenlookup. Then the Public read API for everything else, and the MCP server to give an assistant the same index, or HEY for agents to start an agent in one command. No key needed to read; a free key names you and unlocks bulk reads. - You want to judge HEY
- The whitepaper above, then Data sources for what HEY reads and what it refuses to read. §10.4 of the whitepaper is where the thin parts are named.
Reading HEY
- Watchlist, updates and feedsKeep the projects worth following and hear what changed, on the site, by mail or by feed.
- Research Terminal guideWhat the Terminal is, how to get in, a tour of every view, and how to read what it shows.
- This weekThe weekly rollup: what shipped, who went quiet, who came back.
- SearchHow search keeps published projects and launch records visibly apart.
- NarrativesHow a project gets its discovery labels, and why a label is never a rank.
- Data sourcesEvery third-party source HEY reads, what it is used for and what it is never used for.
- Sponsored placementsThe contract for the one paid, labelled row: what it buys and what it can never touch.
- AlertsTell HEY what to watch — a release, an implementation change, an unlock coming due — and hear it in HEY, by email or at your webhook.
- AI-assisted researchHow Ask HEY’s interpretations are written from HEY’s evidence only, checked, and kept away from scores.
Building on HEY
- Public read APIEvery endpoint, field, limit and promise of the free JSON API.
- MCP serverAsk an AI assistant about Robinhood Chain projects through HEY.
- Agent research receiptsA neutral, project-agnostic receipt an autonomous agent can publish for its own research, and how HEY checks the evidence it cites.
- WebhooksReceive releases, deploys, status moves and site changes as signed events, the moment HEY records them.
- Share cardsThe image and the text behind a shared project link.
- BadgesThe embeddable badge: what it states, what it never states, how to add it.
The $HEY token
Where HEY is going
- The Shipping Signal and its agentThe architecture plan: what fires the Meaningful Shipping Signal, what stops it being gamed, and how the Telegram agent delivers it without ever holding a key.
- Roadmap audit, September 2026What the roadmap claimed, what the code and the tables actually show, and why the roadmap now reads the way it does.
Also on the site
Methodology is how activity status, Build Momentum and Still Building are decided. API & MCP is the short version with working commands. Status shows whether HEY's own data is fresh. Scan asks “Is anyone building this?” of one address, including one HEY has never seen — and the integration guide is how to ask it from your own bot instead. The adapters, the scoring rules and the MCP server are published at hey-research-lab/hey-research-open under MIT, with saved fixtures and tests that fail on any real network call.