API reference / Point-in-time archive

Point-in-time archive

Our own un-backfillable history: immutable daily snapshots of ephemeral feeds (on-chain pools & perps, pre-IPO marks, market regime, squeeze scores) with capture provenance — accumulated since day one, never overwritten.

3 endpoints. Pay per call in USDC via x402 with no account, or get unlimited calls for $99/mo. Every response is shaped { ticker, data, source, as_of }.

GET/api/v1/archive$0.02

Point-in-time archive catalog: every feed & entity with first/last capture dates

Use to discover the point-in-time archive: immutable daily snapshots of ephemeral market state (Hyperliquid perps/spot, JLP pool, pre-IPO marks, market regime, squeeze scores), captured once per UTC day and never overwritten or backfilled. Lists every feed and entity with date coverage; read days via /archive/{feed} and series via /archive/{feed}/range.

Example request
GET /api/v1/archive

Example response coming soon — call the endpoint to see the live shape, or check /openapi.json.

GET/api/v1/archive/{feed}$0.02

One archived day of a feed — full payload + provenance (latest or ?date=)

Use to read one immutable archived day of a feed (sol.jlp, hl.perps, prestocks.markets, scores.squeeze, …): the exact payload the live endpoint returned that day, plus provenance (observed/captured/ingested timestamps + a content hash proving contemporaneous capture). Defaults to latest; ?date=YYYY-MM-DD for a past day, ?entity= on multi-entity feeds.

Example request
GET /api/v1/archive/FEED

Example response coming soon — call the endpoint to see the live shape, or check /openapi.json.

GET/api/v1/archive/{feed}/range$0.03

Date-range history of an archived feed: per-day summaries + content hashes

Use for time-series questions over the archive: how JLP AUM, Hyperliquid funding, a pre-IPO token premium, or a ticker's squeeze score evolved day by day. Per-day summaries (oldest first, ?from ?to ?limit, max 366) with capture provenance; payloads omitted — buy a full day via /archive/{feed}?date=. History accumulates daily and cannot be reconstructed retroactively.

Example request
GET /api/v1/archive/FEED/range

Example response coming soon — call the endpoint to see the live shape, or check /openapi.json.