A phone validation API can tell you a number is “valid” and still leave you guessing. The trouble is that “valid” and “reachable” are not the same thing, and the gap between them is where wasted messages, fraudulent signups, and TCPA exposure live. If you are comparing CheckThatPhone against Twilio Lookup, Telnyx, or Numverify, what matters is how current the data is and whether the API tells you what to do with a number, not just what it is.
The features that matter
The short answer: of these four, CheckThatPhone is the only one that returns a recommended action, a TCPA litigator scrub, and a state DNC check in the same call. Twilio Lookup and Numverify cover far more countries, and Telnyx sells the cheapest pay-as-you-go live routing data.
| Feature | CheckThatPhone | Twilio Lookup | Telnyx | Numverify |
|---|---|---|---|---|
| How they describe the data | Live carrier dip | “Live carrier network data” | Live LRN, HLR and caller-name lookups | “Real time”, against numbering-plan databases |
| Cheapest useful lookup | $0.0009 to $0.005 | $0.008 (line type) | $0.0015 (LRN only) | ~$0.0005 to $0.003 |
| Free tier | 500 credits/month | Formatting and validation | None (paid account) | 100 requests/month (non-commercial) |
| Ported / activity status | Both, in the base lookup | Activity paid (Line Status); no ported field | Ported yes; mobile status via HLR (per Telnyx) | No |
| Recommended action | Yes (send / unsubscribe / error) |
No | No | No |
| IP geolocation & timezone | Included when you pass an IP | No | No | No |
| TCPA litigator scrub | Add-on, +1 credit | No | No | No |
| State DNC + complainer check | Free | No | No | No |
| Landline SMS reachability | Add-on, +1 credit (landlines only) | No | No | No |
Competitor facts come from each provider’s own pricing, product and documentation pages (Twilio Lookup pricing and product page, Telnyx, Numverify), checked October 3, 2026. Verify before you commit budget.
Where CheckThatPhone stands out
The action recommendation is the piece I lean on most. Instead of handing back raw fields and leaving you to build the logic, CheckThatPhone returns action as "send", "unsubscribe", or "error". "send" means the number passed every enabled check (it is not a consent record; you still need your own lawful basis to contact the person). "unsubscribe" means don’t message it: a TCPA litigator match, a line that can’t take SMS, an internal blacklist hit, or a carrier deactivation in the last 45 days, with reason telling you which. "error" means the request itself was malformed. That is one less branch of custom filtering you have to write and maintain around disposable or problematic numbers. The full response schema is in the API documentation.
Fraud screening gets more to work with too. The carrier sub-type separates VoIP (IPES) from wireless and wireline carriers, and deactivation data flags recently disconnected numbers, which catches throwaway numbers that a format check waves through.
There is also a compliance check the other three don’t offer: litigator screening. Turn on the litigator scrub and each number is checked against a database of known serial TCPA plaintiffs and repeat filers, refreshed daily. A match comes back with the litigator name and type, and it rewrites the action to “unsubscribe” so a risky number never lands in a campaign. For anyone running outbound SMS or a dialer, that single field is the difference between a clean list and a demand letter. It is opt-in and costs a credit per lookup, so you only pay for it on the numbers you actually scrub. There are also free dncState and dncComplainer flags that run a state do-not-call check (38 states plus DC) and screen a national complainer list in the same call, and the state check reports when it didn’t run, for numbers in the 12 states it doesn’t cover.
The landline SMS check is the other piece I reach for. About 7% of the landlines we check are SMS-capable, and a plain line-type check throws them all out. Switch on the reachability add-on and you find out which landlines can actually receive a message, so you stop discarding contactable numbers. Mobile numbers skip the check, so the surcharge only lands where it applies.
Lookups are real-time, so it works inline during account signup or right before an SMS goes out. The API docs have curl, JavaScript, and Python examples, and there are official Node.js and Python SDKs.
The scope is deliberate. CheckThatPhone covers US and Canadian numbers only. That narrower focus is what pays for the depth.
Pricing is usage-based and transparent, without locking the useful features behind a premium tier: $0.0009 to $0.005 per credit depending on plan, and 500 free credits a month. The pricing page has current plans and the free tier details.
Where other APIs fall short
- Twilio Lookup prices each signal separately. Line type is $0.008 a request, Line Status (is the number still reachable) is another $0.007, and its Lookup packages include no recommended action, litigator data, or DNC scrub; its US-only Reassigned Number check is the one built for TCPA consent. It does cover far more countries. Full breakdown: CheckThatPhone vs Twilio Lookup.
- Numverify checks numbers against international numbering-plan databases, and its documented response has no ported or line-status field. For low-cost global validation across 232 countries, it does the job. See CheckThatPhone vs Numverify.
- Telnyx is the cheapest pay-as-you-go option for live data ($0.0015 per LRN dip), but mobile carrier codes ($0.0025) and caller name ($0.003) are billed on top, and the response has no DNC or litigator fields.
None of the three returns a recommended action or litigator screening, so you end up building that filtering logic on top yourself.
Matching the tool to the job
| Use Case | Best Fit |
|---|---|
| US/Canada outbound calling or texting with TCPA exposure | CheckThatPhone |
| Lightweight signup filtering (US/Canada) | CheckThatPhone |
| Global phone support | Twilio Lookup, Numverify or Abstract API |
| Format checks only | Twilio’s free formatting and validation check, or Numverify (free plan is non-commercial) |
| Pay-as-you-go LRN routing data | Telnyx |
Where to start
Lead gen, user verification, and messaging platforms each ask different things of a validation API, and no single tool wins everywhere. But if your priorities are cutting failed communications, catching fraudulent signups, scrubbing TCPA litigators before you dial, cleaning CRM data for North American numbers, and keeping messaging costs down, CheckThatPhone covers them in one call.
For a deeper look at what each service charges per lookup, including Trestle, IPQS, and the budget validators, see the phone validation API pricing comparison. All of our head-to-head pages are on the comparison hub, and if you’re still deciding which capabilities matter, choosing a phone validation API walks through the seven to check.
Want to see how it compares on your own data? Explore the documentation to review the endpoints and response fields, or start with the free tier to test real-time validation against your real numbers.