Home · Use cases · Jobs · Profile a creator before a sponsorship

Profile a creator before a sponsorship

For: brand, agency and partnerships teams who vet a video creator or streamer before they pay for a placement. One run is 2 calls and 4 credits.

Get an API key   Run a step free

The job

Before you sponsor a creator you want the basics in one place: how big the channel is, what it says about itself, whether it is verified, when the account started and whether the streamer is live and a partner. Today that is several tabs per creator.

Web data or web intelligence?

Channel pages are made to be watched. Structured answers give you a video channel's name, description, keywords and verification flag, and a streaming channel's display name, partner level, account creation date and follower count, as fields you can score and store.

The calls, in order

StepCallWhat it gives youCreditsDocs
1POST /v1/content/youtube/channelthe video channel: name, description, keywords, verification, channel identifier2Fields
2POST /v1/social/twitch/channelthe streaming channel: display name, partner level, account created, followers2Fields

What one run costs

fact The credits per call are the catalog's: 2 + 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/content/youtube/channel

The input: {"url":"https://www.youtube.com/@YouTube"}. A real response had these fields.

FieldValue in that response
channel_nameYouTube
keywordsyoutube official channel
channel_idUCBR8-60-B28hp2BmDPdntcQ
thumbnailhttps://yt3.googleusercontent.com/LaXtRHwowjJqq8TZcqGx-QDFcFax_vz-5...
curl -X POST 'https://api.foxapis.com/v1/content/youtube/channel' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://www.youtube.com/@YouTube"}'

Step 2: POST /v1/social/twitch/channel

The input: {"channel":"twitch"}. A real response had these fields.

FieldValue in that response
logintwitch
display_nameTwitch
broadcaster_typepartner
account_created2007-05-22T10:39:54Z
total_views0
followers2,506,487
curl -X POST 'https://api.foxapis.com/v1/social/twitch/channel' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"channel":"twitch"}'

All of it as one script

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

// 2 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/content/youtube/channel", {"url":"https://www.youtube.com/@YouTube"});   // the video channel: name, description, keywords, verification, channel identifier
const step2 = await call("POST", "/v1/social/twitch/channel", {"channel":"twitch"});   // the streaming channel: display name, partner level, account created, followers
console.log({ step1, step2 });

What you could build

Limits, plainly

One channel per call. Some figures, such as subscriber counts, can be hidden by the creator and then come back empty; the page shows only fields that held a value in our test on 19 November 2026.

Field lists and the rest of each data type: Every social and creator 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 · Analyse players and games for a gaming community · 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 · 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