Skip to content
eStatcast

Preview data

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

Data coverage by game
GameMatchesFull telemetryBasic officialSynthetic (demo)Events storedLast match
Counter-Strike 225250257,894Jul 9, 2026
VALORANT11110116,349Jul 5, 2026
Fortnite16160165,661Jul 16, 2026
Rainbow Six Siege41041415,200Jul 9, 2026
League of Legends460464624,109Jul 6, 2026

Source registry

every permitted origin, with authority order and health
Source registry
SourceGameTypeAuthorityStatusLegal reviewDocs
Steam Web API (player identity)
Identity resolution for player-linked Steam accounts only. No scraping of Steam community pages.
CS2official api10awaiting reviewdocs ↗
Riot Data Dragon (LoL static assets)
LoL static game assets only: champion, item, rune, summoner-spell and profile-icon metadata plus their asset URLs, pinned to a patch version with the fetch timestamp recorded on every bundle. Explicitly NOT an identity source — Data Dragon contains no professional players, teams, rosters or esports results, and a profile icon is a ladder-account decoration, never a pro player's portrait. Anything reaching for a player photo must go to the identity pipeline, not here.
LoLofficial download10awaiting reviewdocs ↗
Riot Data Dragon (static game data)
Champion/item/patch metadata only. Not match data.
LoLofficial download10okJul 16, 2026docs ↗
VALORANT Content API (VAL-CONTENT-V1)
Official static game data for VALORANT entity pages.
VALofficial api10awaiting reviewdocs ↗
Riot Account API (ACCOUNT-V1)
Identity linking for Riot accounts (LoL + VALORANT).
sharedofficial api10awaiting reviewdocs ↗
League Match API (MATCH-V5 + timeline)
Official basic + timeline data. The timeline feeds LoL advanced metrics (GD@14+, OBJ+, VIS).
LoLofficial api10awaiting reviewdocs ↗
VALORANT Match API (VAL-MATCH-V1)
Player-consented ladder matches only. Never used to fabricate pro-match coverage.
VALofficial api10awaiting reviewdocs ↗
Rainbow Six Esports official match/standings pages
Official esports pages only. Never community stat sites.
R6official match page20awaiting reviewdocs ↗
Fortnite official competitive event pages/leaderboards
Official competitive leaderboards only; parser flags schema drift and quarantines on layout change.
FNofficial leaderboard20awaiting reviewdocs ↗
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.
LoLofficial web page20awaiting review
GRID esports data platform (CS2 official telemetry)
Boundary for a future official CS2 telemetry path via GRID Open Access or a licensed tier. Ships with no fetch implementation on purpose: nothing is fabricated to stand in for a feed we cannot call, so CS2 telemetry coverage stays honestly empty until access exists. Its value today is making that gap visible in the admin registry with the correct remediation path.
CS2authorized partner export30awaiting reviewdocs ↗
FACEIT Data API v4 (CS2 competitions)
Public FACEIT competition data for CS2 only: championships, matches, factions and rosters, results, and the match statistics FACEIT itself exposes, plus references to demo resources. Authoritative for FACEIT-run competitions; for events FACEIT merely hosts qualifiers or mirrors of, it is a relay and must not override the organizer. Demo files are referenced, never fetched: the Downloads API boundary is implemented but hard-disabled, so a demo URL is recorded as a resource reference and nothing downloads it. Token is server-side only.
CS2official esports api40awaiting reviewdocs ↗
Tournament partner demo/export feed (CS2)
Organizer-supplied demos and result exports under contract.
CS2authorized partner export40awaiting review
PandaScore licensed esports reference data
Licensed reference data: leagues, series, tournaments, matches, maps, teams, players, rosters, results and image URLs for the three pilot titles. Reference layer only — carries no positional telemetry at any tier, and never overrides an organizer export or a publisher API. Token is server-side only.
sharedauthorized partner export45awaiting reviewdocs ↗
VALORANT recording upload (authorized)
Feeds the VALORANT vision baseline; all values carry vision confidence and go through review under thresholds.
VALauthorized user upload70okJul 16, 2026
R6 match replay / recording upload (authorized)
Feeds the R6 baseline pipeline; observer recordings preferred for pro matches.
R6authorized user upload70okJul 16, 2026
CS2 demo upload (authorized)
Primary CS2 advanced-data path. One parse yields both conventional stats and telemetry — never re-fetch basics from unofficial APIs.
CS2authorized user upload70okJul 16, 2026
Fortnite replay/recording upload (authorized)
Feeds the Fortnite baseline pipeline; values carry extraction confidence.
FNauthorized user upload70okJul 16, 2026
Administrator manual import (CSV/JSON)
Fallback for any data without a permitted automated source. Full provenance recorded per import.
sharedmanual import80okJul 16, 2026
Liquipedia API (approved access)
Community-maintained wiki content read through Liquipedia's approved API — tournament metadata, rosters and transfers that fill gaps official sources leave. Lowest authority in the registry. Every displayed value must carry CC-BY-SA attribution and a link back to its source page. HTML scraping is prohibited: the adapter rejects any non-API URL.
sharedauthorized partner export90awaiting reviewdocs ↗
Derived metrics engine
All model outputs carry this source; never displayed as official.
sharedderived metric110okJul 16, 2026
Synthetic demonstration fixtures
Demo/development corpus only. Fictional teams and players; never presented as real esports history.
sharedmanual import120okJul 16, 2026

What we never do

  • No scraped community stat sites as data dependencies (no HLTV, VLR, Tracker.gg, Oracle's Elixir feeds). A community source may be used only through an approved, terms-bound API with its licence and attribution recorded.
  • 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.