Profiles & sources
The profile is a useful summary. The records behind it are part of the response.
Response structure
| Field | Meaning |
|---|---|
phoneNumber | The number you requested. |
raw | Underlying lookup records, keyed by record ID. |
providerStatus | Each lookup source’s outcome and an optional reason. |
consolidation.profile | A nullable structured profile. |
consolidation.match | Confidence, rationale, source records, and concerns. |
llm | Consolidation status, reason, model, and optional usage. |
cache | Optional cache status and snapshot timestamps. |
Evidence travels with the fields
A name, email, social profile, employment record, education record, or location includes source IDs. Each ID refers to an entry in raw. Treat IDs as opaque keys and use the IDs returned with the result.
const recordId = result.consolidation?.profile?.name.sources[0];
const evidence = recordId ? result.raw[recordId] : null;The consolidation includes a name, aliases, summary, emails, phones, social profiles, employment, education, and locations when supported. Lists can be empty. Dates and other unknown values may be null.
Lookup outcomes
A lookup status can be matched, no_match, success, skipped, or error. For example, a successful number-intelligence request is not necessarily a person match.
Confidence is a judgment
Match confidence is low, medium, high, or none. Inspect the rationale and concerns alongside it. A high-confidence profile can still refer to someone who used to own the number.