Comparison

CheckThatPhone vs Numverify: porting and deliverability in 2 countries, or validation in 232

CheckThatPhone is a Numverify alternative for US and Canadian numbers when you need the current carrier, whether the number was ported and whether it can take a text. Numverify validates numbers in 232 countries against international numbering plans, from $14.99 a month for 5,000 requests. CheckThatPhone covers only the US and Canada, but runs a live carrier dip on every lookup, from $5 a month for 1,000. Neither is cheaper at every volume: 10,000 lookups a month cost $30 on our 10K plan against $59.99 on Numverify Professional, while 250,000 cost $129.99 on Numverify Enterprise against $250 on our 100K plan. Either way, one CheckThatPhone lookup also includes the ported flag and routing number, recent disconnections, a send-or-not verdict for texts, the time zone and location from your visitor's IP in the same call, which a Numverify request doesn't (what each includes).

If you need numbers from outside North America, or the lowest price per request at certain volumes, Numverify is the better fit. If you call or text North American numbers, the porting, deliverability and compliance fields are what CheckThatPhone adds.

As of October 3, 2026, read from Numverify's own pricing and documentation pages. Each Numverify 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

Cost at different volumes

Base lookups each month, monthly billing, cheapest plan on each side including overage. Numverify figures use the plan prices and overage rates on its pricing page; its Free plan is left out because it is non-commercial.

Neither is cheaper at every volume: it depends on where your volume falls against each plan's included requests. The bigger difference is what a request includes. Numverify's documented response has no ported flag or routing number, while a live carrier dip returns both, along with the carrier serving the number today.

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, the time zone and location from your visitor's IP in the same call, which a request to Numverify (every plan) doesn't.

✓ included ◐ included with a limit + a separately priced package or API – not in the documented request or response

Operational terms

Commitments, limits and support, from each side's own published pages. Where a page doesn't state a term, the table says so.

Not published means it isn't stated on the Numverify pages listed under Sources when we read them. It doesn't mean Numverify doesn't offer it. Our column follows the same rule, using only our own pricing, docs, terms and contact pages.

Which one to choose

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": "617-555-0133"}'

An illustrative response (a fictional 555 number; field names and formats match the live API). The fields with no counterpart in Numverify's documented response are the carrier dip fields (dipLrn, dipPorted, dipOcn), action, deliverable and timezone:

{
  "success": true,
  "credits_used": 1,
  "data": {
    "subscriber": "6175550133",
    "optDate": "2026-10-03T15:31:52.640Z",
    "action": "send",
    "deliverable": "true",
    "reason": "",
    "nanpType": "mobile",
    "blackList": "false",
    "dip": "success",
    "dipLrn": "6175550133",
    "dipPorted": "false",
    "dipOcn": "6010",
    "dipCarrier": "AT&T",
    "dipCarrierSubType": "WIRELESS",
    "dipCarrierType": "mobile",
    "geoState": "MA",
    "geoCity": "boston",
    "geoCountry": "US",
    "geoSource": "area-code",
    "timezone": "America/New_York",
    "tzOffset": 5,
    "error": "false"
  }
}

Sources

Numverify pages, with the date we read each one:

• Numverify pricing page (plans, overage and FAQ) (read October 3, 2026 and October 10, 2026)
• Numverify documentation: response fields and request format (read October 3, 2026 and October 10, 2026)
• Numverify API documentation overview (read October 3, 2026)
• Numverify API reference (endpoints) (read October 3, 2026 and October 10, 2026)
• Numverify homepage (read October 3, 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 Vonage Number Insight and vs Trestle
• Eight vendors side by side: Phone validation API pricing in 2026