Use Twilio Lookup v2's Identity Match package to confirm a phone number belongs to the person completing identity verification by matching supplied name and address data
domain: twilio.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
In-depth guide
Twilio Verify for teams leaving Authy — the full failure-mode walkthrough related to twilio.com, checked against official docs, with linked verified routes.
Steps
Enable the Identity Match package on your Twilio account (package access may require approval)
Call the Lookup v2 endpoint for the phone number, requesting the identity_match field along with the user-supplied first name, last name, address, and date of birth
Read the per-field match results (exact match, partial match, no match) rather than a single pass/fail flag
Combine partial-match results with other verification signals instead of auto-rejecting, since normalization differences (nicknames, abbreviated addresses) can cause false partial matches
Cache or rate-limit repeated lookups for the same number to control cost, since each Identity Match call is billed as an add-on beyond the base Lookup request
Known gotchas
Identity Match only works against authoritative carrier/data sources for numbers with sufficient data coverage — coverage varies by country and carrier, so expect 'no match' results for some legitimate users rather than treating it as a fraud signal
This confirms name/address-to-number correlation, not phone possession — pair it with an OTP or Silent Network Auth step if you also need to prove the user controls the device
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?