Free Data Status | HypeBasis

Direct answer

This is a coverage map, not a real-time uptime dashboard. It shows which public-data workflows support HypeBasis, where each dataset appears, and what the site hides when a source is missing, old, or incomplete.

Evidence for this answer

Hyperliquid public vault stats Hyperliquid Docs: Vaults

Last updated: 2026-08-26Last reviewed: 2026-08-26

Product boundary

A listed workflow is not an uptime promise or proof that every value is currently available. Check the timestamp and source state beside the live number before using it.

Documented workflows: 36
Active or checkable: 36
Paid or key-gated feeds: 0

Coverage map

Open a workflow to see its freshness contract, product use, and unavailable state.

Durable site snapshots

Deployed workflows backed by timestamped Cloudflare KV data.

Hyperliquid vault rankingsHyperliquid public vault stats listDurable

Freshness contract: Refreshed with timestamps and old-data checks.
Where it appears: The shared hourly trigger downloads the public vault list once, keeps the 25 largest open vaults above $100K TVL, and stores that small table. The vaults page reads KV only and makes no request to the multi-megabyte list.
When limited: The vault table stays hidden until the first hourly capture is stored. HLP and address lookups work independently.

HIP-3 capacity and configuration historyOfficial Hyperliquid HIP-3 DEX, limit, status, metadata, cap-status, and market-context snapshotsDurable

Freshness contract: Refreshed with timestamps and old-data checks.
Where it appears: The page shows current public capacity independently. A dedicated six-hour snapshot records configuration fields, and the event CSV publishes only differences between two valid captures with observed-between time precision.
When limited: Current public HIP-3 capacity remains visible when available; configuration events and downloads stay unavailable until two valid stored captures exist.

Funding estimate calibrationOfficial Hyperliquid HlPerp estimates joined to official settled funding historyDurable

Freshness contract: Refreshed with timestamps and old-data checks.
Where it appears: The page shows current estimates independently, stores one prospective observation per tracked market and hourly boundary, then publishes calibration aggregates only after 24 fresh consecutive matches. CSV downloads read the same bounded KV list without a new upstream request.
When limited: Current official estimates remain visible when available; calibration metrics stay hidden until fresh, consecutive forecast-to-settlement matches exist.

Native reserve historyOfficial Hyperliquid native borrow/lend reserve state joined to official spot token metadataDurable

Freshness contract: Refreshed with timestamps and old-data checks.
Where it appears: The reserve page shows current public state independently, then publishes saved utilization trends only after one asset has at least 24 fresh, well-spaced hourly captures. CSV downloads read the same bounded KV list without a new upstream request.
When limited: Current official reserve state remains visible when available; utilization history and changes stay hidden until fresh, sufficiently complete hourly captures exist.

HYPE official supply historyOfficial Hyperliquid HYPE total and circulating supply saved in optional free durable storageDurable

Freshness contract: Refreshed with timestamps and old-data checks.
Where it appears: The HYPE unlock tracker publishes 7-day or 30-day changes only after every daily official-supply capture in the selected window is present and fresh.
When limited: Observed supply changes stay hidden until the shared cron has saved every required UTC day. The live official supply read remains available.

Winning-wallet position historyHourly captures derived from complete official Hyperliquid public-wallet snapshotsDurable

Freshness contract: Refreshed with timestamps and old-data checks.
Where it appears: The whale board exposes 24-hour and 7-day aggregate comparisons after bounded complete history exists. The HYPE route also derives one-hour and 24-hour per-wallet position changes from public addresses present in both complete samples, with strict overlap and 1,000-HYPE materiality gates.
When limited: The board labels aggregate history and HYPE wallet moves as building, gapped, incomplete, or weak-overlap until enough comparable complete hourly captures exist.

Major market historyOfficial Hyperliquid core perp market snapshotsDurable

