People Data Labs
People Data Labs matches a person to a record in its own dataset and charges per match. A FoxAPIs enrich_person call resolves one person from a name and a company and shows how it checked the identity. It returns far fewer fields than People Data Labs, and this page says so row by row. The price comparison is computed further down from the numbers each side publishes.
Read 22 November 20265 sources linkedPOST /v1/enrich_personWhere FoxAPIs wins
- You want to see why a match was accepted and which same-name people were set aside, not only a likelihood number.
- You want news about the person and profile links across several places in the same call.
- You want to start with welcome credits and pay per call from credits that do not expire, without a monthly minimum.
Where People Data Labs wins
- You need the wide record: job title levels, location, skills, inferred salary, birth year and the many company fields; this call returns almost none of them.
- You want a match against a large stored dataset (it describes nearly three billion profiles) rather than a live lookup of one person.
- You want a likelihood score on a database match rather than a live identity check.
Who People Data Labs is for
Teams that need a large, structured person record (job title levels, location, skills, salary estimates) from an API, and pay for matches in volume.
What People Data Labs lists
People Data Labs is a data company with a Person Enrichment API. Facts below are what its pricing and documentation pages showed on 22 November 2026.
- The person pricing page lists Free at $0 a month with up to 100 records a month, Pro "starting at $98 / mo" with "starting at 350 records / mo", and Enterprise at custom pricing. PDL person pricingread 22 November 2026
- That page lists no per-record price. The per-record figure below is our own division of the two Pro numbers. PDL person pricingread 22 November 2026
- The Person Enrichment overview says it performs a one-to-one match of a person with nearly three billion individual profiles in its dataset. PDL Person Enrichment overviewread 22 November 2026
- The reference page says it charges per match, and takes name, company, email, a profile address and other inputs to a request at https://api.peopledatalabs.com/v5/person/enrich. PDL Person Enrichment referenceread 22 November 2026
- The response carries a status, a likelihood from 1 to 10 that the profile is the person you asked for, and a data object; fields with no data are null. PDL output responseread 22 November 2026
| Plan | Listed price | Includes |
|---|---|---|
| Free | Free | Up to 100 records a month |
| Pro | $98 a month, starting | Starting at 350 records a month |
| Enterprise | custom pricing | Custom volume |
Read on 22 November 2026 from People Data Labs's page. We state only what the pages we link showed that day.
How the two differ
People Data Labs returns a stored record from a very large dataset, with many fields and a likelihood. A FoxAPIs call looks the person up live, confirms what it can, and returns less in each place but adds the identity check and recent news. The price per record against the price per call is worked out in the price block below.
Field by field: People Data Labs' documented person fields against ours
We lose rows here. 29 of the 50 People Data Labs fields have no field of ours. Where a row says we do not return it, we do not.
The reference lists the person record fields; which come back depends on the plan's field bundle. We compare names, as listed.
| People Data Labs field | Ours | What we return (real sample, 19 November 2026) |
|---|---|---|
| full_name | We return it | full_name: Same data, our field name. |
| first_name | Closest field | full_name: One field for the whole name; we do not split it. |
| last_name | Closest field | full_name: One field for the whole name; we do not split it. |
| middle_name | We do not return it | We do not return this. |
| name_aliases | We do not return it | We do not return this. |
| emails | Closest field | emails: Candidates, each labelled by how we came by it; none in the sample was confirmed by delivery. |
| work_email | Closest field | emails: One list; we do not mark which is a work address. |
| personal_emails | We do not return it | We do not separate personal addresses. |
| phone_numbers | Closest field | phones: A list; we do not label a number as mobile. |
| mobile_phone | Closest field | phones: A list; we do not label a number as mobile. |
| job_title | We return it | title: Same data, our field name. |
| job_company_name | We return it | employer: Same data, our field name. |
| job_company_website | We do not return it | We do not return this. |
| job_company_size | We do not return it | We do not return this. |
| job_company_industry | We do not return it | We do not return this. |
| job_start_date | Closest field | employment_history: The start date of the current job sits inside the entry that is marked current. |
| job_title_levels | We do not return it | We do not return a seniority level. |
| job_title_role | We do not return it | We do not return this. |
| job_title_sub_role | We do not return it | We do not return this. |
| inferred_salary | We do not return it | We do not return a salary estimate. |
| birth_date | We do not return it | We do not return this. |
| birth_year | We do not return it | We do not return this. |
| sex | We do not return it | We do not return this. |
| languages | We do not return it | We do not return this. |
| location_names | We do not return it | We do not return a location. |
| location_country | We do not return it | We do not return this. |
| location_locality | We do not return it | We do not return this. |
| street_addresses | We do not return it | We do not return this. |
| education | We return it | education: Same data, our field name. |
| experience | Closest field | employment_history: Title, company and dates for each job; no job summary. |
| job_history | Closest field | employment_history |
| skills | We do not return it | We do not return this. |
| interests | We do not return it | We do not return this. |
| headline | We do not return it | We do not return this. |
| summary | We do not return it | We do not return this. |
| certifications | We do not return it | We do not return this. |
| linkedin_url | We return it | linkedin_url: Same data, our field name. |
| linkedin_username | We do not return it | We do not return this. |
| linkedin_connections | We do not return it | We do not return this. |
| github_url | We return it | github_url: Same data, our field name. |
| github_username | We return it | github_username: Same data, our field name. |
| twitter_url | We return it | twitter_url: Same data, our field name. |
| twitter_username | We do not return it | We return a twitter_handle; see the closest field. |
| facebook_url | We do not return it | We do not return this. |
| profiles | Closest field | linkedin_url: We return each profile link as its own field: linkedin_url, twitter_url, github_url, instagram_url, youtube_url and others. |
| likelihood | Closest field | overall_confidence: A 0 to 1 score for the match, with identity_verification giving the reasons. |
| num_sources | Closest field | source_count |
| profile_score | We do not return it | We do not return this. |
| activity_score | We do not return it | We do not return this. |
| possible_profiles | Closest field | possibly_someone_else: Different thing: same-name people we set aside, not extra possible profiles of this person. |
Ours only: identity_verification (why the match was accepted), news_mentions, photo_url, crunchbase_url and other links, deeper_dossier.
Source for the People Data Labs column: PDL field reference, read 22 November 2026.
What a FoxAPIs call returns
POST /v1/enrich_person
Give it a name and a company. It resolves the person and returns confirmed profile links, employment and education history, email candidates each labelled by how we came by them, phone numbers, recent news about the person, and an identity check that says why the match was accepted and which same-name people were set aside. Costs 100 credits a call.
| Field | Real example (19 November 2026) |
|---|---|
| full_name | Patrick Collison |
| employer | Stripe |
| title | none |
| overall_confidence | 0.45 |
| linkedin_url | (text, not shown here) |
| twitter_url | none |
| github_url | none |
| photo_url | none |
| emails | a list of 5 |
| phones | none |
| employment_history | a list of 2 |
| education | a list of 3 |
| news_mentions | a list of 8 |
| identity_verification | an object with 16 fields |
| possibly_someone_else | a list of 4 |
curl -X POST https://api.foxapis.com/v1/enrich_person \
-H "Authorization: Bearer YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"name":"Satya Nadella","company":"Microsoft"}'Price at the costliest listed tier
| People Data Labs or FoxAPIs | Price |
|---|---|
| Pro, the entry paid tier | $98 a month for 350 records is about $0.280 a record (our division of the two numbers the page lists; it states no per-record price). source |
| FoxAPIs /v1/enrich_person | $0.980 a call: 100 credits a call times the price per credit on the Builder plan, calculated by us. The welcome credits cover about 10 calls, no card. |
Plainly: at this tier People Data Labs costs less per record than a FoxAPIs call does. We return fewer fields; what we add is the identity check and recent news.
Dollar figures for FoxAPIs are computed from plans.json when this page is built; none is typed. We show a dollar figure for People Data Labs only where its own pages gave the numbers.
Start with 1,000 credits
Start with 1,000 credits, no card. They arrive once you confirm your email and expire 90 days after they are added; credits you buy never expire. Then from $10. Type your email and the key appears on this page, once, with the request below filled in.
By continuing you agree to the Terms and the Privacy page.
Key created. It is shown once: copy it now.
Move one call
Before: People Data Labs request, from its reference page
curl -G https://api.peopledatalabs.com/v5/person/enrich \ --data-urlencode "api_key=YOUR_PDL_KEY" \ --data-urlencode "name=Satya Nadella" \ --data-urlencode "company=Microsoft"
After: the same job on FoxAPIs. Replace YOUR_KEY with the key from the box above.
curl -X POST https://api.foxapis.com/v1/enrich_person \
-H "Authorization: Bearer YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"name":"Satya Nadella","company":"Microsoft"}'Same two inputs, name and company. The response is a different shape; use the table above to map fields.
Questions before you switch
Is a FoxAPIs call cheaper than People Data Labs?
Compare the two figures in the price block above. People Data Labs' is our division of the two numbers on its pricing page; ours is credits per call times the price per credit on our smallest paid plan, calculated when the page is built. Read both before you decide.
Does People Data Labs charge for a no-match?
Its reference page says it charges per match. It does not state in so many words that a no-match is free, so check before you rely on it.
Where do the extra fields go?
We do not return them. Location, skills, salary estimates, seniority level, company details and birth data are rows in the table above marked as not returned.
Are the emails verified?
No. They are candidates, each labelled by how we came by them. None in our sample was confirmed by delivery.
When to stay with People Data Labs
- You need the wide record: job title levels, location, skills, inferred salary, birth year and the many company fields; this call returns almost none of them.
- You want a match against a large stored dataset (it describes nearly three billion profiles) rather than a live lookup of one person.
- You want a likelihood score on a database match rather than a live identity check.
When a FoxAPIs call is the better fit
- You want to see why a match was accepted and which same-name people were set aside, not only a likelihood number.
- You want news about the person and profile links across several places in the same call.
- You want to start with welcome credits and pay per call from credits that do not expire, without a monthly minimum.