Home · Use cases · Jobs · Analyse players and games for a gaming community

Analyse players and games for a gaming community

For: game studios, esports organisations and community managers who follow players and titles. One run is 3 calls and 4 credits.

Get an API key   Run a step free

The job

Seeding a leaderboard, scouting a streamer or pricing a store page means collecting a player's title, ratings and followers, and a game's developer and price.

Web data or web intelligence?

Raw profile and store pages differ on every site and change often. Structured answers give you a player's title, country, followers and rating per time control on two chess platforms, and a game's developer, publisher, price and discount, all as fields.

The calls, in order

StepCallWhat it gives youCreditsDocs
1POST /v1/gaming/chess/playera player on one chess platform: title, country, followers, ratings per time control1Call and code
2POST /v1/gaming/lichess/playerthe same player on the other platform: ratings per time control and total games1Fields
3POST /v1/content/steam/gamea game: developer, publisher, price, discount, release date2Call and code

What one run costs

fact The credits per call are the catalog's: 1 + 1 + 2 = 4 per run, so 4,000 credits per 1,000 runs. calculated At the plan prices on the pricing page that is about $31.84 per 1,000 runs on Production and $39.20 on Builder (plan price divided by its monthly credits, times the credits). The Free plan gives 100 credits a month with no card.Formula

Your runs a month

Real responses, step by step

fact Captured from https://api.foxapis.com on 19 November 2026 with the documented sample input of each call; every value below is from that response, shortened where long. The nightly check on the status page lists each of these calls as working.

Step 1: POST /v1/gaming/chess/player

The input: {"username":"hikaru"}. A real response had these fields.

FieldValue in that response
usernamehikaru
titleGM
nameHikaru Nakamura
countryUS
locationFlorida
joined_date2014-01-06
curl -X POST 'https://api.foxapis.com/v1/gaming/chess/player' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"username":"hikaru"}'

Step 2: POST /v1/gaming/lichess/player

The input: {"username":"DrNykterstein"}. A real response had these fields.

FieldValue in that response
usernameDrNykterstein
titleGM
patrontrue
onlinefalse
total_games10,455
total_rated10,440
curl -X POST 'https://api.foxapis.com/v1/gaming/lichess/player' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"username":"DrNykterstein"}'

Step 3: POST /v1/content/steam/game

The input: {"url":"https://store.steampowered.com/app/620/Portal_2/"}. A real response had these fields.

FieldValue in that response
app_id620
titlePortal 2
developerValve
developersValve
publisherValve
publishersValve
curl -X POST 'https://api.foxapis.com/v1/content/steam/game' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://store.steampowered.com/app/620/Portal_2/"}'

All of it as one script

The same 3 calls chained, with a key placeholder. Swap the inputs for your own.

// 3 calls, one job run. Put your key in YOUR_API_KEY.
const KEY = "YOUR_API_KEY", BASE = "https://api.foxapis.com";
async function call(method, path, input) {
  const url = BASE + path + (method === "GET" ? "?" + new URLSearchParams(input) : "");
  const r = await fetch(url, { method, headers: { Authorization: "Bearer " + KEY, "Content-Type": "application/json" }, body: method === "GET" ? undefined : JSON.stringify(input) });
  if (!r.ok) throw new Error(path + " answered " + r.status);
  return r.json();
}
const step1 = await call("POST", "/v1/gaming/chess/player", {"username":"hikaru"});   // a player on one chess platform: title, country, followers, ratings per time control
const step2 = await call("POST", "/v1/gaming/lichess/player", {"username":"DrNykterstein"});   // the same player on the other platform: ratings per time control and total games
const step3 = await call("POST", "/v1/content/steam/game", {"url":"https://store.steampowered.com/app/620/Portal_2/"});   // a game: developer, publisher, price, discount, release date
console.log({ step1, step2, step3 });

What you could build

Limits, plainly

Public profile data only, one player or game per call. We tested one player on each platform and one game on 19 November 2026.

Field lists and the rest of each data type: Every games and music field. Single calls with code in six languages: task APIs.

Other jobs: Track a product's open-source and launch momentum · Build a crypto and DeFi dashboard · Write a biomedical research brief · Watch artists for a label or a playlist curator · Give an AI agent structured answers instead of raw pages · Enrich a lead list with company and developer signals · Check a UK company and who controls it · Compare your app with a rival's on both phone stores · Profile a creator before a sponsorship · Check an open-source model and its repository before you adopt it · Profile a developer expert before you hire or sponsor · Check a person's claims before you hire or partner · Score a candidate against a role you describe · Prepare a sales brief on a company and score a prospect's message · Check how AI assistants show your domain · Research an investor before you pitch.

Source: live calls to https://api.foxapis.com on 19 November 2026. Values reflect that moment and those inputs. Credits per call are the catalog's.

How we calculate

Data: the FoxAPIs catalog and plans, read 19 November 2026. Every other figure on this page is copied from the record, not calculated by us.

Run this free, then pay per call

Free to start: 100 credits, no card. Then from $10. Credits you buy never expire. Use them at your own pace. Get my free key

One call costs 1 credit. That is $7.96 per 1,000 calls on the Production plan and $9.80 on Builder (plan price divided by its monthly credits). The Free plan gives 100 credits a month with no card.

Run this freeBuy credits

Building an AI agent?

See the MCP server