Arrr, riot API transparency

Arrr, measured requests, visible safeguards

VRC.LOL keeps Riot credentials on th' harbour, spaces requests deliberately, reads Riot's live limit headers and stops a collection pass afore an observed bucket be exhausted.

Arrr, public Riot data remains disabled Private prototype only while Riot reviews th' Production API application.

Arrr, riot rate-limit documentation Privacy aboard boundary

Arrr, registered productPending Inspect

Product: Arrr, VRC.LOL League Tools
Arrr, app ID: 860951
Arrr, public lookup: Disabled
Arrr, research publication: Disabled

This be a status disclosure, nay a claim o' Riot approval. Private credentials and th' Developer Relations support request be nay published here.

0.8 / secondSpacing

54 / courseArrr, pass cap

80%Headroom

DisabledArrr, public Riot data

Arrr, riot's limit model

Arrr, three limits can apply at once

A successful response can carry application and method counts. A 429 response identifies th' exhausted scope through Riot's rate-limit type header.

Application

Shared across th' product fer one routing value. The collector checks th' returned application count after every Riot request.

Method

Specific endpoints can have their own bucket. Method counts receive th' same 80% headroom protection.

Service

Riot services can enforce additional limits. A 429 be ne'er treated as permission to keep trying immediately.

Arrr, implemented controls

Arrr, what the collector does today

These be present harbour behaviours, nay planned promises.

Arrr, one process

Arrr, a filesystem lock prevents overlapping scheduled collectors.

Arrr, regional passes stay separate

Americas and Europe run sequentially. Their seed pools and request counters be ne'er blended.

Requests be paced

Arrr, at least 1.25 seconds separates Riot API calls, limiting this collector to about 0.8 requests per second.

Arrr, every pass has a hard cap

A regional pass can issue no more booty than 54 Riot requests, even when more booty work be awaiting.

Headers decide th' remaining headroom

The collector reads application and method limits and counts. At 80% utilisation it ends th' pass cleanly.

Arrr, 429 means stop and wait

The collector honours Riot's Retry-After value. Retries are bounded, recorded and never used to bypass a bucket.

Arrr, request budget

Arrr, documented limits versus our prototype

Th' Developer Portal and response headers be th' source o' truth. VRC.LOL does nay assume a Production allowance afore approval.

Scope	Arrr, short window	Arrr, long window	Arrr, VRC.LOL behaviour
Arrr, development / personal baseline	20 Arrr, requests / 1 second	100 Arrr, requests / 120 seconds	Arrr, read from Riot headers at runtime
Arrr, private VRC.LOL collector	0.8 Arrr, requests / second maximum cadence	54 Arrr, requests / regional pass	Stops at 80% o' any observed bucket
Arrr, production starting allowance	500 Arrr, requests / 10 seconds	30,000 Arrr, requests / 10 minutes	Nay assumed or enabled afore approval

Riot may assign different application, method or service limits. Th' values returned in response headers override assumptions made from a general documentation tale.

Battle integrity

Th' loadout freezes when play begins

Th' sailor keeps control o' every decision. Live clash facts ne'er become automatic coaching.

Allowed afore play

Visible completed picks can prepare several matchup and gear choices. Th' sailor selects th' course afore th' clash starts.

Arrr, allowed during play

Th' Companion may keep that static course visible, mark gear already owned, and reveal factual ship's intelligence already visible in Riot's client.

Sailor-picked reference

Th' sailor may manually open a general problem such as healing or magic damage and compare multiple static options. Th' app does nay pick an captain's answer.

Ne'er automatic

Live KDA, doubloons, levels, inventory and prizes cannae reorder a loadout, promote an gear, choose a target, rank a threat, trigger coaching audio or calculate a claim victory chance.

Arrr, hidden stays hidden

A lost overboard champion-pick identity remains "Sailor nay visible". Th' Companion does nay resolve it through a cell ID, PUUID, summoner endpoint, a previous draft cache or an external service. Lost overboard display data be treated as private even when another identifier be present.

Nay battle actions

Th' Companion cannae pick, ban, trade, lock, move, cast, ping, purchase or otherwise control League fer th' sailor.

Arrr, feature-by-feature audit

