Clearbit Alternative
Contact enrichment
without the subscription.
Clearbit charges a monthly subscription whether you use it or not. PeopleDB charges per lookup — buy credits once, use them whenever. No minimums, no renewals, no waste.
Get 10 free credits →
No card required.
How they compare
| Clearbit | PeopleDB | |
|---|---|---|
| Pricing model | Monthly subscription | Pay per lookup |
| Minimums | Yes | None |
| Credits expire | Yes (monthly reset) | Never |
| LinkedIn lookup | Yes | Yes |
| GitHub lookup | No | Yes |
| Email addresses | Yes | Yes |
| Phone numbers | Yes | Yes |
| Company enrichment | Yes | No |
| IP reveal | Yes | No |
| Free tier | No | 10 free credits |
When PeopleDB makes more sense
You don't need enrichment at scale every month
Clearbit's pricing assumes constant, high-volume usage. If your enrichment is bursty — an outbound campaign, a one-time import, a background job that runs weekly — you're paying for capacity you don't use. Credits let you pay for what you actually run.
You're building on LinkedIn and GitHub identifiers
PeopleDB is built around social identifiers — pass in a LinkedIn public identifier or GitHub login and get back verified contact data. GitHub lookup in particular is uncommon in the enrichment space. If your pipeline starts with a GitHub handle, there aren't many options.
You want a simple, focused API
One endpoint. Pass in an identifier, get back emails, phones, and social handles. No account manager, no onboarding call, no enterprise tier required to access the API.
The API
GET /api/v1/people
curl "https://peopledb.co/api/v1/people?linkedin_public_identifier=dhh" \
-H "Authorization: Bearer $TOKEN"
// ←
{
"linkedin_public_identifier": "dhh",
"github_login": "dhh",
"email_addresses": ["[email protected]", "[email protected]"],
"phone_numbers": []
}Pricing
100 credits — $2 (2¢ / lookup)
500 credits — $8 (1.6¢ / lookup)
2,000 credits — $28 (1.4¢ / lookup)
10,000 credits — $100 (1¢ / lookup)
Get started →
10 free credits. No card required.