Home › Public Data
BoxBoxF1Fantasy Public Data (2026)
A crawlable index of public JSON files for agents, answer engines and power users who want to understand the data behind the site.
| File | Dataset | Description | Updated | Bytes |
|---|---|---|---|---|
| predictions.json | Current F1 Fantasy predictions | Current-round driver and constructor projections, expected points, confidence ranges, prices, value scores and prediction metadata. | 2026-07-09 | 33,533 |
| season_summary.json | Season summary | Race calendar, completed-round flags, current prices and season-level driver/constructor context used by the site. | 2026-07-09 | 11,906 |
| driver_history.json | Driver and constructor history | Historical fantasy scores and price movement used by season views, form tables and value context. | 2026-07-09 | 39,304 |
| track_data.json | Track data | Circuit metadata and track-classification features for current and future race-week context. | 2026-07-09 | 7,949 |
| weather.json | Weather forecast | Race-week weather forecast metadata used by the weather widget and weather-aware prediction notes. | 2026-07-11 | 8,584 |
| horizon_projections.json | Future-round horizon projections | Forward-looking projections used by the multi-week transfer planner when planning beyond the current race. | 2026-07-09 | 54,074 |
| changelog.json | Changelog | Machine-readable release notes for notable model, scoring, data and tool changes. | 2026-07-10 | 42,329 |
| articles.json | Articles | Machine-readable source for crawlable race previews, recaps and F1 Fantasy strategy articles. | 2026-04-28 | 21,514 |
| youtube_videos.json | YouTube videos | Latest BoxBoxF1Fantasy YouTube videos with title, publish date, thumbnail and URL. | 2026-07-10 | 1,433 |
FAQ
Can agents use these JSON files?
Yes. These are public static JSON files used by the website itself. They can be fetched directly for current projections, season context, articles, videos and other public site data.
Are these predictions guaranteed?
No. The data contains model-based projections and public site metadata. F1 Fantasy outcomes depend on weather, reliability, strategy, penalties and race incidents.
Which endpoint should an AI assistant read first?
Start with predictions.json for the current round and season_summary.json for calendar and price context. Use llms.txt or llms-full.txt for a plain-English site map.