For Agents
An agent can query esports leagues, tournaments, matches, teams, players, standings, and live scores across many videogames, pull game-specific metadata such as champions, items, and maps, and poll change or incident endpoints to keep a local dataset in sync.
PandaScore is a cross-title esports data provider covering many videogames from one bearer-authenticated read API, rather than a single-game feed. It pairs match, team, player, and tournament data with videogame-specific metadata and change tracking for incremental sync.
Use for: Reading professional esports data (leagues, tournaments, matches, teams, players, standings, live scores) and videogame metadata across multiple competitive titles
Not supported: in-game player data, ranked ladder data, writing or editing data, real-time push streaming, game publisher endpoints
Credentials: Both APIs authenticate with the same PandaScore bearer token sent in the Authorization header, so one credential covers all endpoints across both variants.
All 2 PandaScore OpenAPI specs are vendor-official and indexed by Jentic, kept validated and agent-ready.
PandaScore provides esports data across major competitive videogames including League of Legends, Dota 2, CS:GO, Valorant, and Overwatch. Its APIs cover leagues, series, tournaments, matches, teams, players, standings, and live scores, along with videogame-specific metadata like champions, items, and maps. Change and incident tracking endpoints let applications keep local data synchronized. All access is read-only over a shared bearer token, structured around a Leagues to Series to Tournaments to Matches hierarchy.
2 APIs across 1 product group. All share one credential.
| I want to... | Use | Why |
|---|---|---|
| Videogame-specific metadata such as champions, items, maps, and abilities | PandaScore REST API for All Videogames | The 56-endpoint variant exposes per-game endpoints like /lol/champions, /dota2/items, and /csgo/maps alongside the core match and team data. |
| A streamlined interface for core esports data with incident-based change tracking | PandaScore API | The 34-endpoint variant focuses on leagues, matches, players, teams, and tournaments with a single /incidents endpoint for tracking additions, changes, and deletions. |
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PandaScore APIs, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpandascore.co" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpandascore.co" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Once connected, ask your agent something like: “get esports matches and team data”.
Each workflow spans multiple PandaScore APIs. Jentic routes each operation to the right API automatically.
Match app with per-game reference data
Combine the two variants to build an esports app that shows matches and rosters alongside game metadata. The pandascore variant lists leagues, matches, teams, and players, while the main variant supplies videogame-specific details like champions, items, and maps to enrich each match view.
Call the pandascore variant GET /matches to list upcoming games, then call the main variant GET /lol/champions to attach champion metadata to each League of Legends match.
PandaScore API + PandaScore REST API for All Videogames
Cross-variant esports data sync
Keep a local esports database current by using change and incident tracking from both variants. The pandascore variant exposes an /incidents endpoint for additions, changes, and deletions, while the main variant offers /changes and /additions with a since timestamp for incremental updates.
Poll the pandascore variant GET /incidents and the main variant GET /changes?since={timestamp} on a schedule, then apply the returned deltas to the local store.
PandaScore API + PandaScore REST API for All Videogames
What agents get from Jentic-routed access to this vendor.
Setup
Wiring PandaScore by hand means handling bearer-token auth against api.pandascore.co, shaping filter and pagination parameters, and building your own retry and error handling for both API variants. With Jentic you install Jentic One once, add the PandaScore APIs from the Jentic directory, store the token once, and your agent calls any endpoint.
Permission scoping
Because you run Jentic One yourself, your own rules decide which PandaScore operations and credentials the agent may use. Both APIs are read-only, so you can restrict the agent to just the read calls it needs, such as listing matches, teams, or champions, and nothing beyond that is available unless you add it.
Credential isolation
Your single PandaScore token is stored encrypted by your own Jentic One instance and injected as the Authorization header at execution time across both API variants. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search the Jentic directory by intent such as 'get League of Legends matches' or 'list CS:GO maps', and Jentic returns the matching PandaScore operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Specific to using PandaScore APIs through Jentic.
What can I build with PandaScore across its APIs?
You can build live scoreboards, esports calendars, tournament bracket and standings displays, team and player profile pages, and analytics dashboards. Both API variants draw from the same esports dataset, so you can mix match, team, tournament, and videogame metadata as needed.
How many videogames does PandaScore cover?
PandaScore covers 13 or more major competitive titles including League of Legends, Dota 2, CS:GO, Valorant, Overwatch, Rainbow Six Siege, and Rocket League. Each title has dedicated endpoints, and the main variant adds per-game metadata like champions, items, and maps.
What is the difference between the two PandaScore APIs?
The main variant has 56 endpoints and adds videogame-specific metadata such as champions, items, maps, and abilities. The pandascore variant has 34 endpoints with a streamlined interface for leagues, matches, teams, players, and tournaments plus a single incidents endpoint for change tracking. Both use the same base URL and token.
Do both APIs use the same credential?
Yes. Both variants authenticate with the same PandaScore bearer token against api.pandascore.co, so a single token works across every endpoint in both APIs.
Can I keep my own data synchronized with PandaScore?
Yes. The pandascore variant provides an incidents endpoint that returns additions, changes, and deletions, and the main variant provides changes and additions endpoints filtered by a since timestamp. Polling these lets you run incremental sync without full data refreshes.
Does PandaScore provide in-game or ranked ladder data?
No. PandaScore focuses on professional esports competition data such as tournaments, matches, teams, players, and standings. Live in-game player telemetry and ranked ladder standings come from the game publishers rather than PandaScore.
All 3 are in the Jentic catalogue with the same one-credential, intent-search pattern.
BOOK A DEMO
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.