Agent-ready OpenAPI document · curated by JenticAnalyticsBusiness Intelligencebearer13 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Look up PUBG players by name or id, then read their season, ranked, and lifetime stats, weapon and survival mastery, and match details. Also returns leaderboards per season and game mode on each platform shard.
Use for: Find the PUBG account id for player name shroud on steam, Get my lifetime squad-fpp stats in PUBG, Retrieve the ranked stats for this player in the current season, List all seasons on the xbox shard
Not supported: Does not handle game purchases, account management, or other games' stats. Use for reading PUBG: Battlegrounds player, match, and leaderboard data only.
Jentic publishes the only available OpenAPI specification for PUBG API, keeping it validated and agent-ready. The PUBG API returns in-game PUBG: Battlegrounds data for players on the steam, kakao, xbox, psn, stadia, and tournament shards: player lookups, season, ranked, and lifetime stats, match details, weapon and survival mastery, and leaderboards per season and game mode. Responses follow the JSON:API specification, and a sample endpoint returns a random set of recent match ids for bulk analysis.
Install Jentic One Beta
Connect the PUBG API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PUBG 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.
1
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%2Fpubg.com%2Fpubg" | sh2
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%2Fpubg.com%2Fpubg" | 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.
Capabilities
What an agent can do with PUBG API.
Look up up to 10 PUBG players at once by name or account id on a platform shard
Read a player's season, ranked, and lifetime stats, or batch season stats for up to 10 players in one game mode
Fetch a match by id with its rosters
Retrieve weapon mastery and survival mastery progress for a player
Get the leaderboard for a season and game mode such as squad-fpp, paged with page[number]
Pull a sample of recent match ids from a createdAt start time for bulk match analysis
Use Cases
Patterns agents use PUBG API for, with concrete tasks.
★ Agent-built PUBG performance reports
A Discord bot or coaching assistant can resolve a player name to an account id, read the matches list on the player record, fetch each match, and combine that with season and lifetime stats to explain how the player is trending. The PUBG API answers per platform shard, so the agent includes steam, xbox, psn, or kakao in the path to read the right account.
Look up player name shroud on the steam shard with filter[playerNames], then get the current season id and return that player's squad-fpp season stats
Season leaderboards and team scouting
Community sites and esports scouts track the strongest players per mode. The leaderboard operation returns ranked players for a seasonId and gameMode from solo to squad-fpp, and the batch season stats operation pulls stats for up to 10 player ids in one request, so a roster can be compared without a call per player.
Get the leaderboard for the current season with gameMode squad-fpp on steam, then batch fetch season stats for the first 10 player ids
Bulk match sampling for analysis
Analysts studying the meta need many matches, not one player's history. The samples operation returns a random set of recent match ids, optionally from a filter[createdAt-start] time, which a pipeline then expands with the match operation to study placement, kills, and survival across a broad player base.
Fetch match samples on the steam shard from filter[createdAt-start] 2026-11-11T00:00:00Z and retrieve the first five matches by id
Key Endpoints
13 endpoints — jentic publishes the only available openapi specification for pubg api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/shards/{platform}/players
Find players by name or id
GET
/shards/{platform}/players/{playerId}/seasons/{seasonId}
Get player season stats
GET
/shards/{platform}/players/{playerId}/seasons/lifetime
Get player lifetime stats
GET
/shards/{platform}/matches/{matchId}
Get a match
GET
/shards/{platform}/leaderboards/{seasonId}/{gameMode}
Get a leaderboard
GET
/shards/{platform}/players/{playerId}/weapon_mastery
Get weapon mastery
GET
/shards/{platform}/samples
Get match samples
GET
/shards/{platform}/players
Find players by name or id
GET
/shards/{platform}/players/{playerId}/seasons/{seasonId}
Get player season stats
GET
/shards/{platform}/players/{playerId}/seasons/lifetime
Get player lifetime stats
GET
/shards/{platform}/matches/{matchId}
Get a match
GET
/shards/{platform}/leaderboards/{seasonId}/{gameMode}
Get a leaderboard
GET
/shards/{platform}/players/{playerId}/weapon_mastery
Get weapon mastery
GET
/shards/{platform}/samples
Get match samples
Jentic AI Readiness Score
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.
P
PUBG API
- AI-Aware (B-)61/100
75
Foundational Compliance63
Developer Experience & Jentic Compatibility42
AI-Readiness & Agent Experience94
Agent Usability60
Security63
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
75
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
2%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: BSignals: 4
4%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
48%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
42
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D-Signals: 4
20%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
60
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
60%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
63
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: BSignals: 1
63%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the PUBG API by hand means attaching its API key as a Bearer token, parsing its JSON:API responses, and resolving player names to account ids before any stats call. Through Jentic you install once, import PUBG from the API Directory, store the key once, and your agent calls it.
Permission scoping
The PUBG API puts the platform shard and player id in the URL path (/shards/{platform}/players/{playerId}/...), so a rule can pin your agent to one shard or one player account and the operations you pick. The spec contains read operations only, and you choose which lookups the agent may call.
Credential isolation
Your PUBG API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'get PUBG player stats' or 'show the season leaderboard', and Jentic returns the matching PUBG operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using PUBG API through Jentic.
Why is there no official OpenAPI spec for PUBG API?
PUBG documents its API on the PUBG Developer Portal but does not publish a machine-readable OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call the PUBG API via structured tooling. To run it on your own infrastructure, install Jentic One from its GitHub repo.
What authentication does the PUBG API use?
The PUBG API authenticates with an API key sent as a Bearer token in the Authorization header, per its OpenAPI spec. The GET /status check needs no key. Through Jentic the key is stored once and injected at call time, so it never appears in your agent's prompt or logs.
Can I look up several PUBG players in one request?
Yes. GET /shards/{platform}/players accepts comma-separated values in filter[playerNames] or filter[playerIds], up to 10 per request. For stats, GET /shards/{platform}/seasons/{seasonId}/gameMode/{gameMode}/players returns season stats for up to 10 player ids in one game mode.
What are the rate limits for the PUBG API?
The OpenAPI spec defines a rate-limited response but does not state the limit itself. Check the PUBG Developer Portal at https://developer.pubg.com for the limit attached to your API key.
How do I get a player's season stats with the PUBG API through Jentic?
Search Jentic for 'get PUBG player season stats', which returns GET /shards/{platform}/players/{playerId}/seasons/{seasonId} with its input schema. Resolve the player id first with the players lookup and the season id from GET /shards/{platform}/seasons, then call it.
Is there a PUBG MCP server?
You don't need an MCP server to give your agent the PUBG API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it, finding each operation by intent instead of loading a full tool list into its context.
Can I limit what my agent is allowed to do with the PUBG API?
Yes. Write a rule that allows only the season and lifetime stats operations under /shards/steam/players/{playerId}, naming one account id, so a personal stats bot reads that player and nothing else, and every call it makes is logged.
GET STARTED