AFL model inputs: odds, movement and comparison context
Intro: AFL betting models need current and historical market prices to compare fair estimates against bookmaker odds.
What data you need: match winner, line, totals, bookmaker IDs, timestamps and if available opening and closing prices.
How the API works: pull AFL odds through REST/JSON, feed prices into your model, then compare model probability against implied probability.
Code concept: convert decimal odds to implied probability, compare with your fair probability and log the edge and closing-line movement.
AU bookmaker coverage note: AFL liquidity sits with local bookmakers, so Australian coverage is more important than generic global sport depth.
Responsible gambling note: model outputs are uncertain and should be displayed with risk controls and no guarantees.
- AFL odds
- Implied probability
- Model input
- Market movement
- Free key
Example API calls
# Racing — its own endpoint family, NOT a sport_key
curl "https://api.puntersedge.online/v1/racing/next-to-go?categories=horse&num_races=5" \
-H "X-API-Key: YOUR_API_KEY"
# Sports — best price per outcome across the books quoting it
curl "https://api.puntersedge.online/v1/best-odds/nrl" \
-H "X-API-Key: YOUR_API_KEY"
curl "https://api.puntersedge.online/v1/racing/next-to-go?num_races=5" \
-H "X-API-Key: YOUR_API_KEY"