People API Reference

Overview

Company-scoped; requires Authorization: Bearer nv_sk_…. Opt-in: an AccountKit that has never enabled people is refused with 403 subprocessor_consent_required, and one that turned it off with 403 primitive_disabled_by_kit. MCP equivalents (naive_people_*) meet the same gate. Metered on 3× the provider run’s real spend. A no-match is billed too — the run happened — nothing. Send Idempotency-Key on search and enrich: it deduplicates the response and becomes the credit-ledger reference, so a retry cannot be charged twice. See People for the governance boundary — B2B work details only, never for employment, credit, insurance or housing decisions.

Endpoints

Method	Path	Description
POST	`/v1/people/search`	Find people by `title`, `company`, `industry`, `geo`, `seniority` (limit ≤ 50)
POST	`/v1/people/enrich`	Resolve one identity (`linkedin`, or `name` + `company`) into a work profile
POST	`/v1/people/tasks`	Async batch enrich, up to `PRIMITIVE_BATCH_MAX` identities
GET	`/v1/people/tasks/:id`	Batch status and, once complete, the matched records
GET	`/v1/people/terms`	Acceptable-use terms as JSON (unmetered)
POST	`/v1/people/erasure`	Data-subject erasure by `email` or `linkedin` (unmetered)

Notes

email-only and domain-only enrich stay on the request contract but are refused by the current provider rather than answered empty.
phone and match_likelihood are on the response schema and never populated — the first by policy, the second because the provider scores no matches.
With include_contact, email_verification reports what was actually established: valid, invalid, invalid_syntax, no_mail_server, domain_only or unverified. mailbox_verified is true only when a mailbox was probed.

​Overview

​Endpoints

​Notes

Overview

Endpoints

Notes