People Data Labs

Install corsair and @corsair-dev/pdl, add the People Data Labs plugin, and connect with an API key. Then call methods like corsair.pdl.api.autocomplete.suggest() from your app. Corsair syncs data per tenant.

Yes. People Data Labs requires an API key from your People Data Labs account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit People Data Labs, GitHub, Notion, Stripe, and the rest. Trigger People Data Labs from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for b2b person and company data - enrichment, dataset search, identity resolution, ip lookups and cleaners from people data labs. Common builds include sync jobs, admin tooling, and agents that call People Data Labs APIs from your backend. Local DB entities let you query synced People Data Labs records without hitting the API on every read.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per People Data Labs API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/pdl in the open repo. When People Data Labs ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your People Data Labs data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store People Data Labs data on your behalf.