RoundTrace VAL API
Terms Reviewer guide

Checking live service

Player-authorized VALORANT stats.

RoundTrace helps players review their own match history and gives developers a consent-aware API. Personal statistics are available only after the player links their Riot account.

Review the product flow Inspect live endpoints

Public production-key prototype. Riot Sign On becomes functional after Riot issues the approved RSO client.

Live request pending 
GET /api/compliance

{
  "playerStats": "opt-in-only",
  "officialApisOnly": true,
  "productionMocks": false
}
DeploymentCloudflare Worker
Product phasePublic prototype
Player dataOpt-in only
RSOAwaiting approval

The intended player journey.

Riot reviewers can inspect every stage without creating an account. The production connection button activates only after Riot provides the approved RSO client.

  1. 1.0

    Connect through Riot

    The player selects Connect Riot Account and authenticates on Riot's domain. RoundTrace never receives the player's Riot password.

    RSO
  2. 2.0

    Give informed consent

    Before statistics become public to authorized clients, the player sees what data is collected, how it is used, and how to revoke access.

    Opt in
  3. 3.0

    Build reflective statistics

    RoundTrace uses supported Riot match and content APIs to calculate historical performance such as K/D, ACS, agent usage, map results, and recent form.

    Official APIs
  4. 4.0

    Share under player control

    The player's dashboard and authorized RoundTrace API clients may display the opted-in data. Revoking consent stops future access and starts deletion.

    Revoke anytime
Open the complete reviewer walkthrough

What RoundTrace will do.

  • Require Riot Sign On before displaying identifiable player statistics.
  • Use supported Riot account, match, content, leaderboard, and status APIs.
  • Transform match history into useful retrospective statistics.
  • Give players clear consent, revocation, access, and deletion controls.
  • Keep Riot credentials server-side and issue separate RoundTrace developer keys.

What RoundTrace will not do.

  • No arbitrary player lookup or opponent scouting.
  • No unofficial MMR or ELO calculation.
  • No private game-client or undocumented Riot endpoints.
  • No real-time advice that changes play during a match.
  • No production endpoint that returns fabricated player data.

The player dashboard, before data.

This is an interface-only prototype: dashes show where official match-derived values appear after opt-in. No sample player or fabricated API response is used.

Illustrative interface Connected player Riot ID appears after RSO
Matches
—
Win rate
—
K/D
—
Average combat score
—
No linked player

After Riot approval, connect an account to populate this view from official match history.

Test the live service.

These public operational endpoints are real and require no reviewer account. Personal-data endpoints remain disabled until production approval and RSO integration.

GET

Response

GET /health

Ready 
Select "Send request" to call RoundTrace.

Public endpoints.

The explorer is generated from the same OpenAPI document available to reviewers and tooling.