canonical: https://jentic.com/apis/developers.wargaming.net/wargaming-main # Wargaming.net API Jentic publishes the only available OpenAPI specification for Wargaming.net API, keeping it validated and agent-ready. The Wargaming.net Public API exposes player, vehicle, clan, and Global Map data for World of Tanks, World of Warships, and World of Warplanes. This spec covers 16 endpoints across account lookup, vehicle statistics, encyclopedia data, clan membership, ratings, and Clan Wars provinces - the surface community sites and stat trackers depend on for player profiles and competitive leaderboards. ## For AI agents Look up player profiles, vehicle stats, clan rosters, and Clan Wars Global Map data across Wargaming titles like World of Tanks. ## Scope Does not handle in-game purchases, account creation, or live battle telemetry - use for player, vehicle, clan, and Global Map data reads only. ## Capabilities - Search players by nickname through GET `/wot/account/list`/ and pull profile detail via `/wot/account/info`/ - Retrieve a player's vehicle roster and per-vehicle stats from `/wot/account/tanks`/ and `/wot/tanks/stats`/ - Read the World of Tanks encyclopedia for vehicles, achievements, maps, and meta info under `/wot/encyclopedia`/ - Look up clans and their members with `/wot/clans/list`/, `/wot/clans/info`/, and `/wot/clans/membersinfo`/ - Pull ratings and rating types via `/wot/ratings/types`/ and `/wot/ratings/accounts`/ - Inspect Clan Wars Global Map provinces and clan presence through `/wot/globalmap/provinces`/ and `/wot/globalmap/clans`/ ## Use cases ### Player profile pages on community stat sites Community-run stat sites and overlays use account list and account info to render searchable player profiles with WN8, win rate, battles, and most-played vehicles. The list endpoint maps a nickname to an account_id, then info and tanks/stats produce the full profile. The data is per-region (RU, EU, NA, ASIA) by templating the {region} server variable. Example prompt: Call GET `/wot/account/list`/ for nickname='ExamplePlayer' on region='eu', take the account_id from the first result, then call GET `/wot/account/info`/ to fetch the profile. ### Clan recruitment and roster monitoring Clan officers and recruitment tools poll `/wot/clans/list`/, `/wot/clans/info`/, and `/wot/clans/membersinfo`/ to monitor roster changes, identify recruits matching skill thresholds, and detect when a member leaves. Combined with player ratings via `/wot/ratings/accounts`/ this powers automated recruitment dashboards used by competitive clans. Example prompt: Call GET `/wot/clans/list`/ to find a clan ID, then GET `/wot/clans/membersinfo`/ and join with GET `/wot/ratings/accounts`/ to produce a roster report with skill metrics. ### Clan Wars Global Map intelligence Clan Wars commanders and meta-trackers pull `/wot/globalmap/provinces`/ and `/wot/globalmap/clans`/ to monitor province ownership, prime times, and rival clan movements. Stitched with encyclopedia data this powers strategy dashboards that highlight contested fronts and revenue-rich provinces. Updates happen on the campaign tick, so the data is queried hourly by most consumers. Example prompt: Call GET `/wot/globalmap/clans`/ for the active campaign, then GET `/wot/globalmap/provinces`/ filtered to the rival clan IDs to map their territory. ### AI-agent stats lookups via Jentic AI agents serving Discord communities or Twitch overlays can call Wargaming.net through Jentic without managing application_id query-string injection. Jentic stores the application_id in your Jentic One instance and exposes high-level intents like 'look up a World of Tanks player' so the agent passes a nickname and receives the parsed profile. Example prompt: Search Jentic for 'look up a World of Tanks player', load the schema for GET `/wot/account/list`/, and execute with the nickname from the user message. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/wot/account/list/` | Search players by nickname | | GET | `/wot/account/info/` | Get player profile | | GET | `/wot/account/tanks/` | Get vehicles owned by a player | | GET | `/wot/tanks/stats/` | Get vehicle statistics for a player | | GET | `/wot/encyclopedia/vehicles/` | List encyclopedia vehicles | | GET | `/wot/clans/info/` | Get clan info | | GET | `/wot/clans/membersinfo/` | Get clan member info | | GET | `/wot/globalmap/provinces/` | List Clan Wars Global Map provinces | ## Key resources - **Account** — Search players, fetch profile, and list owned vehicles - **Tanks** — Per-vehicle stats and achievements for a player - **Encyclopedia** — Static reference data for vehicles, achievements, and maps - **Clans** — List, info, and member roster for clans - **Ratings** — Player ratings and the configured rating types - **Clan Wars** — Global Map clans and provinces ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 44 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 72 / 100 - Developer Experience & Jentic Compatibility: 55 / 100 - AI-Readiness & Agent Experience: 44 / 100 - Agent Usability: 94 / 100 - Security: 15 / 100 - AI Discoverability: 64 / 100 - **View full report:** https://jentic.com/apis/developers.wargaming.net/wargaming-main/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the Wargaming.net API by hand means appending your application_id and access_token as query parameters, picking the right regional World of Tanks host, and handling each method's parameters yourself. Through Jentic you install once, import the Wargaming.net API from the API Directory, store the credentials once, and your agent calls it. - **Permission scoping:** You choose which Wargaming operations the agent may call, so you can limit it to the ones it needs, such as looking up a player and listing clan members, and leave the encyclopedia or Global Map reads out unless you add them. Every operation is a data read, so the agent cannot make purchases or create accounts. - **Credential handling:** Your Wargaming application_id and access_token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'look up a World of Tanks player' or 'list a clan's members', and Jentic returns the matching Wargaming operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Riot Games API** — Riot's data API serves League of Legends and Valorant in the same player-and-match shape as Wargaming - **Steam Web API** — Steam Web API provides cross-game player presence and library data that complements per-title stats - **Battle.net API** — Blizzard's Battle.net API exposes Diablo, World of Warcraft, and Hearthstone game data in a similar shape ## FAQ ### Why is there no official OpenAPI spec for Wargaming.net API? Wargaming publishes per-method documentation pages on developers.wargaming.net but not a single OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Wargaming.net API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the Wargaming.net API use? Wargaming uses an application_id query-string parameter for unauthenticated calls and an additional access_token query parameter for authenticated user actions. Through Jentic both values are held in your Jentic One instance and injected per call so the application_id is never embedded in client-side code. ### Can I look up a player by nickname with this API? Yes. GET `/wot/account/list`/ accepts a search parameter and returns matching nicknames with account_ids. Pass the account_id to GET `/wot/account/info`/ to fetch the full profile and to GET `/wot/tanks/stats`/ for per-vehicle stats. ### What are the rate limits for the Wargaming.net API? Wargaming applies a per-application rate limit (commonly 10 requests per second for server-side application_ids) that is not declared in the OpenAPI spec. Standard tier accounts get a daily request quota; consult the application settings on developers.wargaming.net for the live values and build retry-with-backoff. ### How do I look up a World of Tanks player through Jentic? Run pip install jentic, then with the async client search for 'look up a World of Tanks player', load the schema for GET `/wot/account/list`/, and execute with the nickname. Jentic returns the matching account_ids ready to feed into `/wot/account/info/.` ### Does this API cover World of Warships and World of Warplanes? The spec is structured around the World of Tanks /wot/ paths. The same operations exist for World of Warships and World of Warplanes under /wows/ and /wowp/ on the relevant region hosts; future spec versions will add those branches. ### Can I limit what my agent is allowed to do with the Wargaming.net API? Yes. Because Jentic One is self-hosted, you decide which Wargaming operations the agent may call, so you can restrict it to just what it needs, such as looking up a player with `/wot/account/list`/ and `/wot/account/info`/ or listing a clan's members with `/wot/clans/membersinfo`/, and leave the encyclopedia and Clan Wars Global Map reads out unless you add them. Every operation is a data read, so the agent cannot make purchases or create accounts. Your rules govern which endpoints and credentials the agent is permitted to use.