Skip to main content
Pulse runs an indexer against Hyperliquid L1 + builder dexes + HIP-4. This page covers what’s tracked, how often it updates, and the historical bounds you should expect.

​
What’s indexed

​
Cutoffs

Some endpoints have hard historical floors because the underlying data collection started after Hyperliquid mainnet:
  • Risk metrics (liquidations, mark dislocations, user-action–derived signals) — clamped to 2026-01-01. Earlier since requests are silently truncated to that floor.
  • HIP-4 outcomes — clamped to 2026-05-02 (mainnet launch). Earlier since requests are silently truncated.
  • Cohort tiers — recomputed daily. Wallets active for less than ~1 week may not yet have a tier assigned.
  • Builder-fee attribution — orders complete from 2025-01-25; trigger-order (stop/TP) fill capture live since 2026-08-20, backfilled to 2026-03-24 with earlier history in progress. Ledger revenue has no floor (cumulative on-chain data). See Builder codes & attribution.
Separately from these floors, caller-controlled windows are silently clamped to 90 days on every tier — see Data windows and authentication.

​
Freshness

The /live/* endpoints are designed for near-real-time use. Typical freshness: The pulse_market_overview response includes generatedAt timestamps so you can measure staleness server-side.

​
What’s not indexed

  • Spot trades on non-canonical pairs (@N indexes) — present in raw data, not classified into cohorts.
  • Off-chain orderflow (RFQ, OTC) — only on-chain L1 fills are captured.
  • Private user information (KYC, beneficial ownership) — addresses are public; wallets are not de-anonymized.

​
How recent is “recent”?

Tools that take a since parameter accept a number plus unit:
  • m — minutes (e.g. 10m)
  • h — hours (e.g. 24h)
  • d — days (e.g. 7d)
Weeks are not a unit — 2w is rejected with 400 invalid since format; use days (14d). Or use explicit startTime / endTime (unix ms or ISO date) for exact ranges. Both are silently clamped to the universal 90-day window — see Data windows.