Clean & enrich
Repair the records you already have
Fix the data you already have before buying more. Canonical matching against golden records, stale-record repair, and email verification — charged per outcome, not per query.
What it does
Three jobs, all of them repairs
Fix what is already there before buying more. A corrected record is worth more than a new one, and cheaper. Stale titles and company details are corrected, and email addresses are checked for validity before the record is used.
- Canonical ID matching resolves your records against a single identity graph
- Stale job titles and company details corrected rather than left to rot
- Per-outcome pricing: pay for records fixed, not for searches that found nothing
Billing
You pay for records fixed, not for searches that found nothing
Per-outcome pricing is the whole shape of the commercial model here. A query that returns nothing has changed nothing, so there is nothing to bill for.
For the data underneath this API, see data feeds. If you are still deciding what to build first, company and contact search is the other half. How the rate is set is on the pricing page.
How we work
We will prove it on your data before you commit to anything wider
Bring a slice of the datasets you run on today. We resolve them against the same identities our feeds use and show you exactly what changes — before you are depending on it.
You test it on your own records
Not a demo dataset. Your data, resolved against the same identity graph, so you can see the real delta rather than a curated example.
You see every change we make
If a record is wrong, point at the field. We trace it to the signal that produced it, fix it against the source rather than over the top, and write the reason onto the field so the next read shows what moved.
Corrections land everywhere
A fix shows up in the feeds, in enrichment, and in search — not only in the place you happened to notice it. One dataset means one correction, not three.
Enrichment is billed per accepted outcome
You pay for records actually fixed. A search that returns nothing is not an error and not an invoice, and a retry loop wrapped around a miss does not produce a better answer.
We will tell you if it does not fit
If your use case is better served by something else, we will say so. A short conversation is worth more than a pilot that goes nowhere.
Bring a slice of your own data and we will show you where it breaks
Start with the datasets you already run on. We will resolve them against the same identities our feeds use and show you what changes before anything wider is committed.