Free Data Status | HypeBasis

Last updated: 2026-05-15Last reviewed: 2026-05-15

Product boundary

This is not a market call, uptime promise, alert-delivery promise, or yield recommendation. If a source is missing, old, or too limited, HypeBasis should say so.

Direct answer

Use this page to check whether a number on HypeBasis is fresh enough to trust, whether it comes from a free public source, and what disappears when the data is weak.

Data areas

Markets, validators, ecosystem pages, alerts, and checks with clear freshness rules.

Checked areas

Pages that show when free public data is missing, old, or incomplete.

Paid feeds

The audit blocks paid feeds and key-gated sources.

What You Can Trust

Each row says where the data appears, how it stays fresh, and what HypeBasis hides when the source is weak.

Outcome market history

Hyperliquid public outcome data

Checked

Freshness: Used only when the saved data is fresh enough.
Where it appears: Outcome pages show saved history only when it exists.
When hidden or limited: Probability-change labels stay hidden instead of being guessed from the current quote.

Validator history

Hyperliquid public validator data

Checked

Freshness: Used only when the saved data is fresh enough.
Where it appears: Staking pages show history only when enough fresh saved data exists.
When hidden or limited: Concentration changes, commission-change notes, and charts stay hidden when history is missing or old.

HyperEVM metrics

DeFiLlama documented free endpoints

Checked

Freshness: Used only when the saved data is fresh enough.
Where it appears: Ecosystem pages can show third-party TVL and APY only when saved data exists.
When hidden or limited: TVL and APY stay hidden or limited, and protocol claims stay separate.

HyperLend lending data

HyperLend public API

Checked

Freshness: Used only when the saved data is fresh enough.
Where it appears: The HyperLend review page reads durable saved lending data refreshed by the shared hourly schedule, with the local saved file as a self-hosted fallback.
When hidden or limited: Supply rates, borrow costs, collateral, and liquidation fields stay hidden when saved data is missing, old, incomplete, or broken.

HyperLend data check

Saved HyperLend lending data

Checked

Freshness: Used only when the saved data is fresh enough.
Where it appears: HypeBasis reports whether HyperLend lending data is missing, broken, old, incomplete, or available.
When hidden or limited: Missing or old HyperLend data is a warning, not a lending-market or yield conclusion.

Reference market depth

Hyperliquid, Binance, and Coinbase free public order books

Checked

Freshness: Used only when the saved data is fresh enough.
Where it appears: Reference-depth pages can show saved broader-market depth without fetching external venues on every page load.
When hidden or limited: Depth, bid/ask delta, and spread stay hidden or limited. The page must not become routing or venue-quality advice.

Reference depth check

Saved broader-market depth

Checked

Freshness: Used only when the saved data is fresh enough.
Where it appears: HypeBasis reports whether broader-market depth is missing, broken, old, incomplete, or available.
When hidden or limited: Missing or old data stays missing or limited. HypeBasis does not infer liquidity, routing, or venue quality.

Reference depth

Saved broader-market depth

Saved data

Freshness: Refreshed with timestamps and old-data checks.
Where it appears: Reference-depth pages prefer fresh saved data when it is available; old or missing data stays clearly labeled.
When hidden or limited: Reference-depth labels stay hidden when saved data is missing, broken, old, or incomplete.

Vertex market data

Vertex public order book

Checked

Freshness: Used only when the saved data is fresh enough.
Where it appears: Comparison pages stay cautious until Vertex source quality is proven.
When hidden or limited: Vertex spread, depth, and bid/ask delta stay hidden or limited. HypeBasis must not infer venue quality or routing.

Vertex data check

Saved Vertex market data

Checked

Freshness: Used only when the saved data is fresh enough.
Where it appears: HypeBasis reports whether Vertex data is missing, broken, old, incomplete, or available.
When hidden or limited: Missing or old data stays missing. It is not a market-quality conclusion.

Paradex market data

Paradex public order book

Checked

Freshness: Used only when the saved data is fresh enough.
Where it appears: Comparison pages stay cautious until Paradex source quality is proven.
When hidden or limited: Paradex spread, depth, and bid/ask delta stay hidden or limited. HypeBasis must not infer venue quality or routing.

Paradex data check

Saved Paradex market data

Checked

Freshness: Used only when the saved data is fresh enough.
Where it appears: HypeBasis reports whether Paradex data is missing, broken, old, incomplete, or available.
When hidden or limited: Missing or old data stays missing. It is not a market-quality conclusion.

Lighter market data

Lighter public order book

Checked

Freshness: Used only when the saved data is fresh enough.
Where it appears: Comparison pages stay cautious until Lighter source quality is proven.
When hidden or limited: Lighter spread, depth, and bid/ask delta stay hidden or limited. HypeBasis must not infer venue quality or routing.

Lighter data check

Saved Lighter market data

Checked

Freshness: Used only when the saved data is fresh enough.
Where it appears: HypeBasis reports whether Lighter data is missing, broken, old, incomplete, or available.
When hidden or limited: Missing or old data stays missing. It is not a market-quality conclusion.

edgeX market data

edgeX public order book

Checked

Freshness: Used only when the saved data is fresh enough.
Where it appears: Comparison pages stay cautious until edgeX source quality is proven.
When hidden or limited: edgeX spread, depth, and bid/ask delta stay hidden or limited. HypeBasis must not infer venue quality or routing.

