Every forecast, as JSON.
Read-only and unauthenticated. The same data the site is built from — nothing is hidden behind a key, and the ledger endpoints let anyone check the record independently.
Service status, forecast count and whether the ledger chain still verifies.
{
"status": "ok",
"forecasts": 7913,
"ledger_ok": true
}
Published forecasts, newest first. Filter with ?status=scheduled or ?division=E0.
{
"count": 52,
"data": [{
"fixture_id": "…",
"home": "Arsenal", "away": "Chelsea",
"p_home": 0.52, "p_draw": 0.25, "p_away": 0.23
}]
}
Scored history: RPS, closing-line value and the same record the site shows.
{
"settled": 7861,
"rps": 0.2022,
"accuracy": 0.509,
"clv_mean": -0.0037
}
Recomputes every row hash and returns the chain head. Slow by design — it does the real work.
{
"ok": true,
"rows": 7913,
"head": "f7c97bf2…"
}
Accumulator search. Takes ?target=10&min_legs=2&max_legs=6 and returns the most probable slips.
{
"slips": [{
"combined_odds": 9.75,
"model_probability": 0.124,
"legs": [ … ]
}]
}
Verifying without trusting us
Each forecast carries its row hash and the previous row's hash. `/api/v1/ledger/verify` recomputes the whole chain and returns ok: true only if every link matches — so a silently edited probability would be detectable years later.