Comparison
CheckThatPhone vs Vonage Number Insight: a US and Canada replacement before the February 2027 sunset
Vonage's Number Insight overview says: "Effective February 4, 2027, Vonage will sunset Vonage Number Insights," and asks customers to migrate to its Identity Insights API. If your numbers are in the US and Canada, CheckThatPhone is a replacement that returns the current carrier, line type, porting status, routing number and deliverability in one lookup, for mobiles, landlines and VoIP. 10,000 lookups a month cost $30 on our 10K plan; Identity Insights' Current Carrier insight lists at $81.90 for the same 10,000 (10,000 × $0.00819), for mobile numbers only. One CheckThatPhone lookup also includes the ported flag and routing number, recent disconnections, a send-or-not verdict for texts and location from your visitor's IP in the same call, which Identity Insights' Current Carrier doesn't, and covers landlines and VoIP too (what each includes).
Vonage's own path is Identity Insights. Its transition guide maps Number Insight's formatting, original carrier and current carrier to equivalent insights, and the new API adds SIM Swap and Subscriber Match. Its API reference has no porting-status field and no caller-name insight, and roaming and reachability move to insights whose coverage is "currently limited" and "only exposed through Vonage Virtual Operator". For numbers outside North America or for SIM Swap, Identity Insights is the better fit. If you rely on caller name (CNAM), we don't return it, and the Identity Insights API reference lists no caller-name insight.
As of October 9, 2026, read from Vonage's own developer documentation and pricing pages. Each Vonage fact links to the page it came from. A few were read later, on October 10, 2026, and are dated where they appear. Prices change, so check the source before you commit budget. CheckThatPhone is our product. How we compare vendors.
At a glance
Vonage's column covers both Number Insight, until the sunset, and Identity Insights, the API Vonage asks Number Insight customers to move to. Each cell says which one it describes.
| CheckThatPhone | Vonage | |
|---|---|---|
| Status | Available | "Effective February 4, 2027, Vonage will sunset Vonage Number Insights"; Vonage points to its Identity Insights API source |
| Coverage | US and Canada (NANP) only | Identity Insights Format, Original Carrier and Current Carrier: worldwide, no approval needed source |
| Pricing | $5 a month for 1,000 lookups up to $450 for 500,000; overage $0.005 down to $0.0009 per lookup | Per request, per insight: Format "No Cost", Original Carrier $0.00117, Current Carrier $0.00819; SIM Swap and Subscriber Match "Price varies per country". Number Insight per-level prices are no longer on its pricing pages pricing NI pricing API pricing |
| Current carrier | Every lookup, mobile or landline: dipCarrier and dipOcn from a live carrier dip | Current Carrier insight: "applicable to mobile numbers only"; it "reflects number portability" source |
| Original carrier | nanpCarrier and nanpType from numbering-plan data (not authoritative after porting) | Original Carrier insight, "not reflecting portability changes" source |
| Ported flag and routing number | dipPorted and dipLrn on every lookup | Number Insight Standard and Advanced return porting information; the Identity Insights API reference has no porting-status field NI details II API |
| Line type | Mobile or landline, plus carrier sub-type (IPES = VoIP) | Number Insight: "mobile/landline/virtual number/premium/toll-free"; Identity Insights Current Carrier network_type: MOBILE only Standard II API |
| Reachability | action, deliverable and deactivationDate in every lookup (a different method, not the same check) | Number Insight Advanced: reachable "not available in the US"; in Identity Insights, Reachability is a Developer Preview, "only exposed through Vonage Virtual Operator" Advanced II details transition guide |
| Caller name (CNAM) | Not offered | Number Insight add-on, US only, charged "regardless of whether any information is returned"; no caller-name insight in the Identity Insights API reference NI API II API |
| SIM swap, subscriber match | Not offered | Identity Insights SIM Swap (general availability) and Subscriber Match (beta), after operator approval; US and Canadian operators listed II details coverage |
| Location and time zone | State, city, metro, timezone and tzOffset | The Format insight returns offline_location and time_zones source |
| TCPA litigator scrub | Add-on, +1 credit, refreshed daily | Not listed on its Identity Insights pricing page source |
| State DNC and complainer checks | Free add-on: 38 states plus DC, refreshed weekly (no federal DNC) | Not listed on its Identity Insights pricing page source |
| Text-enabled landlines | Add-on, +1 credit on landlines only | Not listed on its Identity Insights pricing page source |
| Errors and billing | Failed lookups are not charged (credits_used: 0) | Number Insight refunds internal lookup errors (refund_price); Identity Insights returns a status per insight and doesn't say whether a failed insight is billed NI API transition guide |
| Request | POST /v1/lookup, JSON body, bearer API key | Number Insight: GET or POST to api.nexmo.com/ni/basic, /standard or /advanced, HTTP Basic auth. Identity Insights: POST /identity-insights/v1/requests with a JWT NI API II API transition guide |
Field mapping: Number Insight to CheckThatPhone
Number Insight's documented response fields (Standard and Advanced) and where each one lands in a CheckThatPhone response. Every field is described in our API reference.
| Number Insight field | CheckThatPhone field | Notes |
|---|---|---|
current_carrier.name source | dipCarrier | Ours covers landlines and VoIP too; Vonage documents current_carrier for mobile numbers only. |
current_carrier.network_type source | nanpType, dipCarrierType, dipCarrierSubType | VoIP shows as IPES in dipCarrierSubType. |
current_carrier.network_code source | dipOcn | A different identifier: the carrier's OCN, not an MCC/MNC. |
original_carrier source | nanpCarrier, nanpType | Numbering-plan data; not authoritative after porting. |
ported source | dipPorted + dipLrn | Ours is "true" / "false" with the routing number; theirs adds assumed_ported, assumed_not_ported and unknown. |
lookup_outcome source | dip | "success", "error" or "invalid". |
valid_number source | dip / dipCarrierType | An invalid number shows as "invalid". |
reachable source | action, deliverable, deactivationDate | A different method, not the same check (their values include blacklisted). deactivationDate is not reassigned-number detection. |
caller_identity (CNAM) source | No equivalent | We don't return caller name. |
roaming source | No equivalent | |
country_code source | geoCountry | |
national_format_number source | subscriber | Ten digits, no formatting. |
request_price, refund_price source | credits_used | Failed lookups return credits_used: 0. |
Cost at different volumes
Number Insight's own per-level prices are no longer on Vonage's pricing pages, which now show Identity Insights, so the Vonage columns use its pay-per-request list prices (Identity Insights pricing; Vonage asks you to contact it for pricing by country). "Current + Original" assumes each requested insight is billed at list; the pages we read don't say whether an insight that returns no data is billed. CheckThatPhone is our cheapest plan for the volume, including overage.
| Lookups a month | Vonage Current Carrier | Vonage Current + Original Carrier | Vonage Original Carrier | CheckThatPhone |
|---|---|---|---|---|
| 1,000 | $8.19 | $9.36 | $1.17 | $5 (1K plan) |
| 10,000 | $81.90 | $93.60 | $11.70 | $30 (10K plan) |
| 50,000 | $409.50 | $468 | $58.50 | $100 (100K plan) |
| 100,000 | $819 | $936 | $117 | $100 (100K plan) |
| 250,000 | $2,047.50 | $2,340 | $292.50 | $250 (100K plan) |
| 500,000 | $4,095 | $4,680 | $585 | $450 (500K plan) |
Original Carrier alone costs less than our plans below about 85,000 lookups a month, but Vonage describes it as "not reflecting portability changes", so it can name the wrong carrier for a ported number. Current Carrier reflects porting and is documented for mobile numbers only; our lookup returns the current carrier for landlines and VoIP numbers too.
What one request includes
A lower price per request only compares like with like when the requests return the same data. One CheckThatPhone lookup also includes the ported flag and routing number, recent disconnections, a send-or-not verdict for texts and location from your visitor's IP in the same call, which a request to Vonage (Current Carrier + free Format) doesn't.
| One request includes | CheckThatPhone | VonageCurrent Carrier + free Format |
|---|---|---|
| Current carrier | Included: Yes, live carrier dip | Partly: Mobile numbers only source |
| Mobile, landline or VoIP | Included: Yes, VoIP as IPES | Partly: Mobile only source |
| Ported flag and routing number | Included: Yes | Not included: No source |
| Recently disconnected | Included: Yes, last 45 days | Not included: No source |
| Can it take a text | Included: Yes: action and reason | Not included: No source |
| State and city | Included: Yes, from the area code or the IP | Included: From the number's prefix source |
| Time zone | Included: Yes | Included: Yes source |
| IP geolocation in the same call | Included: Yes: pass ip | Not included: No source |
included included with a limit a separately priced package or API not in the documented request or response
Every documented field, by name
The response fields that describe the number, from each side's own reference. Not listed:
copies of the number you sent, format variants, ids, status, error and price fields; on our
side also deliverable, doNotSms and tzOffset, which
restate other fields.
Vonage documents Current Carrier for mobile numbers only. Original Carrier adds 4 fields for $0.00117 more. II API pricing read October 10, 2026
CheckThatPhone 18 fields
actionreasondeactivationDateblackListsmsEligiblenanpTypenanpCarrierdipLrndipPorteddipOcndipCarrierdipCarrierTypedipCarrierSubTypegeoCountrygeoStategeoCitygeoMetrotimezone
Vonage 9 fields
current_carrier.namecurrent_carrier.network_typecurrent_carrier.country_codecurrent_carrier.network_codeformat.country_codeformat.country_nameformat.offline_locationformat.time_zonesformat.is_format_valid
Operational terms
Commitments, limits and support, from each side's own published pages. Vonage's column describes Identity Insights unless a row says Number Insight. Where a page doesn't state a term, the table says so.
| CheckThatPhone | Vonage | |
|---|---|---|
| Minimum commitment | None: a Free plan, or monthly plans from $5 that you can cancel any time from the billing page pricing terms | None listed: "All API pricing is by usage" source |
| Free tier or trial | 500 lookups a month, hard-capped; card on file, verified with a $0 check and never charged source | "Start developing now with free credit. No credit card required." The amount isn't stated. source |
| Past the plan allowance | $0.005 down to $0.0009 per lookup on paid plans, on the next invoice; the Free plan stops at 500 source | No plan allowance: each insight is billed per request source |
| Failed or invalid lookups | Not charged: a failed lookup returns credits_used: 0, and a malformed number returns HTTP 400 pricing docs | Number Insight: "If there is an internal lookup error, the refund_price will reflect the lookup price." Identity Insights: not stated, and "The HTTP response can succeed (e.g. HTTP 200) even if one or more insights failed" NI API transition guide |
| API access | Every plan, Free included: POST /v1/lookup with a bearer API key, plus CSV upload in the dashboard docs bulk | Format and carrier insights are self-serve with no approval; SIM Swap and Subscriber Match need approval from the mobile operators. Identity Insights uses POST with a JWT II details SIM Swap transition guide |
| Rate limit | Not a fixed published number: each account's limit grows with its billing history source | Not published |
| Uptime SLA | No contractual uptime SLA in our standard terms; enterprise agreements on request source | Not published |
| Support | Email (hello@checkthatphone.com) and the contact form source | Its API pricing page lists "flexible Service and Support plans" source |
| Unused credits | Not published | Not published |
| High volume | The 500K plan keeps working past 500,000 at $0.0009 per lookup; a quote form for higher volume source | "contact us for specific pricing by country" source |
Not published means it isn't stated on the Vonage pages listed under Sources when we read them. It doesn't mean Vonage doesn't offer it. Our column follows the same rule, using only our own pricing, docs, terms and contact pages.
Which one to choose
Choose Vonage if…
- Your numbers are outside the US and Canada. Identity Insights' Format and carrier insights are listed as worldwide; we cover two countries. source
- You need SIM Swap or Subscriber Match. Identity Insights offers both (Subscriber Match is in beta), with US and Canadian operators listed, once the operators approve your access. We offer neither. II details coverage
- You only need number formatting. The Format insight costs nothing. source
- You only need the originally assigned carrier. Original Carrier is $0.00117 a request, less than our plans below about 85,000 lookups a month, though it doesn't reflect porting. pricing Original Carrier
- You rely on caller name (CNAM). Number Insight Standard and Advanced offer it as a US add-on until the sunset. We don't return caller name, and the Identity Insights API reference lists no caller-name insight. NI details II API
- You want no monthly plan, paying per request, with free credit to start and no card. API pricing pricing
Choose CheckThatPhone if…
- You want more in one call: the ported flag and routing number, recent disconnections, a send-or-not verdict for texts and location from your visitor's IP in the same call come with every lookup (compare).
- You need porting data: the ported flag (
dipPorted) and routing number (dipLrn) on every lookup. See the LRN lookup API. - You check landlines and VoIP numbers too. Carrier and line type come back for every US and Canadian number, with VoIP shown as
IPES. See the line type lookup API. - You want a send-or-not answer:
action,deliverableanddeactivationDatein every lookup. - You want compliance screening in the same call: the TCPA litigator scrub (+1 credit) and the free state DNC and complainer checks.
- You text landlines. About 7% of landlines we check are SMS-capable, and the landline SMS lookup finds them.
- You clean lists: CSV upload up to 1,000,000 rows, each unique number billed once.
- You want a plain API key: a bearer key on
POST /v1/lookup, with no JWT to sign.
Example request and response
A standard CheckThatPhone lookup:
curl --request POST \
--url 'https://api.checkthatphone.com/v1/lookup' \
--header 'Authorization: Bearer YOUR_API_KEY' \
--header 'Content-Type: application/json' \
--data '{"phone": "404-555-0117"}'
An illustrative response (a fictional 555 number; field names and formats match the live API).
This number is ported: dipPorted is "true", the status Number
Insight returned as ported, and dipLrn is the routing number it now
uses.
{
"success": true,
"credits_used": 1,
"data": {
"subscriber": "4045550117",
"optDate": "2026-10-09T14:12:40.318Z",
"action": "send",
"deliverable": "true",
"reason": "",
"nanpType": "mobile",
"blackList": "false",
"dip": "success",
"dipLrn": "4045550199",
"dipPorted": "true",
"dipOcn": "6010",
"dipCarrier": "AT&T",
"dipCarrierSubType": "WIRELESS",
"dipCarrierType": "mobile",
"geoState": "GA",
"geoCity": "atlanta",
"geoCountry": "US",
"geoSource": "area-code",
"timezone": "America/New_York",
"tzOffset": 5,
"error": "false"
}
} CheckThatPhone vs Vonage Number Insight: common questions
When does Vonage Number Insight shut down?
Vonage's Number Insight overview says: "Effective February 4, 2027, Vonage will sunset Vonage Number Insights." Its transition guide asks customers to move their Basic, Standard and Advanced integrations to the Identity Insights API before then.
Is CheckThatPhone a drop-in replacement for Number Insight?
For US and Canadian carrier, line type and porting data, it covers the same ground under different field names (see the field mapping above), and it adds deliverability, litigator and state DNC checks. It is not a drop-in: the request is a POST with a JSON body and a bearer API key, and we don't return caller name, roaming or numbers outside the US and Canada.
We use CNAM (caller name). Can we move to you?
No. CheckThatPhone doesn't return caller name, and the Identity Insights API reference lists no caller-name insight either. Number Insight Standard and Advanced offer CNAM as a US add-on until the sunset, so plan that part of the migration separately.
Why not move to Vonage Identity Insights?
If your numbers are outside North America, or you need SIM Swap or Subscriber Match, it's the natural path. For US and Canadian numbers, compare what comes back: Vonage documents Current Carrier for mobile numbers only and its Identity Insights API reference has no porting-status field, while every CheckThatPhone lookup returns the carrier, line type, ported flag and routing number for mobiles, landlines and VoIP.
How does the cost compare with Identity Insights?
At 10,000 lookups a month: $30 on our 10K plan, $81.90 for Current Carrier at Vonage's $0.00819 list price, or $93.60 for Current plus Original Carrier, which its transition guide says to request together. Original Carrier alone ($11.70) costs less than our plans at that volume, but it reflects the first-assigned network, not porting.
What changes in the integration?
Number Insight is a GET (or POST) to https://api.nexmo.com/ni/standard or /advanced with HTTP Basic auth; Identity Insights needs a JWT. CheckThatPhone is a POST to https://api.checkthatphone.com/v1/lookup with a JSON body and a bearer API key, and returns flat fields such as dipCarrier and dipPorted, with booleans as strings ("true" / "false"). Official SDKs: npm install checkthatphone and pip install checkthatphone.
Sources
Vonage pages, with the date we read each one:
- Vonage Number Insight overview (sunset notice) (read October 9, 2026)
- Vonage Number Insights Transition Guide (read October 9, 2026)
- Vonage Number Insight technical details (feature table) (read October 9, 2026)
- Vonage Number Insight API reference (read October 9, 2026)
- Vonage Number Insight Standard code snippet (read October 9, 2026)
- Vonage Number Insight Advanced (async) code snippet (read October 9, 2026)
- Vonage Number Insight pricing page (now shows the Identity Insights prices) (read October 9, 2026)
- Vonage Identity Insights pricing (read October 9, 2026 and October 10, 2026)
- Vonage API pricing overview (read October 9, 2026)
- Vonage Identity Insights API reference (read October 9, 2026 and October 10, 2026)
- Vonage Identity Insights technical details (availability table) (read October 9, 2026)
- Vonage Network Features coverage (operators by country) (read October 9, 2026)
- Vonage Identity Insights: Current Carrier guide (read October 9, 2026 and October 10, 2026)
- Vonage Identity Insights: Original Carrier guide (read October 9, 2026)
- Vonage Identity Insights: SIM Swap guide (read October 9, 2026)
CheckThatPhone figures come from our pricing page, API documentation and terms of service.
Related
- All comparisons and the cost at different volumes: CheckThatPhone compared
- Other options: vs Twilio Lookup, vs Abstract API, vs Numverify and vs Trestle
- Eight vendors side by side: Phone validation API pricing in 2026