canonical: https://jentic.com/apis/callofduty.com/callofduty # Call of Duty API The Call of Duty API exposes player-facing game data: gamer profiles, match history, career and mode statistics, loadouts, and friend and identity information across titles and platforms. It reads player accounts and detailed match records for companion apps and stat trackers. Requests authenticate with a session cookie named ACT_SSO_COOKIE. ## For AI agents Read Call of Duty player profiles, match history, career statistics, loadouts, and friend information across titles and platforms. ## Scope Does not handle matchmaking, in-game purchases, or account modification - use for reading player profiles, matches, and statistics only. ## Capabilities - Retrieve a player's profile and career statistics for a title - Fetch detailed match history for a gamer and mode - Look up a player's loadouts across titles and platforms - Resolve gamer identities and linked platform accounts - Read friend and account information for a player ## Use cases ### Player stat tracking A companion app needs a player's career and mode statistics. The Call of Duty API reads a gamer's profile and stats for a title and platform so a stat tracker can display performance over time. Example prompt: Fetch a gamer's profile and career statistics for a title and platform and render a stats page ### Match history analysis An analytics tool needs recent match details for a player. The match operations return detailed records for a gamer and mode so a backend can compute trends and highlights. Example prompt: Retrieve detailed match records for a gamer and mode and summarize recent performance ### Loadout and identity lookup A community site needs a player's loadouts and linked accounts. The loadout and identity operations return a gamer's configurations and platform links so profiles can be shown across platforms. Example prompt: Look up a gamer's loadouts and resolve their linked platform identities for a profile page ### AI agent game data lookup An AI agent building a gaming assistant can pull player data without hand-wiring the session cookie. Through Jentic the agent discovers the read operations by intent and calls them with the stored credential. Example prompt: Search Jentic for 'get a player's Call of Duty stats', load the schema, and fetch a gamer's profile ## Key resources - **Profiles and stats** — Read player profiles and career or mode statistics for a title - **Matches** — Fetch detailed match history for a gamer and mode - **Loadouts** — Look up a player's loadouts across titles and platforms - **Identities** — Resolve gamer identities and linked platform accounts ## 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:** 61 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 48 / 100 - Developer Experience & Jentic Compatibility: 71 / 100 - AI-Readiness & Agent Experience: 55 / 100 - Agent Usability: 90 / 100 - Security: 50 / 100 - AI Discoverability: 64 / 100 - **View full report:** https://jentic.com/apis/callofduty.com/callofduty/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 Call of Duty API by hand means carrying the ACT_SSO_COOKIE session cookie on every request and shaping the title, platform, and gamer path parameters yourself. Through Jentic you install once, import the API from the API Directory, store your credential once, and your agent calls it. - **Permission scoping:** The Call of Duty API addresses gamers, titles, and platforms by value in the URL path, so you can limit the agent to the read operations it needs, such as fetching a profile or match history. You credit the agent only with the operations you allow, so anything you have not granted stays out unless you add it. - **Credential handling:** Your the Call of Duty credential 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. - **Discovery method:** Agents search Jentic by intent such as 'get a player's Call of Duty stats', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing docs. ## Related APIs - **PUBG API** — Player stats and match data for PUBG - **OpenDota API** — Match and player statistics for Dota 2 - **Steam Web API** — Steam player profiles and ownership data ## FAQ ### What authentication does the Call of Duty API use? The Call of Duty API authenticates with a session cookie named ACT_SSO_COOKIE obtained from a signed-in account. Through Jentic the cookie value is stored encrypted in your own instance and applied to each request at run time. ### Is there a the Call of Duty API MCP server? You don't need an MCP server to give your agent the Call of Duty API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it. That keeps another server's tool definitions out of your agent's context while still giving it the operation set from the spec. ### What player data does the Call of Duty API expose? It reads gamer profiles, career and mode statistics, detailed match history, loadouts, and friend and identity information across titles and platforms, for companion apps and stat trackers. ### Can I limit what my agent is allowed to do with the Call of Duty API? Yes. Because you run Jentic One yourself, your own rules decide which the Call of Duty API operations and credentials the agent may use. You grant only the operations it needs, such as reading a player's stats, so any write operation you have not granted stays off limits unless you add it. The choice of what the agent may call is yours. ### How do I connect my agent to the Call of Duty API through Jentic? Search Jentic by intent such as 'get a player's Call of Duty stats' to discover the operation, load its input schema, and your agent calls it with your stored credential injected at run time. To run it on your own infrastructure, install Jentic One from its GitHub repo.