Four JSON endpoints, refreshed every ~6 hours by the same pipeline that runs the live desk. What makes this dataset different: the track record behind it is cryptographically verifiable — the ledger is sha256-fingerprinted daily and past fingerprints are never edited.
GET onlyno authno rate keyCORS *Every settled engine position, deterministic field order, sorted by resolution — this exact byte stream is what gets fingerprinted. Verify it in one line:
curl -s https://rex-income.vercel.app/ledger/ledger.json | shasum -a 256 # compare with the latest entry in /ledger/hashes.json
| field | meaning |
|---|---|
| id | engine position id (stable) |
| conditionId | Polymarket condition id — resolve it on-chain |
| question · outcome | the market and the side the engine took |
| entryPrice · stakeUsd | entry (0–1) and paper stake |
| status · pnlUsd | won | lost and the realized result |
| createdAt · resolvedAt | ISO timestamps, open → settled |
Append-only: one fingerprint per UTC day (date, sha256, settled, wins, losses, pnlUsd). Past days are immutable; every snapshot is also committed to git as an independent witness. If a published hash ever stopped matching the ledger, the dataset would be provably corrupt — that's the deal we signed.
The engine's current smart-money screen: picks[] with slug, conditionId, outcome, currentPrice, payoutMultiple, weightedScore (the ranking signal), top-holder stats (holderCount, bestHolderRank, avgHolderRoi, totalSizeUsd) and hoursToResolution. Refreshed ~6h; check generatedAt.
strategies[] with out-of-sample, survivorship-bias-free numbers: hitRatePct, ci95, edgePts, roiPerBetPct, n. Backtests are labeled as backtests — forward performance lives in the ledger, losses included.
Free for any use, commercial included. If you build something public with it, a link back to rex-income.vercel.app is appreciated — and if you cite the hit rate, cite the forward number (wins ÷ settled, losses in), never a backtest alone. Paper-trading data; not financial advice.
Building on this? The pages behind it: Forward Ledger · losses · settled verdicts · today's verdict · roast machine.
Endpoints are static snapshots on a CDN — hammer them as hard as you like. Schema additions are backwards-compatible; existing fields don't change meaning. Found something broken? The whole pipeline is auto-generated, so it'll be fixed at the source.