Resources

All endpoints are GET, unauthenticated, under https://api.hypersight.xyz/v1. Every response includes generatedAt (epoch ms). See Freshness.

What each one weighs

Sizes decide how you call this. The aggregates are small enough to poll; one curve is not, and the bulk export is a download, not a request.

manifest.json

The archive’s table of contents. Also served at the API root (/).

{
  "generatedAt": 1787000000000,
  "freshness": "regenerated on market settlement (~1 min) and nightly; not continuous",
  "license": {
    "name": "CC BY 4.0",
    "url": "https://creativecommons.org/licenses/by/4.0/",
    "attribution": "Hypersight (hypersight.xyz)"
  },
  "coverage": { "firstExpiryMs": 1777788000000, "lastExpiryMs": 1787000000000 },
  "counts": { "settledMarkets": 700, "settledEvents": 300, "marketFiles": 1000 },
  "resources": ["/v1/archive.json", "/v1/events.json", "/v1/governance.json", "/v1/markets/{outcomeId}.json"]
}

Counts and timestamps above are illustrative — the archive grows daily, and the live manifest is the only truthful copy of its own numbers.

archive.json

Every settled price market (crypto binaries and buckets), newest first.

events.json

Every resolved event market (macro decisions, sports fixtures, one-off questions), with the winning side and, for matches, the final score.

Every field above is always present on every event row. Optional ones carry null rather than disappearing, so the shape does not change from row to row.

archive/{YYYY-MM}.json and events/{YYYY-MM}.json

The same rows, sliced by the month a market resolved in. The whole-archive documents stay the simplest way in, but they grow with the archive; these let you fetch a slice, or backfill history once and never read it again. The manifest’s shards array lists every month that exists, with its counts.

Both files exist for every month the manifest lists, with count: 0 and an empty array when that month had none of that kind. So the obvious loop over shards never hits a 404.

curl https://api.hypersight.xyz/v1/archive/2026-07.json

changes.json

The most recent resolutions, newest first: outcomeId, type, settledAt and the market’s URL. Poll this instead of re-reading the aggregates.

It is deliberately bounded (500 entries). If your last sync is older than oldestSettledAt, the feed cannot tell you what you missed, and it says so in its own note field: re-read archive.json and events.json instead of assuming the gap is empty.

bulk/manifest.json

Gzipped JSON Lines covering the whole archive, one market per line. A line is the same document markets/{id}.json serves — market, dataQuality, deployer, family, flow, oddsMeta, the series URLs and the settlement — with outcomeId promoted to the top level, because a line has no URL to say which market it is. Regenerated nightly. Ingest it once, then follow changes.json.

The two heavy series ship beside it, one line per market, keyed by outcomeId: odds.*.jsonl.gz and price.*.jsonl.gz. They are separate files for the same reason they are separate resources: most callers want the results, not the tapes.

All three are split by size, so read files rather than guessing chunk names: marketChunks, oddsChunks and priceChunks say how many of each exist, and the counts move as the archive grows.

# Fetch every chunk the manifest lists, whatever it is called
curl -s https://api.hypersight.xyz/v1/bulk/manifest.json   | jq -r '.files[].url'   | xargs -I{} curl -O https://api.hypersight.xyz{}

openapi.json

An OpenAPI 3.1 description of this surface, generated with the live counts and coverage window. Every response is described field by field, and the two row shapes are named schemas (PriceMarket, EventMarket), so a generated client comes out typed rather than as a bag of any.

npx @openapitools/openapi-generator-cli generate \
  -i https://api.hypersight.xyz/v1/openapi.json -g typescript-fetch -o ./client

governance.json

Aggregated validator settlement activity: how many settlement actions were observed, vote counts, and the most active validators by address.

voteLag

The zero of this axis is the action’s opening, which Hyperliquid does not publish: it is derived as expireTime - votingWindowMs. That makes one field load-bearing.

This file also carries n, quorum_reached and last_seen as deprecated aliases of count, quorumReached and lastSeen. They are the raw column names, kept only because v1 promises nothing disappears. Read the camelCase ones; a future major version drops the others.

markets/{id}.json

One market in full: the page most builders want.

curl https://api.hypersight.xyz/v1/markets/813.json