Freshness contract: Refreshed with timestamps and old-data checks.
Where it appears: Tracked market pages combine official candle and funding history with bounded hourly open-interest and rolling-volume captures. The whale board reuses the saved hourly funding rates for coverage-gated 24-hour and seven-day receiving-side counts without another upstream request.
When limited: Price and funding history remain available from official endpoints; open-interest and rolling-volume history stay explicitly unavailable until hourly captures exist.

Market funding receiving-side historyCoverage-gated saved hourly Hyperliquid funding ratesDurable

Freshness contract: Refreshed with timestamps and old-data checks.
Where it appears: The hourly market-history workflow writes a compact receiving-side summary. The five-minute whale collector reads that small derived snapshot instead of reparsing the full market-history series.
When limited: The whale board labels saved funding history as building until the hourly market-history workflow writes a sufficiently covered derived snapshot.

Network explorer dashboardOfficial Hyperliquid data with labeled Hypurrscan indexed activityDurable

Freshness contract: Refreshed with timestamps and old-data checks.
Where it appears: Explorer overview and activity pages prefer a bounded five-minute public snapshot, with one timeout-bounded live cold-start fallback.
When limited: Each panel reports partial, stale, empty, or unavailable data without inventing missing activity.

Public whale-position boardOfficial Hyperliquid public leaderboard, perp state, and spot balancesDurable

Freshness contract: Refreshed with timestamps and old-data checks.
Where it appears: A scheduled worker refreshes current positions for a disclosed leaderboard-derived cohort every five minutes and rebuilds the cohort and full-feed PnL extremes every two hours. The dedicated HYPE whale route reads the same saved snapshot, keeps raw exposure separate from verified spot offsets and entity-adjusted exposure, and publishes coverage-gated position changes without another upstream request. The HYPE liquidation map groups side-consistent visible liquidation prices around a mark derived from the same snapshot and reports both position and notional coverage.
When limited: The board shows no substitute wallets when the scheduled official-source snapshot is missing or stale beyond its disclosed window.

Outcome market historyHyperliquid public outcome data saved in optional free durable storageDurable

Freshness contract: 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 limited: Outcome side-price change labels stay hidden when saved history is missing, over limit, old, broken, or disabled.

Assistance fund historyHyperliquid public assistance-fund balances saved in optional free durable storageDurable

Freshness contract: 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. Saved daily history feeds the balance chart after several capture days and the tokenomics burn-versus-staking-rewards comparison after seven complete daily intervals.
When limited: Burned-balance history stays hidden until saved daily captures span several days; the live balance read does not depend on it.

Local and scheduled snapshots

Collectors and fallbacks that create bounded saved datasets.

HYPE valuation contextOfficial Hyperliquid HYPE spot price and supply with separately labeled DeFiLlama revenue observationsSnapshot

Freshness contract: Used only when the saved data is fresh enough.
Where it appears: The page excludes the current UTC day and publishes a 7-day or 30-day revenue pace only when every completed daily observation in that window is present. Price, revenue pace, and supply basis remain editable without logging numeric inputs.
When limited: Missing official price or circulating supply withholds the live valuation. Missing, gapped, or stale revenue days withhold the affected window instead of extrapolating across the gap.

HYPE holder distributionHypurrscan indexed HIP-1 HYPE balancesSnapshot

Freshness contract: Used only when the saved data is fresh enough.
Where it appears: The page separates documented protocol system addresses before ranking non-system spot balances and compares indexed counts and balances at 24-hour, seven-day, and 30-day points.
When limited: Current count and ranking are withheld when the current index fails. Missing history or aliases remain explicitly partial instead of being inferred.

Outcome market historyHyperliquid public outcome dataSnapshot

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

Validator historyHyperliquid public validator dataSnapshot

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

HyperEVM metricsDeFiLlama documented free endpointsSnapshot

Freshness contract: 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 limited: TVL and APY stay hidden or limited, and protocol claims stay separate.

HyperLend lending dataHyperLend public APISnapshot

