Riot Games API review package

Chatrix VALORANT integration dossier

Chatrix is a multi-game Twitch chat companion browser extension. The current public version supports CS2 through FACEIT. This page demonstrates the planned VALORANT integration for Riot Games API review.

Live: CS2 through FACEIT Next: VALORANT through Riot APIs Model: RSO and opt-in only
Reviewer access Public page, no account, no Discord, no app download required.
Production rule No live VALORANT player data until Riot API approval.
Consent boundary Users link with RSO before any public VALORANT display.

For Riot reviewers

This page is intentionally public and account-free. It lets a reviewer verify the planned product behavior, the consent model, and the deployment/legal surfaces without installing the browser extension.

Product URL

https://chatrix.it.com/valorant

Dedicated review surface for the VALORANT integration.

Current status

CS2/FACEIT live

VALORANT is planned next and shown here with mock data only.

Player data

Opt-in only

No VALORANT data appears unless the user links through RSO and enables visibility.

Verification

/riot.txt ready

The domain can serve Riot's verification string as exact text after submission.

Reviewer access

No account wall

Riot can review the planned flow without creating an account or joining a community server.

Production behavior

Approval gated

Chatrix will not make live VALORANT API calls or display live VALORANT player data before approval.

Proposed player experience

Four mock screens show how the extension would move from game selection to Riot linking, explicit public visibility, and chat display. All names and ranks are placeholder data.

screen 1

Choose your game

Chatrix keeps each game integration separate.

CS2FACEIT rank in Twitch chatlive
VALORANTRiot RSO and opted-in badgesplanned
League of LegendsSeparate future applicationlater
screen 2

Connect Riot account

RSO is required before any VALORANT player data is available.

Link with Riot Sign On
Chatrix will not auto-match Twitch usernames to Riot accounts. Users must link their own Riot account.
Public visibility
screen 3

Visibility control

Public display starts disabled.

By linking your Riot account and enabling public VALORANT visibility, selected VALORANT profile and gameplay data may become visible to other Chatrix users. You can disable visibility or request deletion at any time.
Public VALORANT badge
Enable public badge
screen 4

Twitch chat preview

Mock data - no live Riot API data.

VALOptedInViewer
Ascendant 2 - EU
VALLinkedStreamer
Diamond 3 - NA
PrivateViewer
No badge because no opt-in

Security model

Riot API keys and RSO client secrets stay behind the Chatrix backend. The extension displays approved summaries and never ships Riot credentials to browser-exposed code.

Extension -> Chatrix backend -> Riot APIs

Browser extension

Reads visible Twitch usernames and displays badges for opted-in accounts only.

no Riot secrets

Chatrix backend

Owns RSO exchange, consent state, visibility checks, and allowed Riot API requests.

secrets stay here

Riot APIs

Used after approval for identity, opted-in match/profile summaries, content, status, and leaderboard data.

approved endpoints only

Data lifecycle

The production path is designed around explicit consent, narrow display, and reversibility.

1

Link

User starts Riot Sign On from Chatrix.

2

Consent

User enables public VALORANT visibility separately from linking.

3

Fetch

Backend requests only approved Riot API data needed for the selected display.

4

Display

Extension shows compact Twitch chat badges for opted-in users only.

5

Disable

User can turn visibility off or request deletion through the public contact channel.

Compliance commitments

We do

  • Use Riot Sign On for VALORANT account linking.
  • Ask for explicit public visibility opt-in.
  • Show selected VALORANT summaries only for opted-in users.
  • Let users disable visibility or request deletion.
  • Keep Riot API keys and RSO secrets backend-only.

We do not

  • Show VALORANT stats for users who have not opted in.
  • Auto-identify Twitch usernames as Riot accounts.
  • No scouting or opponent pre-match analysis.
  • Create real-time in-game overlays.
  • Calculate hidden MMR, ELO, or unofficial rankings.
  • Create alternate reporting/player evaluation tools.
  • Sell paid or exclusive access to VALORANT player data.
  • Claim Riot partnership, sponsorship, approval, or endorsement.

Policy boundary map

The VALORANT module is intentionally scoped to community-friendly Twitch chat identity and opted-in self-expression, not competitive intelligence.

Allowed use
  • Player-controlled account linking.
  • Opted-in Twitch chat badge display.
  • Riot-provided public content metadata.
Blocked use
  • Non-consenting player lookup.
  • Hidden skill estimates or unofficial ranking systems.
  • Negative labels, shaming, or report alternatives.
Deferred use
  • League of Legends and other games will be submitted as separate product applications.
  • No shared Riot production key will run multiple game products.
  • Any gray-area feature will be asked about in App Notes first.

Intended API usage

The production implementation will use only Riot-documented VALORANT APIs and only for users who opt in where player data is involved.

  • Riot Sign On/account identity for explicit account linking.
  • VAL-MATCH-V1 for opted-in profile and match-summary display where permitted.
  • VAL-CONTENT-V1 for Riot-provided VALORANT content metadata such as agents, maps, queues, and localized names.
  • VAL-STATUS-V1 for platform and service status where relevant.
  • VAL-RANKED-V1 only for Riot-provided public leaderboard information where applicable.