// COMPARE
outcometick vs Resolved Markets
What outcometick provides, row by row, beside what the Resolved Markets site states for the same thing as of 2026-11-03. Where their pages do not say, the cell says so. Prices are left out: both sides change them.
| outcometick | Resolved Markets | |
|---|---|---|
| Venues | Polymarket, Predict.fun | Polymarket, Hyperliquid |
| Chainlink settlement streams | Yes: Chainlink price and TWAP streams, the feeds the Up/Down markets resolve on | Spot crypto prices recorded at capture time; Chainlink not stated |
| Strike and outcome per market | Yes: strike and settled outcome per market, in the same archive as the order books | Settled market outcomes; strike not stated |
| Public settlement audit | Yes: markets recomputed from the archived settlement stream and compared with the official outcome, per-day verdicts downloadable | Not stated on the pages checked |
| Per-file checksum | SHA-256 and byte length listed per file | Not stated on the pages checked |
| File formats | Gzipped JSON Lines and CSV, plus Parquet | JSON and CSV |
| Access | REST API, Python and Node SDKs, ot CLI, MCP server | REST API, MCP server |
| Try before paying | A public sample day, no key or sign-up needed | Limited free tier |
| Backtest framework | Open-source engine for Python and Node: taker fees, fills walked through book depth, a queue for resting orders, markouts in the report; replays the sample day locally | Not stated on the pages checked |
| Hosted backtesting | Yes: your Python or Node strategy runs in a sealed sandbox against the archive; the same engine replays locally | On paid tiers, for some crypto Up/Down markets |
Resolved Markets column checked 2026-11-03, from: resolvedmarkets.com. Their site is the authority; tell us if a cell has gone stale.
Check it yourself
Every cell in our column can be checked before buying a key: the public sample day is one real day in the same formats as the paid archive, and the file schemas list every field.