Freshness contract: 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 limited: Supply rates, borrow costs, collateral, and liquidation fields stay hidden when saved data is missing, old, incomplete, or broken.

Reference market depthHyperliquid, Binance, and Coinbase free public order booksSnapshot

Freshness contract: 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 limited: Depth, bid/ask delta, and spread stay hidden or limited. The page must not become routing or venue-quality advice.

Vertex market dataVertex public order bookSnapshot

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

Paradex market dataParadex public order bookSnapshot

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

Lighter market dataLighter public order bookSnapshot

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

edgeX market dataedgeX public order bookSnapshot

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

Active durable storageFree durable storage docsSnapshot

Freshness contract: Prepared for free durable storage, but only used when present.
Where it appears: Scheduled collectors write bounded public snapshots to the shared KV namespace; pages read those snapshots without requiring paid data feeds.
When limited: Pages must show saved-data or missing-data labels when storage is missing, over limit, old, or broken.

Validation and alert workflows

Checks and handoff records that do not promise delivery or availability.

Major market history checkSaved hourly Hyperliquid market observationsCheck

Freshness contract: Refreshed with timestamps and old-data checks.
Where it appears: The check reports capture freshness, cadence gaps, priority-market coverage, base-unit OI coverage, and whether 1h or 24h comparisons have enough history.
When limited: Missing, stale, malformed, or still-building history is reported explicitly and does not expose comparison metrics.

HyperLend data checkSaved HyperLend lending dataCheck

Freshness contract: 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 limited: Missing or old HyperLend data is a warning, not a lending-market or yield conclusion.

Reference depth checkSaved broader-market depthCheck

Freshness contract: 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 limited: Missing or old data stays missing or limited. HypeBasis does not infer liquidity, routing, or venue quality.

Reference depthSaved broader-market depthCheck

Freshness contract: 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 limited: Reference-depth labels stay hidden when saved data is missing, broken, old, or incomplete.

Vertex data checkSaved Vertex market dataCheck

Freshness contract: 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 limited: Missing or old data stays missing. It is not a market-quality conclusion.

Paradex data checkSaved Paradex market dataCheck

Freshness contract: 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 limited: Missing or old data stays missing. It is not a market-quality conclusion.

Lighter data checkSaved Lighter market dataCheck

Freshness contract: 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 limited: Missing or old data stays missing. It is not a market-quality conclusion.

edgeX data checkSaved edgeX market dataCheck

Freshness contract: 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 limited: Missing or old data stays missing. It is not a market-quality conclusion.

Perp DEX data checkSaved Perp DEX market dataCheck

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

Alert rule checksHyperliquid public market dataWorkflow

Freshness contract: 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 limited: Rules show waiting, invalid, or missing-data labels when market data or thresholds cannot be checked.

Alert delivery handoffAlert review recordsWorkflow

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

Outcome history checkSaved outcome historyCheck

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

Planned workflows

Documented boundaries that are not active production dependencies.

Perp DEX collector coverage

These checks review source readiness. They do not rank venues or tell a trader 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

Related tools

Sources and methods

Data dictionary

Local watchlist

Validator inspection

Sources

32 references · Expand

