Third-Party Enrichment
Third-party enrichment services: the external data providers Intempt contracts on your behalf, what each fills in, and how lookups are metered and billed.
Third-Party Enrichment
Third-party enrichment is any field filled in by an outside data vendor. Intempt holds the contracts with those vendors and resells access as metered lookups. You do not sign up with them, you do not hold their API keys, and you do not pay four separate invoices. The lookups appear on your Intempt bill.
That is the differentiator worth being concrete about: a team assembling this themselves contracts a person-and-company data vendor, an email validation vendor, a domain reputation vendor and a logo vendor, then writes the mapping from four different response shapes onto one profile schema. Here it is one integration and one bill.
What runs on your behalf
| Operation | Provider | Fills in |
|---|---|---|
| Enrich a person | People Data Labs | Name, contact, location, employment, education, socials |
| Enrich a company | People Data Labs | Name, domain, location, LinkedIn |
| Find a phone number | People Data Labs | Mobile phone |
| Find key contacts at an account | People Data Labs | Candidate people at a company |
| Validate an email address | ZeroBounce | Deliverability verdict |
| Validate a domain | EmailGuard | Domain reputation and sending health |
| Company logo | Logo.dev, Google favicon | Account picture |
Seven operations across four external providers, plus two logo sources.
What People Data Labs writes
PDL is the provider doing the heavy lifting, so it is worth being exact about which reserved keys it can populate. Person enrichment writes:
| Key | Key | |
|---|---|---|
name | city | |
first_name | state | |
middle_name | country | |
last_name | linkedin | |
email | school_name | |
phone | company_name |
Company enrichment writes:
| Key | Key | |
|---|---|---|
name | state | |
website | country | |
city | linkedin |
Every one of these is a reserved key from user and account attributes, not a provider-shaped blob. That is the whole point of the mapping layer: swapping a provider does not change your schema.
Geo and IP location
IP-based location is a separate path from person and company enrichment, and it has two tiers.
| Tier | Provider | Availability |
|---|---|---|
| Standard | ipapi.co | Included |
| Enterprise | MaxMind | Add-on, contact sales |
MaxMind is sold as an enterprise add-on rather than a self-serve toggle. If you need it, talk to us: the pricing and the deployment are handled per contract, and it is not something you enable from the console today.
How lookups are billed
Enrichment is metered, not flat-rate, and the accounting is deliberate about not charging you for work that failed.
| Billing category | data_enrichment |
| Unit | lookups |
| Metered per | Entity looked up, not per API call |
The sequence for any enrichment operation:
- Authorize. Intempt deducts the maximum possible cost up front, for the number of entities you asked to enrich. Enrichment cost is deterministic, so the maximum is knowable before the provider is called. Deducting first closes the race where two operations both check a balance and both proceed.
- Call the provider.
- Reconcile. If the actual number of entities enriched matches what was authorized, the authorization is captured as-is. If fewer came back, because a person was not found or a domain did not resolve, the authorization is refunded in full and the real amount is deducted instead.
Every deduction carries an idempotency key, so a retry does not double-charge.
If the process dies mid-operation, the authorization is left pending and an expiry job refunds it automatically. The failure mode is deliberately in your favour: you get that operation free rather than paying for a lookup nobody captured.
Compared with first-party
First-party enrichment costs nothing per lookup and never leaves your data. Third-party enrichment is what you cannot compute from your own data: whether a company is hiring, who its competitors are, whether an email address will bounce. Reach for first-party first; it is free and it is always available.
Rate of change
Provider coverage is a commercial arrangement, so it changes without a schema change. What will not change under you is the reserved key set: a new provider writes into the same 86 attributes. Check your plan's entitlements in the console for which operations are enabled on your account.