Comparison
CheckThatPhone vs Abstract API
Abstract validates numbers in 190+ countries. CheckThatPhone covers only the US and Canada, and every lookup adds the ported flag, the routing number and a send-or-not answer, with litigator and do-not-call screening in the same call.
Pick Abstract API if
Pick CheckThatPhone if
- You call or text US and Canadian numbers
- You need to know if a number was ported, and its routing number
- You want a send-or-not answer before each text
- You want litigator and do-not-call screening in the same call
10,000 lookups a month
- CheckThatPhone
- $30
- Abstract API2
- $39
Coverage
- CheckThatPhone
- US + Canada
- Abstract API1
- 190+ countries
Free plan
- CheckThatPhone
- 500 a month
- Abstract API2
- 100 a month
Invalid numbers
- CheckThatPhone
- Not charged
- Abstract API3
- Charged
What one request includes
Abstract's pricing page names its Starter plan as the one that returns carrier and line type. Both APIs return the carrier, the line type and whether the line is active.
A CheckThatPhone lookup also returns the ported flag and routing number, a send-or-not answer for texts, and location from your visitor's IP when you pass one. Abstract's Standard and Professional plans add other data at the same price, with fewer requests.
| One request | CheckThatPhone | Abstract APIStarter plan |
|---|---|---|
| Current carrier | Included: Yes, live carrier dip | Included: Yes3 |
| Mobile, landline or VoIP | Included: Yes, VoIP as IPES | Included: Yes3 |
| Ported flag and routing number | Included: Yes | Not included: No3 |
| Recently disconnected | Included: Yes, up to 45 days | Included: Yes (line status)3 |
| Can it take a text | Included: Yes: action and reason | Not included: No3 |
| State and city | Included: Yes, from the area code or the IP | Included: Yes3 |
| Time zone | Included: Yes | Included: Yes3 |
| IP geolocation in the same call | Included: Yes: pass ip | Priced separately: Separate IP geolocation API3,2 |
Cost at your volume
Abstract sells fixed request bundles with no overage rate, and moves to custom pricing above 150,000 requests a month. Our plans bill past their allowance at the plan's rate.
Abstract costs less at 5,000 and 50,000 a month. We cost less at the other volumes in the table.
| Lookups a month | CheckThatPhone | Abstract API Starter2,1 |
|---|---|---|
| 5,000 | $251K plan + overage | $19Starter |
| 10,000 | $3010K plan | $39Starter |
| 50,000 | $100100K plan | $99Starter |
| 100,000 | $100100K plan | $199Starter |
| 250,000 | $250100K plan + overage | CustomEnterprise, custom pricing |
| 500,000 | $450500K plan | CustomEnterprise, custom pricing |
List prices, monthly billing. The lower price in each row is in bold.
The details
Everything else, side by side, from Abstract's pricing, product and docs pages.
| Item | CheckThatPhone | Abstract API |
|---|---|---|
| What you get | ||
| Coverage | US and Canada (NANP) only | 190+ countries1 |
| How the data is described | Live carrier dip at lookup time | "Check any phone number in real time"; its FAQ says it uses "several databases of numbers", with "various updates to the data" daily and "substantive updates" weekly and monthly1 |
| Free plan | 500 lookups a month, hard-capped; card on file, verified with a $0 check and never charged | 100 requests a month, no credit card, every field included2 |
| Paid plans | $5 a month for 1,000 lookups up to $450 for 500,000; every plan returns the full response | Starter, Standard and Professional, each from $19 a month; the same price buys 5,000, 3,000 or 2,000 requests as each tier adds data; Enterprise is custom2 |
| Annual billing | 15% off | 10% off ($17 a month instead of $19)2 |
| Invalid or malformed numbers | HTTP 400, not charged; failed lookups never consume credits | Each submitted number counts as a credit, including invalid input3 |
| Carrier and line type | Carrier, OCN, line type and sub-type; VoIP is detected and shows as IPES in the sub-type (no separate flag) | Carrier name, line type (mobile, landline, voip, toll_free and more), MCC, MNC, is_voip3 |
| Ported numbers | dipPorted and dipLrn (routing number) on every lookup | No porting or routing-number field in the documented response3 |
| Line status | In every lookup through deliverable and action / reason, with deactivationDate for recent carrier deactivations (up to 45 days; no separate field) | line_status (e.g. active, inactive); minimum_age of the number from Standard up2 |
| Decision or risk field | action: "send", "unsubscribe" or "error", with a reason | risk_level (low, medium, high), disposable and abuse flags on Professional3 |
| Registered name and breaches | Not offered | Registered name and type (consumer or business) and breach history on Professional2 |
| TCPA litigator scrub | Add-on, +1 credit, refreshed daily | Not listed on its phone product or pricing pages2 |
| State DNC and complainer checks | Free add-on: 38 states plus DC, refreshed weekly (no federal DNC) | Not listed on its phone product or pricing pages2 |
| SMS fields | Text-enabled landline check, add-on, +1 credit on landlines only | Email-to-SMS gateway address (sms_domain, sms_email) from Standard up2 |
| List upload | CSV upload in the dashboard, up to 1,000,000 rows, deduplicated | CSV upload on paid plans, up to 50,000 rows per file3 |
| Request | POST /v1/lookup, JSON body, bearer API key | GET with api_key and phone in the query string (its docs also show a bearer-token header and POST)3 |
| Plans and terms | ||
| Minimum commitment | None: a Free plan, or monthly plans from $5 that you can cancel any time from the billing page | Monthly plans from $19 ($17 a month billed annually)2 |
| Free tier or trial | 500 lookups a month, hard-capped; card on file, verified with a $0 check and never charged | 100 requests a month, no credit card, every field included2 |
| 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 | Not published |
| Failed or invalid lookups | Not charged: a failed lookup returns credits_used: 0, and a malformed number returns HTTP 400 | Each submitted number counts as a credit, including invalid input3 |
| API access | Every plan, Free included: POST /v1/lookup with a bearer API key, plus CSV upload in the dashboard | GET with api_key and phone in the query string (its docs also show a bearer-token header and POST); CSV upload on paid plans, up to 50,000 rows per file3 |
| Rate limit | Not a fixed published number: each account's limit grows with its billing history | Its Phone plan cards list "3 requests / second", while its API docs say free plans are "limited to 1 per second"; Enterprise is "Flexible"2,3 |
| Uptime SLA | No contractual uptime SLA in our standard terms; enterprise agreements on request | Its product page lists a "99.99% uptime SLA" under "Enterprise ready"; the Enterprise plan lists "Enhanced SLA & support"1,2 |
| Support | Email (hello@checkthatphone.com) and the contact form | "24/7 via email, chat, and phone"; its pricing page says plans differ "not by speed or support"1,2 |
| 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 | Enterprise (custom pricing) above 150,000 requests a month2 |
Not published means the term isn't stated on the pages in the Sources list when we read them. It doesn't mean the vendor doesn't offer it. Our column follows the same rule, using only our own pricing, docs, terms and contact pages.
Switching from Abstract API
Abstract is a GET with api_key and phone in the query string, and returns nested objects such as phone_carrier. CheckThatPhone is a POST to https://api.checkthatphone.com/v1/lookup with a JSON body and a bearer API key, and returns flat fields with booleans as strings ("true" / "false").
curl --request POST \
--url 'https://api.checkthatphone.com/v1/lookup' \
--header 'Authorization: Bearer YOUR_API_KEY' \
--header 'Content-Type: application/json' \
--data '{"phone": "312-555-0188"}' Show a sample response
{
"success": true,
"credits_used": 1,
"data": {
"subscriber": "3125550188",
"optDate": "2026-10-03T16:04:11.210Z",
"action": "send",
"deliverable": "true",
"reason": "",
"nanpType": "mobile",
"blackList": "false",
"dip": "success",
"dipLrn": "3125550188",
"dipPorted": "false",
"dipOcn": "6010",
"dipCarrier": "AT&T",
"dipCarrierSubType": "WIRELESS",
"dipCarrierType": "mobile",
"geoState": "IL",
"geoCity": "chicago",
"geoCountry": "US",
"geoSource": "area-code",
"timezone": "America/Chicago",
"tzOffset": 6,
"error": "false"
}
} | Abstract API field | CheckThatPhone field |
|---|---|
phone_validation.is_valid3 | dip"success", "error" or "invalid". A malformed number returns HTTP 400 and costs nothing. |
phone_validation.line_status3 | action, deliverable, deactivationDateA different method: recent carrier deactivations (up to 45 days) plus a send-or-not verdict. |
phone_validation.is_voip3 | dipCarrierSubTypeVoIP shows as "IPES". |
phone_carrier.name3 | dipCarrier |
phone_carrier.line_type3 | nanpType, dipCarrierType |
phone_carrier.mcc, phone_carrier.mnc3 | dipOcnA different identifier: the carrier's OCN, not an MCC/MNC. |
phone_location.region, phone_location.city3 | geoState, geoCity |
phone_location.timezone3 | timezone |
Questions
Is CheckThatPhone a good Abstract API alternative?
For US and Canadian numbers where porting, deliverability and TCPA or do-not-call screening matter, yes. For numbers in other countries, or for registered-name and breach data, stay with Abstract.
Is Abstract cheaper than CheckThatPhone?
At some volumes. Billed monthly, Abstract Starter is $19 for 5,000 requests and $99 for 50,000, which beats us at those two points. At 10,000 and 100,000 a month we cost less, and above 150,000 Abstract moves to custom pricing. Abstract's free plan needs no card; ours includes more lookups but needs a card on file, verified with a $0 check.
Does Abstract return ported numbers?
Abstract's documented response has the carrier name, line type, MCC, MNC and a line status, but no porting flag or routing number. We return dipPorted and dipLrn on every lookup.
Are invalid numbers charged?
At Abstract, yes: its docs say each submitted number counts as a credit. Here, a malformed number returns HTTP 400 and costs nothing, and failed lookups never use credits.
What changes in the integration?
Abstract is a GET with your key and the number in the query string. CheckThatPhone is a POST to https://api.checkthatphone.com/v1/lookup with a JSON body and a bearer API key, and returns flat fields with booleans as strings ("true" / "false"). Official SDKs: npm install checkthatphone and pip install checkthatphone.
Sources
All 3 sources, with the date each was read
- Abstract Phone Validation API product page and FAQ, read October 10
- Abstract pricing page (Phone Validation plans, FAQ and sample responses), read October 10
- Abstract Phone Intelligence API documentation (response fields, bulk upload, billing), read October 10
CheckThatPhone
Try both on the same numbers
500 free credits a month. Run a slice of your list and compare the fields side by side.