Promethean Markets
Log inGet started
Prediction-market data infrastructure

The prediction-market record, certified daily.

Tick-level order books, trades and settlement prices from the venues where the world prices its beliefs — regulated exchanges, on-chain games and the crypto reference market — captured on one UTC clock and certified before they are sold.

Pre-launch — ten-source re-inception in progress · every file SHA256-manifested
availability → download → verify
$ export PM_API=https://api.promethean.markets
$ curl -sH "Authorization: Bearer $PM_KEY" \
"$PM_API/v1/availability?source=binance_spot" | jq '.days|length'
chain re-incepting · 0 released today · demo below is from a pre-launch certification day
$ curl -sH "…Bearer $PM_KEY" -o trades.parquet \
"$PM_API/v1/download?source=binance_spot&channel=crypto_trades&scope=BTC&day=2026-07-16"
212.8 MB · 2,805,821 rows
$ shasum -a 256 trades.parquet
79ef9ff6d7753d9c6b7afb9bc6ea6ab04fd0ed1ee7eeaed01c25d7058f5fc80f  trades.parquet
matches manifest.sha256 · 2026-07-16 certified
Binance spotin certification · pre-launchBinance USD-M futuresin certification · pre-launchPolymarket Up/Downin certification · pre-launchPolymarket broadin certification · pre-launchPolymarket Chainlink RTDSin certification · pre-launchPredict.Funin certification · pre-launchKalshi12d collecting493Mrows49 GBLimitless12d collecting156Mrows13 GBPancakeSwap Prediction8d collecting101Krows16 MBPolymarket US7d collecting4Mrows190 MB
10
Sources in certification
25
Up/Down selectors
100ms
Grid alignment
150/150
Trade partitions proven
Why this archive

Built so the data can defend itself.

Historical market data is easy to claim and hard to prove. Everything here is structured so you never have to take our word for it.

Certified before sold

A day enters the catalog only after five ordered gates pass — coverage, on-chain reconciliation, artifact audits, durable-mirror verification, and the gapless promotion gate.

Gapless by construction

The archive advances one contiguous day at a time. Red days are recovered and re-run, never skipped; corrections are a public ledger, never a silent rewrite.

Cross-venue by design

The venues, the reference exchange and the settlement oracle are captured against one UTC timeline: event feeds keep venue timestamps, gridded lanes align to 100ms, and every row carries source and receive time — so settlements can be reconstructed, not assumed.

Verifiable by you

Every file ships with a SHA256 manifest and row counts. You can re-hash every byte you buy and confirm it against the certificate — trust is checkable, not asked for.

One pipeline

Every completed UTC day runs the full chain.

Five ordered gates; a day that fails any of them is recovered and re-run — never skipped, never partially published.

01Close gateswindow coverage · 100ms floors · freshness lineage
Each selector’s expected market windows are compared against what we observed — including the evidence-gated venue_unlisted disposition. Coverage floors require ≥95% fresh-or-usable with a missing count of exactly 0; a day that misses any floor does not advance.
02On-chain trade reconciliationevery Polymarket partition proven vs the CTF-exchange OrdersMatched event
150 of 150 trade partitions have reconciled at every certification to date. Every trade row carries the transaction hash it was proven against, so you can spot-check it yourself on Polygon.
03Artifact auditsschema · timestamp walls · value domains · manifest counts + SHA256
Timestamp walls are enforced per-dataset: receive stamps must not trail event stamps, with one disclosed venue exception (Predict.Fun’s clock runs up to ~7.4s ahead of true receive time; rows store both stamps honestly). Row counts and SHA256 in every manifest must match the file exactly, and stable IDs must be unique.
04Durable mirror + verificationmirrored to object storage, re-verified by SHA256 metadata
Hundreds of files per day are mirrored and then re-verified by their SHA256 metadata — never by trusting storage ETags. A single mismatch blocks the day from release.
05Gapless promotion gateday D refused unless D-1 is released
The archive can only advance one contiguous day at a time. When a day goes red we recover it and re-run the chain; we never skip it or backfill silently.
What you get

Files, an API, and the means to check both.

Files

Day-partitioned Parquet — one file per source / channel / scope / day, each with a sibling manifest.

binance_spot/
crypto_trades/
BTC/
2026-07-16.parquet
2026-07-16.manifest.json
API

Bearer auth with keys prefixed pmk_. Four endpoints, released days only.

GET /v1/datasets
GET /v1/availability
GET /v1/download
GET /v1/manifest
Verification

Every file ships with a manifest. Re-hash it yourself; it equals the recorded SHA256.

{
"sha256": "79ef9ff6d7753d9c6b7afb9bc6ea6ab04fd0ed1ee7eeaed01c25d7058f5fc80f",
"row_count": 2805821,
"schema_fingerprint": "4f8b025ecbc7c9cc7b246eda92ff863437722d4c06af919760ff2e0d8cd2d7fc"
}
What it's for

Built to be re-run.

Evidence-grade history for the desks that stress-test it — where a result only counts if it survives being reproduced.

released dayyour modelreproducible result
All use cases →
Coverage

Pre-launch — ten-source re-inception in progress.

See full status →

The released chain restarts at the ten-source inception day. Every prior day was withdrawn to the public corrections ledger — nothing is sold that did not certify. View the corrections ledger →

One clock

The same instant, four vantage points.

t = 2026-07-16T12:00:00.000Z
Binance spotBTC book
bid 64,256.52 / ask 64,256.53
Chainlink RTDSBTC oracle
64,200.40218
Polymarket Up/DownBTC 1h books
Up .46/.47 · Down .53/.54
Predict.FunBTC Up/Down books
.10/.89 · .03/.97

BTC and ETH are captured simultaneously across a reference exchange, the settlement oracle, and two prediction venues — every row on one UTC clock, so a settlement can be reconstructed from all four.

The full matrix

Every rail on that same clock — including the ones still certifying.

BTCBinance spotBinance futuresChainlink oraclePolymarketPredict.FunKalshiLimitlessPancakeSwap
ETHBinance spotBinance futuresChainlink oraclePolymarketPredict.FunKalshiLimitlessPancakeSwap
SOLBinance spotBinance futuresChainlink oraclePolymarketKalshiLimitless
XRPBinance spotBinance futuresChainlink oraclePolymarketKalshiLimitless
DOGEBinance spotBinance futuresChainlink oraclePolymarketKalshiLimitless
BNBPancakeSwap

Solid rails are released and sellable today. Amber rails are already collecting on the same UTC clock — Kalshi, Limitless and PancakeSwap in certification, Polymarket US behind them — and each joins the released chain the day its own data certifies green. Nothing joins early, and nothing is backfilled.

The failure surfaces

Data we won't sell you.

Collection alone is never sellable

A venue joining the archive is not purchasable until it has its own certified days. Its history starts at certification — never backfilled from uncertified collection.

A red day is recovered

Missing data is a hard red, never silently patched. We recover the day and re-run the chain — we do not skip it or backfill quietly.

Venue gaps are disclosed

When a venue never listed an expected window, we say so — venue_unlisted, backed by recorded evidence, not patched over.

How certification works →
Quickstart

First file in under a minute.

Once you have a key: list released days, stream one, verify its hash. That's the whole loop.

Read the quickstart →
three curls
$ curl …/v1/availability?source=binance_spot | jq .days
$ curl -o t.parquet …/v1/download?…&day=<released-day>
$ shasum -a 256 t.parquet # == manifest.sha256

Start with the catalog, or tell us the coverage you need.

In candidate collection — not yet for sale