Install Jentic One Beta

Connect the Wargaming.net API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Wargaming.net API, 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%2Fdevelopers.wargaming.net%2Fwargaming" | sh

Step 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%2Fdevelopers.wargaming.net%2Fwargaming" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Capabilities

What an agent can do with Wargaming.net API.

Search player accounts and read their profile details

List a player's vehicles and per-tank statistics

Browse the vehicle encyclopedia and game reference data

Look up clans and their member rosters

Read player ratings within a rating period

GET STARTED

Start building with Wargaming.net API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Wargaming.net API for, with concrete tasks.

★ AI Agent Player Stats Lookup

An AI agent can answer questions about a World of Tanks player by searching their account and reading their profile and per-tank statistics. Through Jentic the agent finds these read operations by intent and passes the account id, so a Discord bot or stats assistant can report win rates and vehicle performance without a developer wiring the endpoints by hand.

Search for a player by nickname, then read their overall statistics and return win rate and battle count

Clan Roster and Standings Tracker

A community agent can track clans by looking up membership and global map standings. The API returns clan details, member lists, and province holdings, so an agent can report roster changes or a clan's position on the global map as part of a scheduled community update.

Look up a clan by name, list its current members, and report its global map province count

Vehicle Encyclopedia Assistant

A reference agent can answer questions about specific tanks using the vehicle encyclopedia. The API returns vehicle specifications and game reference data, so an agent can compare tanks or explain a vehicle's stats to a player without maintaining its own game database.

Fetch the encyclopedia entry for a named tank and return its tier, type, and key specifications

Key Endpoints

16 endpoints — the wargaming.

METHOD

PATH

DESCRIPTION

GET

/wot/account/list/

Search player accounts

GET

/wot/account/info/

Get player account details

GET

/wot/account/tanks/

List a player's vehicles

GET

/wot/tanks/stats/

Get per-vehicle statistics for a player

GET

/wot/encyclopedia/vehicles/

Get vehicle encyclopedia data

GET

/wot/clans/list/

Search clans

GET

/wot/clans/info/

Get clan details

GET

/wot/ratings/accounts/

Get player ratings

GET

/wot/account/list/

Search player accounts

GET

/wot/account/info/

Get player account details

GET

/wot/account/tanks/

List a player's vehicles

GET

/wot/tanks/stats/

Get per-vehicle statistics for a player

GET

/wot/encyclopedia/vehicles/

Get vehicle encyclopedia data

GET

/wot/clans/list/

Search clans

GET

/wot/clans/info/

Get clan details

GET

/wot/ratings/accounts/

Get player ratings

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Wargaming by hand means registering an application for an id, adding it to every request as a query parameter, and handling an optional player access token for private fields. Through Jentic you install once, import the API, store the credentials once, and your agent calls it.

Permission scoping

You choose which Wargaming operations the agent may call. Since every operation is a read-only lookup, a rule can allow just player statistics, or just clan data, so the agent stays within the exact set of lookups you approved.

Credential isolation

Your Wargaming application id and any player access token are stored encrypted by your own Jentic One instance and injected as query parameters at execution time. They never enter the agent's prompt, logs, or context window.

Intent-based discovery

Agents search Jentic by intent such as 'get a player's statistics' or 'look up a clan', and Jentic returns the matching Wargaming operation with its input schema so the agent calls the right endpoint.

FAQs

Specific to using Wargaming.net API through Jentic.

Is there a World of Tanks MCP server?

You don't need an MCP server to give your agent the Wargaming.net API. Jentic connects it directly from the API Directory: import it, store your application id once, and your agent can read player stats, clans, and encyclopedia data. Operations are discovered on demand, so no extra tool definitions sit in the agent's context.

Can I limit what my agent is allowed to do with the Wargaming.net API?

Yes. Every operation is a read-only lookup, so you write a rule that allows only the ones you need, such as reading player statistics but not clan data. The agent cannot reach any operation you did not pick, and every call it makes is logged.

What authentication does the Wargaming.net API use?

The Wargaming.net API requires an application id, sent as the application_id query parameter per its OpenAPI spec, and it accepts an optional access_token query parameter for data that needs the player's consent. Through Jentic these are stored encrypted by your own Jentic One instance and added at call time.

Can my agent read a player's per-tank statistics with the Wargaming.net API?

Yes. After finding an account, the agent can read the player's overall statistics and their per-vehicle statistics, along with the list of tanks in their garage. This lets a stats assistant report win rates and performance for specific vehicles.

What are the rate limits for the Wargaming.net API?

The OpenAPI spec does not specify rate limits. Check the Wargaming developer documentation at https://developers.wargaming.net for the current per-application request limits before running high-volume lookups.

How do I read World of Tanks player stats through Jentic?

Search Jentic for 'get a World of Tanks player's statistics', import the operation, and store your application id once. Your agent then searches accounts and reads their stats on demand. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Wargaming.net API

Name: Wargaming.net API
Brand: Wargaming
Availability: InStock

Official vendor OpenAPI document · agent-readyMediaContent DeliveryapiKey16 EndpointsREST

For Agents

Read World of Tanks player profiles, per-vehicle statistics, clan rosters, encyclopedia entries, ratings, and global map data through the Wargaming.net API. Read-only game data.

Use for: Find a World of Tanks player by nickname, Get a player's overall and per-tank statistics, List the vehicles in a player's garage, Look up a clan and its members

Not supported: Covers reading World of Tanks player, vehicle, and clan data. Does not modify accounts, handle purchases, or cover other Wargaming titles.

The Wargaming.net API serves player, vehicle, and clan data for World of Tanks. You can search accounts and read a player's profile, vehicles, and per-tank statistics, browse the vehicle encyclopedia, look up clans and their members, and read player ratings and global map standings. Every operation is a read that returns game data.

Jentic One on Github View OpenAPI Document