Don’t trust our probabilities. Check them.
Every number here is scored against finished matches we forecast before kickoff: not a backtest, not a training-set score. The raw figures are on a public endpoint with no key, so you can reproduce every one of them in a few lines of code before you write a line of integration.
Headline results
Matches scored
3,445
finished, forecast pre-kickoff
Log loss
1.0228
lower is better
Brier score
0.2042
lower is better
Calibration error
1.9%
avg gap, forecast vs reality
How the record is kept honest
Frozen before kickoff
The forecast is recorded ahead of the match and never edited afterwards.
Scored on results
Only settled matches count. Log loss and Brier score punish confident misses.
Against the market
Bookmaker odds with the margin removed are the benchmark, because it is the hardest one.
Open to inspection
The same numbers come from a public, keyless endpoint. Reproduce them yourself.
When we say 60%, it happens about 60% of the time
This is the check that matters for a probability API. If forecasts were honest, each dot would sit on the dashed line. Dots drawn hollow have fewer than 30 matches and are not counted as evidence either way.
Expected calibration error
- Home win3.2%
- Draw0.5%
- Away win2.1%
The average distance between the probability we gave and how often it happened. Lower is better.
Show the bin-by-bin table
Home win
Draw
Away win
Our forecasts vs the betting market
On matches with bookmaker odds, the market consensus still scores slightly better than our early forecasts. We publish that too.
Same 2,865 matches, same scoring. Lower log loss and Brier score are better; a positive edge means we scored better than the market. Small gaps are within normal noise and should not be read as an advantage either way. Where odds exist, the published forecast follows the bookmaker consensus (margin removed), because our own model has not beaten it. For a developer that is the useful part: you get market-grade probabilities, plus a model for the matches the market does not cover.
Our log loss
1.0228
Market log loss
0.9579
Log loss edge
-0.0649
behind market
Brier edge
-0.0146
behind market
Matchday record
The forecast frozen about an hour before kickoff, which is the one you would use on the day. It is recorded once and never edited. 583 settled matches, average lead 56 minutes.
Accuracy
54.2%
Log loss
0.9532
lower is better
Statistical model on its own, same matches: log loss 1.0198, accuracy 48.9%. Where bookmaker odds exist, the published forecast follows the market, because our model has not beaten it.
- Bookmaker consensus (margin removed): 572 matches, log loss 0.9543, accuracy 53.8%
- Statistical model (no odds available): 11 matches, log loss 0.8955, accuracy 72.7%
Accuracy over recent evaluation runs
Verify it yourself
No API key, no signup. This is the same JSON this page is built from, so anything above can be checked against it.
Shell
curl -s https://api.predictiqpro.com/status/accuracy
Python
import requests
r = requests.get("https://api.predictiqpro.com/status/accuracy", timeout=20).json()
print("matches scored :", r["n_matches_evaluated"])
print("log loss :", r["log_loss"])
print("brier score :", r["brier_score"])
mc = r.get("market_comparison")
if mc:
print("market log loss:", mc["market_log_loss"])
print("edge vs market :", mc["log_loss_edge_vs_market"]) # negative = behind
# Worst calibration gap among bins with enough matches
gaps = [
(abs(b["predicted_avg"] - b["actual_rate"]), side, b["bin"], b["n"])
for side, bins in r["calibration"].items()
for b in bins if b["n"] >= 30
]
print("largest gap :", max(gaps) if gaps else "n/a")/status/accuracy/history for every evaluation run, and /status/matchday for the forecast frozen about an hour before kickoff.What this does and does not show
It does show
- Whether our probabilities are calibrated: what we call 60% happens about 60% of the time.
- How we score against bookmaker consensus on identical matches.
- A record that grows daily and is published whether it flatters us or not.
It does not claim
- That the model beats the market. Our own testing says it does not, and we say so.
- That accuracy predicts betting profit. This is football data, not betting advice.
- That small gaps mean anything: every figure has a sample size and a margin of error.
How to read each number
- Log loss and Brier score: penalise confident forecasts that turn out wrong. Lower is better, and both are scored on the same matches as the market.
- Calibration: the gap between the probability we gave and how often the outcome happened.
- Accuracy: 49.3% of finished matches went the way we rated most likely (95% range 48–51%). It ignores confidence, so the three above matter more.
Disagreement simulation
A back-test, not a promise and not evidence of an edge: one unit staked on every match where our forecast beat the market’s by at least 3 points, at the market’s average odds. A result near zero is what our own testing predicts. It ignores stake limits, odds movement and margins.
Simulated bets
1,219
Win rate
36.8%
Units staked
1219
Simulated return
-6.9%
before real-world costs
Build on probabilities you can audit
The same probabilities, expected goals and goals markets behind these numbers are available through a REST API and an MCP server for AI agents. 14-day trial, card required, nothing charged until it ends. Cancel before then and you pay nothing.