3 APIs across 3 product groups. All share one credential.
| I want to... | Use | Why |
|---|---|---|
| Read Clash of Clans clan, war, and player data | Clash of Clans API | Covers clans, war logs, war leagues, leagues, locations, and player profiles for Clash of Clans. |
| Read Clash Royale clan, tournament, and player data | Clash Royale API | Adds tournaments, cards, and river race logs alongside clan and player lookups specific to Clash Royale. |
| Read Brawl Stars player, club, and brawler data | Brawl Stars API | Uses clubs instead of clans and exposes brawler rankings and lists unique to Brawl Stars. |
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Supercell 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%2Fsupercell.com" | 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%2Fsupercell.com" | 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.
What agents get from Jentic-routed access to this vendor.
Setup
Wiring these APIs by hand means handling a separate bearer token for each game against three different base hosts and managing retries yourself. With Jentic One installed, your agent finds and adds any of the Supercell APIs from the Jentic directory, and you store each token once.
Permission scoping
Every operation across the three APIs is a read, and player and clan tags sit in the URL path, so your own rules in your Jentic One instance can pin the agent to specific games, clans, or players and let it fetch nothing else.
Credential isolation
Each game's bearer token is stored encrypted by your own Jentic One instance and injected only at execution time, so raw tokens never enter the agent's prompt, logs, or context.
Specific to using Supercell APIs through Jentic.
Which games does the Supercell portfolio cover?
The portfolio covers three official game data APIs: Clash of Clans, Clash Royale, and Brawl Stars. Each exposes read-only access to that game's players, clans or clubs, and competitive data.
Can one credential access all three Supercell APIs?
No. Each game issues its own bearer token from its developer portal, so an agent needs a separate token for Clash of Clans, Clash Royale, and Brawl Stars. The tokens are not interchangeable.
Can agents change game state through these APIs?
No. Every operation across the three APIs is a read. Agents can fetch player, clan, war, and ranking data but cannot modify accounts, join clans, or affect matchmaking.
How consistent are the APIs across the three games?
The APIs share a common shape: player tags and clan tags are the primary keys, responses are JSON, and access uses a bearer token. Brawl Stars uses clubs where the others use clans, and each game adds resources specific to it such as tournaments, cards, or brawlers.
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.
For Agents
An agent can look up player profiles, clan and club information, member lists, war and battle logs, and country rankings across Clash of Clans, Clash Royale, and Brawl Stars. All operations are reads, so agents fetch and compare competitive game data without changing anything in the games.
Supercell is the only source of official, first-party game data for Clash of Clans, Clash Royale, and Brawl Stars, with player and clan tags used consistently as the primary keys across all three APIs. This lets an agent track the same style of player, clan, and war data across three separate games using one uniform bearer-token access pattern.
Use for: Reading live player, clan, club, war, ranking, and card data across Clash of Clans, Clash Royale, and Brawl Stars.
Not supported: writing game data, payments, player messaging, matchmaking control, real-time streaming
Credentials: Each API uses its own bearer token issued from that game's developer portal, so one credential does not cover all three APIs; an agent needs a separate token per game.
Across 3 Supercell APIs: 2 vendor-official, 1 third-party, all indexed by Jentic and kept validated and agent-ready.
Supercell publishes official game data APIs for its mobile titles Clash of Clans, Clash Royale, and Brawl Stars. Each API exposes read-only access to player profiles, clans and clubs, war logs, rankings, and card or brawler data, secured with a bearer token. Together they let developers and agents pull live competitive game data across Supercell's three flagship games from a single portfolio.
Once connected, ask your agent something like: “get player and clan data across Supercell games”.
Each workflow spans multiple Supercell APIs. Jentic routes each operation to the right API automatically.
Cross-game player profile lookup
Pull a player's profile from more than one Supercell game by their player tag to build a combined view of their competitive activity across titles.
Call GET /players/{playerTag} on Clash of Clans and GET /players/{playerTag} on Clash Royale, then merge the two profiles into one summary.
Clash of Clans API + Clash Royale API
Multi-game clan and club standings
Compare a community's competitive standings across games by reading clan rankings from one title and club rankings from another for the same country.
Call GET /rankings/{countryCode}/clubs on Brawl Stars and the clan ranking endpoint on Clash Royale, then rank the results side by side.
Clash Royale API + Brawl Stars API
Unified war and battle activity report
Assemble a report of a group's recent competitive activity by reading clan war logs from Clash of Clans and player battle logs from Brawl Stars.
Call GET /clans/{clanTag}/warlog on Clash of Clans and GET /players/{playerTag}/battlelog on Brawl Stars, then combine both into an activity timeline.
Clash of Clans API + Brawl Stars API
Intent-based discovery
An agent searches the Jentic directory by intent such as 'get clan information' or 'read a player battle log', and Jentic returns the matching Supercell operation with its input schema so the agent calls the right endpoint across the right game without reading reference docs.
What kind of data can an agent combine across the games?
An agent can pull the same player or community across titles, compare clan and club rankings by country, and merge war logs and battle logs into a single activity report, since the three APIs share tags and response structures.
Are these the official Supercell APIs?
The Clash of Clans and Brawl Stars specs are vendor-official, and the Clash Royale spec is sourced from a third party. All three describe Supercell's own public game data endpoints.
All 3 are in the Jentic catalogue with the same one-credential, intent-search pattern.