Free data architecture

Free Data Status

A status inventory for HypeBasis collectors, local snapshot outputs, production behavior, and unavailable-state rules.

Last updated: 2026-05-11Last reviewed: 2026-05-11
Product boundary
This page describes operational data boundaries. It is not a market status page, uptime guarantee, alert-delivery promise, or yield recommendation. Missing local or self-hosted snapshots must remain visible as unavailable states.

Direct answer

HypeBasis uses free public sources plus ignored local JSON outputs for optional history and audit trails. Production pages should not depend on paid APIs, API keys, or hidden hosted services. When a collector has not run, the matching page should show unavailable, partial, or stale context.

Collector inventory

Commands are local or self-hosted. Output paths are ignored local artifacts unless a future free storage adapter is explicitly documented.

Outcome market history

Hyperliquid public info endpoint

npm run outcomes:collect
Output
.hypebasis/outcome-history.json
Production behavior
Outcome pages use stored local/self-hosted history only when available.
Unavailable state
Probability-change context stays unavailable instead of being inferred from the current quote.

Validator history

Hyperliquid validatorSummaries info endpoint

npm run validators:collect
Output
.hypebasis/validator-history.json
Production behavior
Staking pages show aggregate local-history context only when enough fresh snapshots exist.
Unavailable state
Concentration deltas, commission-change audits, and charts stay unavailable when history is missing or stale.

HyperEVM metric context

DeFiLlama documented free endpoints

npm run ecosystem:collect
Output
.hypebasis/hyperevm-metrics.json
Production behavior
Ecosystem pages can show optional third-party context when a local/self-hosted snapshot exists.
Unavailable state
TVL and APY context remains unavailable or partial, and primary protocol claims stay separate.

Local alert runtime

Hyperliquid public market data

npm run alerts:run
Output
.hypebasis/alert-outbox.json
Production behavior
Alert evaluation writes local audit records and does not send email by itself.
Unavailable state
Rules show waiting, invalid, or unavailable states when market data or thresholds cannot be evaluated.

Local alert delivery files

Local alert outbox records

npm run alerts:deliver
Output
.hypebasis/alert-email-outbox/
Production behavior
Delivery creates local .eml files for self-hosted workflows without a paid email API.
Unavailable state
No delivery guarantee is implied; missing consent, unsubscribe, or duplicate records remain skipped.

Verification

`npm run verify` runs `npm run data:free-audit` before tests, lint, and production build. The audit scans operational collectors, stores, and free-data pages for paid or key-gated service drift.

Related tools

Data persistence methodology

Read the storage rules and no-paid-service boundary.

Source methodology

See how claims are sourced and reviewed.

Alerts

Inspect local alert-rule and outbox behavior.

Validator inspection

Review the current free validator data surface.

Sources