Leaguepedia API alternative: REST, not Cargo.
Leaguepedia is the reference wiki for pro League of Legends, but its API is Cargo: SQL-like queries over wiki tables, anonymous rate limits, and a bot password once you need volume. The same questions as one REST call each: league history and champions, schedules, results, rosters and team records.
- No Cargo query syntax
- No bot password
- 500 free requests / month
{ "success": true, "data": [ { "tournamentId": "lol-lck_split_2_2026", "name": "Split 2 2026", "startDate": "2026-03-31", "winner": { "orgSlug": "hle", "teamName": "Hanwha Life Esports" } }, { "tournamentId": "lol-lck_split_1_2026", "name": "LCK Cup 2026", "startDate": "2026-01-13", "winner": { "orgSlug": "gen", "teamName": "Gen.G Esports" } }, ... ]}Seamless Integration with our MCP Server
Give Claude, Cursor and ChatGPT the League of Legends esports data. One command writes the MCP config; agents call live match, team, player and schedule tools with real ids instead of guessing them, and your key stays on your machine.
MCPInstall the Cito MCP serverThe wiki's tables, as endpoints
What people query Cargo for, already joined.
League history
Every split and tournament of a league with its dates and winner.
Schedules
Upcoming, live and past matches per league and team.
Results
Series and game results with the winner and side.
Rosters
Current rosters and roster history per team.
Team records
Win rates, side splits and head-to-head.
Stable ids
Match, game, team and player ids you can store and join, no page titles.
Cargo table to endpoint
| Leaguepedia (Cargo) | Endpoint |
|---|---|
| Tournaments / TournamentResults | GET /lol/leagues/{league}/history |
| MatchSchedule | GET /lol/leagues/{league}/matches/upcoming |
| ScoreboardGames | GET /lol/matches/{matchId}/games |
| TournamentPlayers / Players | GET /lol/teams/{slug}/roster |
| RosterChanges | GET /lol/teams/{slug}/roster/history |
When Leaguepedia is still the right tool
Leaguepedia covers more history and more obscure leagues than any API, and its editors are fast. For deep historical research it is the reference.
For an app, a bot or a model that needs the same data every day, a REST API with stable ids and a known rate limit is less work than maintaining Cargo queries.
FAQs
Leaguepedia, Cargo and the API
Can't find what you're looking for? Contact our customer support team
More LoL esports APIs
Every page names the endpoint behind it.
- LoL wiki APIWiki-style league, team and player data as REST.
- gol.gg API alternativegol.gg's data as a REST API.
- LoL esports historical dataEvery completed series since 2023 for models.
- LoL team stats APIWin rates, side splits and head-to-head per team.
- League of Legends APIThe whole LoL esports API on one page.
- PandaScore LoL alternativeA self-serve LoL API with a free key.
Query league history
Swap a Cargo query for one REST call on a free key.