People data, United States
Property-to-Person Identity Resolution
An identity resolution API and batch service: send an address, a name, a phone or an email and get back the person, the property they own and verified contact points, anchored to the parcel.
Most identity graphs are built on digital exhaust. Ours is anchored to the physical world: a parcel, a deed and a person's name on it. Give us any fragment, an address, a name plus city, a phone or an email, and we return the resolved person, their current and prior addresses, the properties they own and their verified contact points.
It runs as an API for real-time use and as batch for files of millions.
How the identity resolution API works
Send whatever you have about a person. The API resolves it against the parcel, deed, consumer, telco and professional graphs and returns one person with a confidence score. Where the address disambiguates, matching is permissive; where it does not, it is strict.
| You send | You get back |
|---|---|
| Address | The owner of record and the resident, the properties they own, mobile and email |
| Name plus city or ZIP | The resolved person, current and prior addresses, properties owned |
| Phone | The person behind the number, line type, their home and other contact points |
| Email or SHA-256 hash | The person, their address history and the property they own |
The same resolution runs as batch for CRM files and lead lists. See bulk files versus API for which fits.
Sample rows
Illustrative and synthetic. Real samples for your geography are a reply away.
| input | resolved_name | current_address | owns | prior_addresses | mobile | confidence | |
|---|---|---|---|---|---|---|---|
| (615) •••-••33 | A••••• N••• | 5•• Maple Ridge Dr, Franklin TN | 1 property | Chicago IL (2019-2026) | (615) •••-••33 | a•••••@outlook.com | 0.94 |
| •••• W Oakwood Ave, Chicago IL | K••••• W••••• | same | 3 properties | (•••) •••-••04 | k•••@gmail.com | 0.91 |
Schema
| Field | Type | Notes |
|---|---|---|
| input | text | non-personal |
| resolved_name | text | personal data |
| current_address | text | personal data |
| owns | boolean | non-personal |
| prior_addresses | text | personal data |
| mobile | phone | personal data |
| personal data | ||
| confidence | number | non-personal |
Abridged. The full data dictionary ships with every sample and lists every field, its fill rate and its source.
Used for
- CRM deduplication and enrichment
- Lead scoring with property context
- KYC and fraud checks
- Cross-device audience matching
How it is built
A union of our consumer, telco, property and professional graphs with permissive matching where the address disambiguates and strict matching where it does not. Confidence is reported on every response.
Questions we get
What inputs does the identity resolution API accept?
An address, a name with city or ZIP, a phone number, an email, or SHA-256 hashes of the email or phone. More fragments raise the confidence of the match.
What comes back?
The resolved person, their current and prior addresses, the properties they own, matched mobile and email, and a confidence score on every response.
API or batch?
Both. The API handles one record at a time inside a user flow; batch handles files of millions and returns the same fields.
Do you match on hashed emails?
Yes, SHA-256 email and phone hashes are accepted inputs.