io.github.hey-research-lab/hey-research

HEY Research Lab

Evidence-backed Robinhood Chain research: builders, ships, contracts, changes, market context.

0.1.2
Version
remote + npm
Transport
13
Tools

Security review

Review passed

Reviewed 1d ago.

  • tools: 13 tools scanned
  • metadata: scanned
  • packages: 1 checked

No findings.

Tools (13)

  • find_projects

    Find Robinhood Chain projects by name, ticker or contract, or browse one of HEY's surfaces. A full 0x address is a contract lookup: is anyone building it, its ships in 30 days, the last one with its source. Surfaces: building-with-token: verified shipping, active or resumed, with a token whose market is live. still-building: verified activity continuing through a market drawdown HEY tracked. under-the-radar: eligible under HEY's Under the Radar rule (status shipping, active or resumed; Build Momentum at least 30; at least 2 meaningful events in the last 30 days, one of them a ship rather than a commit summary; a fresh reading of an active market, not a thin one or only a launch curve, for the project's own token) and a positive Discovery Gap — market-attention percentile below the build percentile; a positive gap alone is not enough, and it does not bound attention itself. shipping-now: status SHIPPING. most-active: shipping, active or resumed, by Build Momentum. new-builders: recorded

  • get_project_snapshot

    One project in one read: identity, build status and Build Momentum, market context with its kind or why it is withheld, on-chain use, 7-day product usage (distinct caller addresses per day — addresses, not people), verification, HoodLock locks, latest changes, freshness and what HEY does not know. Context blocks, never building: paid promotion (presence and dates), DefiLlama protocol economics (measured, not tracked or unread), developer footprint (counts only where measured).

  • get_changes

    The canonical change ledger for Robinhood Chain or one project: releases, ships, status moves, contract deployments and upgrades, verification, sources, scheduled unlocks — one event per change, with its own time and precision, when HEY first knew, and its evidence. Browse newest first; to follow along pass after=c1.0 (or a kept cursor) and keep each answer's cursor. A retraction means HEY no longer makes that claim. Facts, never causes.

  • get_project_timeline

    One project's research timeline: builds, releases, code, contract deploys, upgrades and interface changes, token verification, locks and scheduled unlocks, each with how precisely HEY knows its time. Lenses: everything, build, code, onchain, market, locks. Paged with the before cursor each answer gives.

  • explain_fact

    Why HEY publishes a fact about one project: the value, FACT, DERIVED or UNKNOWN, the canonical rule and version, the winning source and why, the inputs, the lineage from source to public value, and the evidence ids. Omit fact to list what can be explained; source.counted takes a source id.

  • get_evidence

    Open one published record by its typed id — ship:, signal:, abi:, impl:, lock:, source:, claim:, state:, integrity:, narrative:, method:, sourcechange:, security:, v4hook: — as a receipt: what it claims, its source URL, when it happened at what precision, when HEY knew, how it is backed. Ids come from the other tools. A withdrawn record says so.

  • get_token_market

    One token's market from HEY's own daily index: the current reading (valuation kind, provider), price, liquidity, volume and trades by day, the lifecycle (deploy, launchpad claim, stage, first trade), pools and depth, supply concentration (shares only, no addresses), contract checks and events by day. include=["moves"] adds each day-on-day valuation move with the building events published before it — a sequence, never a cause. Context, never a recommendation.

  • get_contract

    A contract as a research entity: creation, deployer (the only account named, with a count of other tracked projects' tokens it deployed), verified source and whose code it is (template, bytecode match or its own), Sourcify's answer, proxy and implementation history or the clone's original, interface changes, and 7 days of calls per method (counts; names withheld; an undecoded selector's signature candidate — a guess, never a name). chainId and address, or slug for all of a project's. A proxy HEY did not read is "not read", never "not a proxy".

  • project_diff

    One project between two dates (YYYY-MM-DD, at most 400 days apart): releases and meaningful ships, status and Build Momentum then and now, valuation and liquidity then and now, and the changes recorded — each from the nearest persisted point with its date and basis. Never a cause.

  • ask_hey

    A free-text question about one project (English or Malay). HEY matches it to the parts of its record it is about and answers only from that record, every line tagged FACT, DERIVED or UNKNOWN with its source. It records building only and offers no view on price.

  • chain_overview

    Robinhood Chain as a whole. view: days (default; trades, volume, tokens, transactions, launches, ships per day), this-week, weekly-report (an ISO week, or the latest), unlocks (scheduled HoodLock unlocks with proof), build-market (Build Momentum beside market attention). Aggregates only; nobody is named.

  • research_answer

    HEY's agent contract (AgentIntelligenceResponse v1), Robinhood Chain 4663: research_project; what_changed (1–30 days, project or chain); builder_status (rule, inputs, evidence); verify_project (is a contract the project’s); compare_builders (2–4, no winner); unknowns (every coverage state). Claims FACT/DERIVED/UNKNOWN with freshness and evidence ids; source text is quoted data.

  • market_integrity

    For one project: what happened to its tracked token market — liquidity against the level it held, trading, a pool migration — beside its builder activity, and where the two disagree. It describes the token market, never whether development stopped, and never calls a project a rug or safe.