The model reads a single JSON file (Documentation Index
Fetch the complete documentation index at: https://mintlify.com/ValveSoftware/counter-strike_regional_standings/llms.txt
Use this file to discover all available pages before exploring further.
matchdata.json) containing an array of matches and an array of events. This page documents the expected shape of that file and every field the model reads.
Top-level structure
The file has two top-level keys:matches array contains individual match objects. The events array contains event metadata that matches reference by eventId. Event structure is documented separately in Event data JSON schema.
Match object fields
Each entry in thematches array represents a single match between two teams.
Display name of team 1.
Display name of team 2.
Array of player objects representing team 1’s roster. Exactly 5 players are required; matches with any other count are discarded before ranking runs.
Array of player objects representing team 2’s roster. Exactly 5 players are required; matches with any other count are discarded before ranking runs.
Identifier for team 1. Used to look up prize distribution entries in the event’s
prizeDistribution array. In practice this value is a numeric string (e.g., "11814").Identifier for team 2. Used to look up prize distribution entries in the event’s
prizeDistribution array. In practice this value is a numeric string (e.g., "11555").Indicates which team won:
1 for team 1, 2 for team 2.Unix timestamp in seconds when the match began. Used to apply the time-window filter and the scoring decay ramp.
Reference to the event this match belongs to. Must correspond to an
eventId present in the top-level events array.When
true, the match was a forfeit. The model still processes forfeited matches but treats the roster record as pending until a non-forfeited match is observed for the same players.Whether this match counts toward the official CS2 Regional Standings. Required for all matches with a
matchStartTime on or after 2025-01-01 (Unix timestamp 1735689600).valveRanked is only required for matches played on or after January 1, 2025. Matches before that date are included regardless of whether this field is present.Player object fields
Each entry inteam1Players and team2Players represents a single player.
Unique identifier for the player. Used to determine roster identity — the model compares
playerId values to detect shared players across lineups. In practice this value is a numeric string (e.g., "13290").The player’s in-game nickname or handle.
Two-letter ISO country code for the player’s nationality, in lowercase (e.g.,
"us", "dk", "br"). Used when assigning teams to regions by plurality of player nationalities.