Home · Use cases · Jobs · Check a person's claims before you hire or partner

Check a person's claims before you hire or partner

For: recruiting-research, partnerships and due-diligence teams who need to know whether what someone says about themselves holds up. One run is 2 calls and 60 credits.

Get an API key   Run a step free

The job

A CV or a pitch is a list of claims. You want to know which ones hold against public records, which could not be checked, and what the person's employer, education and history look like, without reading a dozen pages per name.

Web data or web intelligence?

Pages are made for a person reading one profile. Structured answers give a verdict with one sentence on it, each claim and what was found for it, a list of what was not checked, and then a profile with employer, education, a fact check and a list of what could not be confirmed, as fields you can store beside the candidate.

The calls, in order

StepCallWhat it gives youCreditsDocs
1POST /v1/vet_personthe claims: a verdict, a sentence on it, each claim and finding, and what was not checked30Fields
2POST /v1/get_dossierthe profile: employer, education, employment history, a fact check and what could not be confirmed30Fields

What one run costs

fact The credits per call are the catalog's: 30 + 30 = 60 per run, so 60,000 credits per 1,000 runs. calculated At the plan prices on the pricing page that is about $478 per 1,000 runs on Production and $588 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/vet_person

The input: {"name":"Patrick Collison","company":"Stripe"}. A real response had these fields.

FieldValue in that response
oktrue
subjectan object with 5 fields
verdictpartially_verified
verdict_sentence(text, not shown here)
claimsa list of 2
findingsa list of 2
curl -X POST 'https://api.foxapis.com/v1/vet_person' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"Patrick Collison","company":"Stripe"}'

Step 2: POST /v1/get_dossier

The input: {"name":"Patrick Collison","company":"Stripe"}. A real response had these fields.

FieldValue in that response
emailsa list of 5
employerStripe
educationa list of 3
full_namePatrick Collison
fact_checkan object with 5 fields
enriched_at2026-11-19T23:08:49.270Z
curl -X POST 'https://api.foxapis.com/v1/get_dossier' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"Patrick Collison","company":"Stripe"}'

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/vet_person", {"name":"Patrick Collison","company":"Stripe"});   // the claims: a verdict, a sentence on it, each claim and finding, and what was not checked
const step2 = await call("POST", "/v1/get_dossier", {"name":"Patrick Collison","company":"Stripe"});   // the profile: employer, education, employment history, a fact check and what could not be confirmed
console.log({ step1, step2 });

What you could build

Limits, plainly

One person per call, named with a company so the right person is found; a request that finds too little to say answers with nothing and is not charged. Both calls take longer than a plain lookup, so they answer after a short wait. A confidence figure in the profile is an estimate, not a verification, and this is research from public records, not a screening report. Tested on one well-known person on 19 November 2026.

Field lists and the rest of each data type: Every people and company research 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 · 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 · 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