Hyperliquid public vault statsAccessed 2026-09-26
Supports: Public vault list with name, vault address, leader, TVL, closed status, parent/child relationship, creation time, reported APR, and day, week, month, and all-time PnL series.
Hyperliquid Docs: VaultsAccessed 2026-08-26
Supports: Current HyperEVM vault architecture and the distinction from legacy HyperCore vaults.
Cloudflare Workers KV Docs: LimitsAccessed 2026-05-12
Cloudflare Workers Docs: Cron TriggersAccessed 2026-05-12
Cloudflare Workers Docs: LimitsAccessed 2026-05-12
Hyperliquid Docs: HIP-3 builder-deployed perpetualsAccessed 2026-09-04
Supports: HIP-3 builder-deployed perp mechanics, deployer responsibilities, 500,000 HYPE staking requirement, minimum stake duration, deployment rules, configurable fees, settlement, oracle duties, slashing risk, cross margin, and backstop liquidation.
Hyperliquid Docs: Perpetuals info endpointAccessed 2026-09-04
Supports: Core and HIP-3 perpetual DEX discovery, current market contexts including rolling dayNtlVlm, perpetual metadata, funding history, predicted funding, DEX and market limits, DEX status, configuration metadata, clearinghouse state, and open-interest cap fields.
Hyperliquid Docs: Rate limits and user limitsAccessed 2026-09-04
Supports: Current REST request-weight, WebSocket, and user-limit constraints for public-data tooling.
Hyperliquid Docs: FundingAccessed 2026-09-04
Supports: Hourly funding, funding formula, interest-rate component, premium component, funding payment formula, and the direction of payments when funding is positive or negative.
Hyperliquid Docs: Info endpointAccessed 2026-09-04
Supports: Public info endpoint families used for market, book, candle, account, portfolio, native borrow/lend reserve, vaultDetails, userFees account-rate, and maxBuilderFee approval reads.
Hyperliquid Docs: Portfolio marginAccessed 2026-09-04
Supports: The pre-alpha status of portfolio margin, eligible quote-asset supplying and borrowing, utilization definition, hourly interest indexing, the documented pre-alpha stablecoin rate model, protocol interest buffer, LTV context, and liquidation mechanics.
Hyperliquid Docs: Spot info endpointAccessed 2026-08-26
Supports: Public spot token and pair metadata, rolling dayNtlVlm market contexts, outcomeMeta request and response fields, asset-context price and supply fields, tokenDetails maximum-supply definitions, and spotClearinghouseState balances.
Cloudflare Workers KV Docs: PricingAccessed 2026-05-12
Hyperliquid Docs: FeesAccessed 2026-08-26
Supports: Rolling 14-day volume tiers, perps and spot fee schedules, HIP-3 deployer fee scale and growth mode, strict HYPE staking-tier thresholds and discounts, referral fee formula and limits, staking-account linking risks, fee-model caveats, fee distribution to HLP, the assistance fund, and deployers, the assistance fund system address, and burn recognition of assistance-fund HYPE.
DeFiLlama: Hyperliquid fees and revenueAccessed 2026-08-26
Supports: Third-party daily, 7-day, 30-day, and cumulative fee and revenue estimates for Hyperliquid, with DeFiLlama's adapter methodology. Complete daily revenue observations support the HYPE valuation pace comparison.
Hypurrscan API: HIP-1 token holdersAccessed 2026-08-25
Supports: Third-party indexed HIP-1 holder counts, address balances, point-in-time holder snapshots, and public aliases. It does not establish beneficial ownership or merge staking and HyperEVM address balances.
Hyperliquid Docs: HyperCore and HyperEVM transfersAccessed 2026-08-25
Supports: The HYPE system address, its role in transfers between HyperCore and HyperEVM, and the limits of interpreting its balance as one holder.
Hyperliquid public leaderboard statsAccessed 2026-08-24
Supports: Public leaderboard address rows, account-value fields, and day, week, month, and all-time PnL, ROI, and volume windows used for position-cohort selection and full-feed PnL extremes. Current positions come separately from clearinghouseState.
Hyperliquid public explorer RPCAccessed 2026-08-20
Supports: Official public HyperCore transaction lookup by transaction hash for read-only explorer detail pages.
Hypurrscan API: current TWAPsAccessed 2026-08-26
Supports: Documented third-party chain-indexed endpoints for current TWAP programs, including indexed parent size, side, duration, market asset ID, and schedule time used for transparent scheduled-pace calculations; plus recent transfers, deployments, auctions, fee observations, spot USDC observations, aliases, and public search.
Hyperliquid node README: Validator endpointsAccessed 2026-08-20
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-08-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
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.