Games, coverage & sources
The platform's compliance spine: what data exists per game, and exactly where it may come from. Connectors run only with a recorded documentation/terms review, credentials, and an enabled flag — page sources snapshot everything they read.
Coverage by game
| Game | Matches | Full telemetry | Basic official | Synthetic (demo) | Events stored | Last match |
|---|---|---|---|---|---|---|
| Counter-Strike 2 | 25 | 25 | 0 | 25 | 7,106 | Jul 5, 2026 |
| VALORANT | 11 | 11 | 0 | 11 | 3,431 | Jun 27, 2026 |
| Fortnite | 16 | 16 | 0 | 16 | 1,371 | Jul 7, 2026 |
| Rainbow Six Siege | 41 | 41 | 0 | 41 | 4,053 | Jun 19, 2026 |
| League of Legends | 46 | 46 | 0 | 46 | 7,574 | Jul 2, 2026 |
Source registry
every permitted origin, with authority order and health| Source | Game | Type | Authority | Status | Legal review | Docs |
|---|---|---|---|---|---|---|
Riot Data Dragon (static game data) Champion/item/patch metadata only. Not match data. | LoL | official download | 10 | ok | Jul 16, 2026 | docs ↗ |
League Match API (MATCH-V5 + timeline) Official basic + timeline data. The timeline feeds LoL advanced metrics (GD@14+, OBJ+, VIS). | LoL | official api | 10 | awaiting review | — | docs ↗ |
Riot Account API (ACCOUNT-V1) Identity linking for Riot accounts (LoL + VALORANT). | shared | official api | 10 | awaiting review | — | docs ↗ |
VALORANT Match API (VAL-MATCH-V1) Player-consented ladder matches only. Never used to fabricate pro-match coverage. | VAL | official api | 10 | awaiting review | — | docs ↗ |
VALORANT Content API (VAL-CONTENT-V1) Official static game data for VALORANT entity pages. | VAL | official api | 10 | awaiting review | — | docs ↗ |
Steam Web API (player identity) Identity resolution for player-linked Steam accounts only. No scraping of Steam community pages. | CS2 | official api | 10 | awaiting review | — | docs ↗ |
LoL Esports official schedule/results pages Placeholder registry entry so pro-match coverage gaps are visible in the admin UI with the correct remediation path. | LoL | official web page | 20 | awaiting review | — | — |
Rainbow Six Esports official match/standings pages Official esports pages only. Never community stat sites. | R6 | official match page | 20 | awaiting review | — | docs ↗ |
Fortnite official competitive event pages/leaderboards Official competitive leaderboards only; parser flags schema drift and quarantines on layout change. | FN | official leaderboard | 20 | awaiting review | — | docs ↗ |
Tournament partner demo/export feed (CS2) Organizer-supplied demos and result exports under contract. | CS2 | authorized partner export | 40 | awaiting review | — | — |
CS2 demo upload (authorized) Primary CS2 advanced-data path. One parse yields both conventional stats and telemetry — never re-fetch basics from unofficial APIs. | CS2 | authorized user upload | 70 | ok | Jul 16, 2026 | — |
R6 match replay / recording upload (authorized) Feeds the R6 baseline pipeline; observer recordings preferred for pro matches. | R6 | authorized user upload | 70 | ok | Jul 16, 2026 | — |
VALORANT recording upload (authorized) Feeds the VALORANT vision baseline; all values carry vision confidence and go through review under thresholds. | VAL | authorized user upload | 70 | ok | Jul 16, 2026 | — |
Fortnite replay/recording upload (authorized) Feeds the Fortnite baseline pipeline; values carry extraction confidence. | FN | authorized user upload | 70 | ok | Jul 16, 2026 | — |
Administrator manual import (CSV/JSON) Fallback for any data without a permitted automated source. Full provenance recorded per import. | shared | manual import | 80 | ok | Jul 16, 2026 | — |
Derived metrics engine All model outputs carry this source; never displayed as official. | shared | derived metric | 110 | ok | Jul 16, 2026 | — |
Synthetic demonstration fixtures Demo/development corpus only. Fictional teams and players; never presented as real esports history. | shared | manual import | 120 | ok | Jul 16, 2026 | — |
What we never do
- No unofficial statistics APIs or community stat sites as data dependencies (no HLTV, VLR, Tracker.gg, Liquipedia, Oracle's Elixir feeds).
- No undocumented or reverse-engineered publisher endpoints; no rate-limit or anti-bot circumvention.
- No game-client memory reading, process injection, or anti-cheat interference.
- No scraping behind authentication; page sources require a recorded terms/robots review before they can run.
- No synthetic data presented as real esports history — demo rows are labeled and bulk-removable.