Public datasets
Narrow, outdated, often single-title hobby drops. Fine for a Kaggle notebook. Untenable for a production model.
Six titles. Multi-year history. Billions of structured events. All rights-cleared for commercial AI training and live inference - the foundation your model legal team can sign off on.
{
"event": "PLAYER_DIED",
"game_time": 142.318,
"round": 14,
"map": "de_inferno",
"actor": { "id": "s1mple", "team": "NAVI" },
"weapon": "awp",
"headshot": true,
"economy": { "ct_eq": 22400, "t_eq": 14250 },
"win_prob_at_event": 0.71,
"source": "official_game_server",
"license": "commercial_ai_ok"
}Narrow, outdated, often single-title hobby drops. Fine for a Kaggle notebook. Untenable for a production model.
Lossy, unofficial, and legally exposed for commercial use. Schema breaks every time a game patches.
A multi-year engineering project. New title, new pipeline. Coverage gaps you'll find in production.
So the question is - what does it actually take to train models that ship?
Captured directly from the game server, under rights agreements with the publishers and tournament organisers who own the data. One schema. Every covered title. Licensed for commercial AI.
Six flagship titles. Years of history. Live, real-time events on top.
Rights-cleared for commercial AI training and live inference. The dataset your legal team will actually approve - and your model can ship on.
A single, versioned data model across every covered title. No per-title cleaning, no per-update breakage, no schema drift mid-training run.
Player events, economy state, positional data, objectives. The feature richness models need - not just box scores.
Hit any match, any event window. Good for offline training, evaluation, and on-demand inference.
Sub-200ms live match state for real-time inference, agents, copilots, and live decisioning.
Multi-year archives delivered as Parquet, JSON, or CSV. Built for training pipelines and warehouses.
Point-in-time match state for backtesting and reproducibility. Run the same eval on the same state every time.
Forecast match, map, and round outcomes from live game state - for markets, content, or engagement.
Predict KDA, contribution, form, and matchup effects across players, teams, and series.
Sharpen pricing, settlement, and risk models on the same official data settlement is run against.
Build esports-aware assistants, fan chatbots, content generators, and broadcast copilots on live data.
Train and validate vision models against ground-truth official data - events, positions, outcomes.
Identify match-fixing patterns, behavioural outliers, and integrity flags at population scale.
Yes. The commercial tier grants rights for training and live inference, including for production AI products. For non-commercial research or student projects, get in touch about the right terms.
Six flagship titles - League of Legends, VALORANT, Counter-Strike 2, Dota 2, Tom Clancy’s Rainbow Six Siege, and Mobile Legends: Bang Bang - normalised into one consistent schema. New titles ship through the same data model.
230k+ official matches in the historical archive across covered titles, with 5+ years of structured history. Roughly 1.27M structured events per match on average.
REST for on-demand pulls, WebSocket for live streaming, bulk exports (Parquet, JSON, CSV) for training pipelines, and point-in-time snapshots for reproducible backtesting.
GRID maintains a stable, versioned schema across game updates. Breaking changes are flagged ahead of time with a version bump and migration notes - so a mid-training game patch doesn't break your pipeline.
Tell us about your project and the GRID team will scope the right access, from research and prototyping through to production. Get in touch to start.
Whether you're training a production model, building an esports-aware agent, or running live inference - let's talk about what you're building.