A competitor's feature list be evidence, nay transferable permission

Riot requires products and material feature changes to be registered and audited individually. VRC.LOL describes only behavior that be implemented in its present loadout.

Present: local recognition

Th' Companion detects th' signed-in local League client and its phase without sending th' lockfile credential, Riot ID or shipshape local response to VRC.LOL.

Present: static preparation

Champion pick can prepare queue-, role- and matchup-aware loadout, rune and skill references. Th' chosen course freezes when active play begins.

Present: visible facts

Th' overlay can reveal factual state already exposed to th' sailor and mark inventory ownership. It does nay turn that state into an automatic decision.

Arrr, proposed: confirmed rune application

A future champion-pick action may preview, confirm and apply a rune chart or summoner-spell pair. It remains disabled while th' present read-only product description be under inspect.

Needs separate inspect

Live tier comparisons, inferred total-gear doubloons differences, healing-gear detection and other changing-clash analysis require a documented source and an audited user flow afore VRC.LOL can claim or ship them.

Arrr, excluded: cooldown sharing

VRC.LOL will nay provide automatic or manual tracking o' foe ultimate or spell cooldowns that be nay already available through regular gameplay. Riot's League policy gives foe ultimate tracking as a prohibited tale.

OP.GG publicly advertises several capabilities. That demonstrates its own service behavior; it does nay disclose th' approval articles, data contracts or exceptions Riot may have audited fer that product.

Arrr, product boundary

Private research be nay public API access

Th' site separates prototype collection, public features and local Companion behaviour.

Credentials stay harbour-side

Riot API keys be held in private harbour configuration. They be nay embedded in HTML, JavaScript, th' Windows Companion, downloads or URLs.

Arrr, evidence stays private

Collected Clash-v5 evidence be nay published while th' Production API application be pending.

Reuse afore requesting

Deduplication, seen-clash markers, queue separation and caching prevent unnecessary repeat calls.

Th' Companion has no Riot key

Th' invited desktop preview reads permitted local client ship's intelligence on that PC and does nay proxy a development key to testers.

Completed-clash verification be private

When a tester explicitly enables it, th' Companion submits a Clash ID and one-way participant proof after play. Clash-v5 replaces provisional facts, identities be discarded, and unverified records ne'er enter public pages or aggregate evidence.

Arrr, anonymous live contract

Th' optional live feed rejects sailor names, Riot IDs, PUUIDs, sailor record IDs, cell IDs and unknown fields. Fresh uploads be signed, replay protected, rate limited and ne'er accepted from spectator mode.

Arrr, explicit lookup only

A visitor may scan th' horizon a Riot ID they already know. VRC.LOL does nay offer reverse lookup from PUUIDs, concealed draft slots or internal sailor record identifiers, and those identifiers be removed from browser responses.

Nay a data broker

VRC.LOL does nay resell raw Riot data, expose Riot API access, or act as an API relay fer another company. Ship's intelligence be transformed into end-user lookup and learning features.

Permitted battle assets

Champion, gear and other battle-specific static artwork comes from Riot-supported sources such as Data Dragon or permitted Riot materials.

Registration stays present

Material endpoints, client integrations and product features be recorded in th' Developer Portal. Features can remain private or paused while Riot inspect be pending.

Arrr, one key, one product

A Production key be reserved fer its registered VRC.LOL League Tools product and be nay shared wit' unrelated products.

Arrr, required notice

Arrr, independent from Riot Games

This notice be also displayed on th' League homepage and in th' Articles o' use.

VRC.LOL League Tools be nay endorsed by Riot Games and does nay reflect th' views or opinions o' Riot Games or anyone officially involved in producing or managing Riot Games properties. Riot Games and all associated properties be trademarks or registered trademarks o' Riot Games, Inc.

Arrr, primary sources

Inspect th' Riot documentation directly

This chart summarises implementation choices. Riot's present policies, portal records and returned headers always take priority.

Developer Portal chartArrr, rate-limit types, response headers and 429 handling Arrr, League of Legends API policyArrr, registration, key security and approved product use Arrr, general policiesArrr, requirements that apply to every Riot API product Riot API ArticlesTh' binding articles that apply alongside th' policy summaries