People Data Labs: 5 reads, one client
Company and person enrichment and search, plus IP-to-company identification. Free tier: 100 company enrichments a month. Every call below is available over HTTP, through the SDK and as a tool for a coding agent, with the same arguments and the same meter.
What People Data Labs can do here
The integration exposes 5 reads, each with a declared input and output schema rather than a page of documentation you would have to translate. Company and person enrichment and search, plus IP-to-company identification. Free tier: 100 company enrichments a month.
How it authenticates
People Data Labs authenticates with a apiKey, supplied per request or stored once against your account and sealed at rest. On our side the same value is read from apiKey when we broker the call for you.
Capabilities it fulfils
People Data Labs answers business.enrich in the vendor-neutral form, which means code asking for that capability can be pointed at People Data Labs without naming it. If it goes down, or you would rather use somebody else, that is a preference change and not a rewrite.
- companyEnrich — read: Everything PDL believes about one company. The connection test.
- companySearch — read: Find companies by structured or Elasticsearch-style query.
- personEnrich — read: 🔴 PERSONAL DATA. A person's profile from an email, name or profile URL. Read the file header before wiring it: server-side only, and subject to data subject rights regardless of the vendor's terms.
- ipEnrich — read: Identify the company behind an IP address — visitor de-anonymisation.
- jobTitleEnrich — read: Normalise a job title into levels, functions and similar titles.
Questions
Do I have to bring my own API keys?
You can, and that lane is free for ever — pass your key on the request or store it against your account, and we are one proxy hop. The paid lane is the other direction: we call 226 providers with our credentials so you never register anywhere. Both go through the same client and the same operation names.
What happens to a key I store here?
It is sealed with AES-256-GCM before it reaches the database and is only ever opened to make the call you asked for. It is scoped to your account, it is never logged, and deleting the connection deletes it. For an OAuth provider we hold a refresh token instead, and revoking the link at the provider stops the calls here immediately.
What happens when a provider changes its API?
The operation contract is declared, so a response that no longer matches is a refusal rather than a silently wrong answer. The contract does not coerce types — a field declared a number that arrives as a string is rejected at the edge, on the way in and on the way out.