edgeX data check

Saved edgeX market data

Checked

Freshness: Used only when the saved data is fresh enough.
Where it appears: HypeBasis reports whether edgeX data is missing, broken, old, incomplete, or available.
When hidden or limited: Missing or old data stays missing. It is not a market-quality conclusion.

Perp DEX data check

Saved Perp DEX market data

Checked

Freshness: Used only when the saved data is fresh enough.
Where it appears: HypeBasis reports whether saved venue data is ready for future pages.
When hidden or limited: Missing, old, incomplete, or broken venue data is a warning, not a venue-quality or routing conclusion.

Alert rule checks

Hyperliquid public market data

Checked

Freshness: Used only when the saved data is fresh enough.
Where it appears: Alert checks create review records and do not send email by themselves.
When hidden or limited: Rules show waiting, invalid, or missing-data labels when market data or thresholds cannot be checked.

Alert delivery handoff

Alert review records

Checked

Freshness: Used only when the saved data is fresh enough.
Where it appears: Delivery can prepare handoff records without a paid email API.
When hidden or limited: No delivery is guaranteed. Missing consent, unsubscribed users, and duplicates stay skipped.

Optional durable storage

Free durable storage docs

Planned

Freshness: Prepared for free durable storage, but only used when present.
Where it appears: This store is tested for slow public data; outcome pages can use it only when free durable storage is present.
When hidden or limited: Pages must show saved-data or missing-data labels when storage is missing, over limit, old, or broken.

Outcome market history

Hyperliquid public outcome data saved in optional free durable storage

Saved data

Freshness: Refreshed with timestamps and old-data checks.
Where it appears: Saved public outcome history can refresh hourly. Outcome pages read it only when populated.
When hidden or limited: Outcome probability-change labels stay hidden when saved history is missing, over limit, old, broken, or disabled.

Assistance fund history

Hyperliquid public assistance-fund balances saved in optional free durable storage

Saved data

Freshness: Refreshed with timestamps and old-data checks.
Where it appears: The revenue page reads the assistance fund's burned HYPE balance live from the official API; the saved daily history only feeds the balance-over-time view once captures span several days.
When hidden or limited: Burned-balance history stays hidden until saved daily captures span several days; the live balance read does not depend on it.

Outcome history check

Saved outcome history

Saved data

Freshness: Refreshed with timestamps and old-data checks.
Where it appears: HypeBasis reports whether outcome history is missing, available, old, or broken.
When hidden or limited: Missing or old output is a warning, not proof that history was collected.

Perp DEX collector readiness

The Perp DEX check reviews Vertex, Paradex, Lighter, and edgeX data together. It does not rank venues or tell you where to route an order.

Vertex

0 public sources tracked.

Paradex

2 public sources tracked.

Lighter

2 public sources tracked.

edgeX

2 public sources tracked.

Verification

Free-data checks run before deploy. They make sure public pages use free sources, show old or incomplete data clearly, and do not depend on paid or key-gated services.

Related tools

Free data storage

See how HypeBasis stores free data without paid feeds.

Sources and corrections

See how claims are checked and fixed.

Alerts

See what alert rules can and cannot do.

Validator inspection

Review current validator data.

Sources

Hyperliquid Docs: Info endpointAccessed 2026-05-04
Supports: Public info endpoint families used for market, book, candle, account, and portfolio tooling.
Hyperliquid node README: Validator endpointsAccessed 2026-05-11
Supports: Primary validator endpoint discovery for timestamped validator rows and unavailable-state handling.
DeFiLlama API: Protocols and YieldsAccessed 2026-05-11
Supports: Documented free DeFiLlama endpoints used for third-party TVL, yield, fee, and revenue context.
HyperLend Docs: APIAccessed 2026-05-20
Binance Spot API Docs: Order bookAccessed 2026-05-13
Binance USD-M Futures API Docs: Order bookAccessed 2026-05-13
Coinbase Exchange API Docs: Get product bookAccessed 2026-05-13
Cloudflare Workers KV Docs: LimitsAccessed 2026-05-12
Cloudflare Workers Docs: Cron TriggersAccessed 2026-05-12
Cloudflare Workers Docs: LimitsAccessed 2026-05-12
Paradex Docs: Get market orderbookAccessed 2026-05-15
Supports: Paradex order-book endpoint context for liquidity and depth checks.
Paradex Docs: List available marketsAccessed 2026-05-15
Supports: Paradex markets endpoint context for available-market and product-parameter checks.
Lighter API Docs: Order book ordersAccessed 2026-05-15
Supports: Lighter public order-book order endpoint context for market-health checks.
Lighter API Docs: Order book detailsAccessed 2026-05-15
Supports: Lighter public order-book detail endpoint context for market-health checks.
edgeX Docs: Public metadata APIAccessed 2026-05-15
Supports: edgeX public metadata endpoint context for market-list and market-health checks.
edgeX Docs: Public order book depth APIAccessed 2026-05-15
Supports: edgeX public order-book depth endpoint context for liquidity checks.
Hyperliquid Docs: Rate limits and user limitsAccessed 2026-05-04
Supports: Rate-limit and user-limit constraints for public-data tooling.
Cloudflare Workers KV Docs: PricingAccessed 2026-05-12