Skip to content

Releases: hey-research-lab/hey-research-open

@hey-research-lab/sdk 0.2.0

Choose a tag to compare

@hey-research-lab hey-research-lab released this 09 Oct 05:10

Added (coverage detail, 2026-10-09)

  • HeyCoverageEntry.stateDetail?: HeyCoverageStateDetail, additively: PARTIAL under MEASURED (part of the dimension measured; today contractActivity with partial_events_unreadable_some_days) and MAPPING_BLOCKED under NO_SOURCE (a candidate HEY holds — a declared site, docs or a repository — that nothing yet ties to the project; reasons site_not_corroborated, context_only_docs, context_only_repositories). HeyCoverageState keeps its nine values and their meaning; the finer state never replaces it.
  • HeyCoverageEntry.cause?: HeyCoverageCause (own_source_unreachable, provider_unavailable, budget_deferred), additively: whose side a SOURCE_UNAVAILABLE or deferred NOT_ENOUGH_YET read is on. Every existing state and reason code keeps its meaning; treat a value you do not know as a gap.

Added (market truth, 2026-10-09)

  • Valuation withheld reasons (valuationWithheld, valuationImplausible) gain chain_evidence_contradicts (more than 10× away from HEY's own chain readings) and sources_disagree (another source's price within a day more than 10× away), additively; fdvUsd is absent beside them as before. Treat an unknown reason as a withheld valuation you have no words for.
  • sourcesDisagree?: { source, priceUsd, observedAt } beside a published valuation, additively: another source within a day more than 2× away, so the figure is the shown reading's, not a settled fact.
  • HeyChainDay.dexVolumeWithheld?: 'implausible_vs_trailing_median' and HeyWeeklyReport.chain.dexVolumeWithheldDays?, additively: a day's DEX volume more than 10× its 14-day median is withheld (dexVolumeUsd absent), never shown as a figure.
  • HeyPoolStructure.dominantPoolShare is documented as a percentage (0–100, one decimal), as the API has always sent it; no value changed.

Added (partner scan card, 2026-10-09)

  • /api/v1/scan's not-found answer gains indexed?, research_state? (not_researched | not_published | not_indexed) and launched_via?, additively, beside found: false. ships_30d and releases_30d keep their documented zeros, with activity_measured saying whether they are measurements.

Added (alerts and search, 2026-10-09)

  • HeyAlertPresetId gains ship and code, and HeyAlertEventType gains build.code_activity (a weekly code-activity change, shown in the inbox only; never e-mailed or sent to a webhook), additively.
  • A search suggestion may carry sameNameDifferentContract?: true, additively: another page with the same name and a different contract.
  • Evidence receipts' contextReason gains launch_window (a follow-up deployment sent within 24 hours of the token's own creation: launch provenance, never building), additively.

Added (Partner Card evidence link, 2026-10-05)

  • HeyPartnerShip.evidence_link, additively: the latest meaningful ship's reader receipt page (/evidence/ship:<uuid>) with the card's attribution labels, as project_link carries them — the card's one "Evidence" link. evidence_id and url keep their meaning.
  • /api/v1/builder and /api/v1/scan answers are now cache-control: private, max-age=60 (they were public, s-maxage=60 without the integration header). No field changed; a client may still keep an answer a minute.

Added (status, 2026-10-03)

  • HeyStatus.integrity.failing?: { check, label }[], additively: the checks the newest integrity audit failed, by id and plain words. A failing audit now makes verdict critical (it read warn beside a failing run); integrity.verdict keeps its meaning.
  • HeyStatus.catalog.hidden? and hiddenAsOf?, additively. catalog.indexed keeps its meaning — the hidden launch records, approved rows HEY has not published, as /status has always labelled it; it is not the catalogue's "indexed" (every approved row). hidden is the same figure under the catalogue's word, and hiddenAsOf dates it by the hourly summary that counted it: asOf dates only published, verifiedBuilders and verifiedBuildersOnChain.

Added (token market, 2026-10-03)

  • HeyProjectDetail.tokenMarket.readingObservedAt? and figuresScope?: 'reading_pool', additively. readingObservedAt dates the reading behind liquidityUsd and volume24hUsd (evaluatedAt is when the status rule last ran); figuresScope says those pool figures describe the pool the status reading follows, not the token's volume24h. New tokenMarket.reason values not_a_fungible_token (decimals 0: no fungible market, no valuation) and reading_not_current (the newest reading is over 36 hours old), and a rescued market's (liquidity_in_another_pool) valuation is withheld; treat an unknown reason as a code you have no words for.

Added (follow → alerts, 2026-10-03)

  • HeyAlertPresetId gains deploy (contract.deployed: a contract the project deployed, never a serial launcher's follow-up) and status (build.status_changed, build.dormant and build.resumed: an activity status move, measured from building), additively. GET /api/alerts lists them among presets. No existing id changes meaning; treat an unknown preset id as a label you do not have words for.

npm: https://www.npmjs.com/package/@hey-research-lab/sdk

@hey-research-lab/mcp 0.2.0

Choose a tag to compare

@hey-research-lab hey-research-lab released this 09 Oct 05:10

Fixed (2026-10-09)

  • get_token_market printed the largest pool's share of liquidity a hundred times too large ("10000%"): the API sends a percentage (0–100) and the renderer read it as a fraction.
  • A valuation another source contradicts (sourcesDisagree) is printed DERIVED with "sources disagree", never FACT.

Changed (2026-10-09)

  • Bundles @hey-research-lab/sdk 0.2.0: coverage stateDetail and cause, the valuation gate's new withheld reasons (chain_evidence_contradicts, sources_disagree) with their plain words, a withheld chain DEX volume day, and the scan card's additive not-found fields.
  • get_evidence's description lists every evidence family from one list (v4hook: among them), as llms.txt does.
  • The research profile says in one sentence what research_answer still carries (market context labelled context only), instead of "builder intelligence only".
  • The listing note says what the API does: an unknown parameter name is ignored, but a known parameter with an unreadable value is refused (it said every unrecognised filter was ignored).
  • A frozen weekly report whose stored chain volume includes a withheld day is printed with no total and names the withheld days.

npm: https://www.npmjs.com/package/@hey-research-lab/mcp

v0.1.0

Choose a tag to compare

@github-actions github-actions released this 11 Sep 09:03