{
  "generatedAt": 1787097654338,
  "type": "event",
  "dataQuality": { "complete": true, "missing": [] },
  "market": {
    "outcomeId": 813,
    "questionTitle": "World Cup Semifinal: France vs Spain",
    "side0": "France", "side1": "Spain",
    "winnerSide": 1, "winnerLabel": "Spain",
    "homeTeam": "France", "homeScore": 0, "awayTeam": "Spain", "awayScore": 2,
    "expiryMs": null, "settledAt": 1784055600000,
    "totalVolume": 8121997,
    "yesVolume": 2301278, "noVolume": 5820719,
    "tailNotional": 4927922,
    "traders": 1403
  },
  "family": null,
  "oddsMeta": {
    "points": 1095, "firstTs": 1783754570921, "lastTs": 1784062640022,
    "gaps": [{ "fromTs": 1783756269650, "toTs": 1783757376985 }, "… 66 in total"],
    "complete": false, "captureRegime": "event-5s", "source": "book-archive"
  },
  "oddsUrl": "/v1/markets/813/odds.json",
  "tradeOddsMeta": { "points": 8189, "firstTs": 1783755987011, "lastTs": 1784070782196 },
  "tradeOddsUrl": "/v1/markets/813/trade-odds.json",
  "settlement": {
    "quorumReached": true,
    "voters": [{ "validator": "0x8a5d…", "name": "Hyperdash", "stakePct": 2.05, "firstSeen": 1784064279788 }, "… 14 in total"]
  },
  "settlementApplicable": true,
  "settlementCaptured": true
}

A verbatim snapshot of the live document (19 Aug 2026), trimmed where marked — not a cleaned-up ideal. This market is complete: false on purpose: an archive that claims completeness it does not have is worse than one that reports its own holes, and dataQuality exists so you never have to guess.

The flow object

Every figure below is measured per fill from our raw archive, deduplicated per trade: the index serves one row per participant, two per trade.

{
  "fills": 8697,
  "traders": 1016,
  "fee": 4.97,
  "builderFee": 4.97,
  "buyNotional": 1615840.34,
  "sellNotional": 391210.73,
  "splitNotional": 1366973,
  "tailNotional": 1979720.84,
  "tailFills": 1886,
  "deduplicated": true,
  "vwapYes": 0.66,
  "vwapNo": 0.26,
  "biggestFill": 99999.99,
  "bestEntryPx": 0.299
}

markets/{id}/odds.json

The odds series on its own, because a long-running market carries tens of thousands of points (~1 MB uncompressed) that most consumers do not need. Fetch it only when oddsMeta.points > 0.

{
  "generatedAt": 1787097654338,
  "outcomeId": 813,
  "points": 1095,
  "odds": [ { "ts": 1783754570921, "px": 0.5 }, "…" ]
}

Each point is the YES side’s mid price on the 0 to 1 probability scale. How densely they were recorded, and by whom, is in oddsMeta.captureRegime and oddsMeta.source — see Resolution and provenance.

markets/{id}/trade-odds.json

The TRADE odds: every real transaction price of the YES coin, based on the fills archive (buys and sells only, consecutive identical prices collapsed). Same shape as odds.json plus one extra field: volumeBuckets, ~48 adaptive buckets of { t, yes, no } traded notional across the market’s life, from the same deduplicated fills (absent on files derived before the histogram shipped). Its own file and its own name: a different instrument from the sampled mid, never blended with it. Fetch it when tradeOddsMeta is non-null; it exists even for markets that settled before the mid capture was born.

curl https://api.hypersight.xyz/v1/markets/141/trade-odds.json

markets/{id}/settlement.json

Which validators voted the settlement, with the name and stake weight each carried at vote time.

{
  "generatedAt": 1787356995910,
  "outcomeId": 674,
  "found": true,
  "reason": "FIFA officially declared France the winner of the Game.",
  "quorumReached": true,
  "finalized": true,
  "voters": [
    { "validator": "0x0000…acb8", "name": "ValiDAO", "stakePct": 1.5, "firstSeen": 1784160139953 }
  ]
}

Fetch it when settlementUrl is non-null. The market document keeps the verdict and a voterCount; only the roster lives here.

curl https://api.hypersight.xyz/v1/markets/674/settlement.json

markets/{id}/price.json

What the underlying did over the window the market was live, at 5-minute resolution — Hyperliquid’s own price, the one the market settled against, not another venue’s. Frozen at settlement and never recomputed.

{
  "generatedAt": 1787330633626,
  "outcomeId": 3,
  "interval": "5m",
  "points": [ { "t": 1777960800000, "c": 1823.4 }, "…" ]
}

Fetch it when priceUrl is non-null. It is null in two cases, and they are different: event markets have no ticker at all, and a handful of price markets closed before this capture existed.

curl https://api.hypersight.xyz/v1/markets/3/price.json

Anything outside /v1 on this hostname returns a JSON 404.

A 403 applies to a caller, not to a resource: an address lands there after abuse and every path answers the same way. There is nothing to retry, and it is never about authentication — this surface needs no credentials.