Resolve an identity API
people.identity.resolve
- providers document it
- 7
Providers
7 providers document resolve an identity in their own API docs. None routes it through GridRouter yet. Scores appear as calls are routed.

People and company search API with async email finding and reverse lookup.

REACH consumer and B2B contact append and identity APIs with an MCP server.
Mastercard identity verification data for fraud decisions.

Identity resolution and person enrichment platform with an MCP server.

Identity and fraud intelligence from a people search API.

Identity infrastructure provider (sales-led).

Identity resolution (AbiliTec, RampID), clean rooms and activation APIs.
- What counts as a hit:
- At least one linked identifier is returned.
API
Same input for every provider. Set provider.sort to route by price, reliability or latency, or provider.only to pin providers; X-Grid-Max-Cost caps what one call can spend.
| Input | Description |
|---|---|
| Email or SHA-256 of it | |
| phone | E.164 phone |
curl https://api.gridrouter.io/v1/run/people.identity.resolve \
-H "Authorization: Bearer $GRID_API_KEY" \
-H "Content-Type: application/json" \
-H "X-Grid-Max-Cost: 0.05" \
-d '{"input":{"email":"dana@northwind.dev"},"provider":{"sort":"price"}}'Fields
The normalized output every provider maps into. Suppliers come from integrated endpoint mappings (verified) or field names in each provider's API docs (claimed by the provider).