OpenVerbs pricing: phone validation API
Is OpenVerbs yours? Write to us about this page. We invite selected tool providers to our WhatsApp group.
44% complete: 4 of the 9 fields on our checklistSee the 9 fields
$2.00per 1,000 phonesWe haven't run OpenVerbs through our phone validation API benchmark yet.We rank 1,184 plans for phone validation APIs by price. Half the plans cost $3.152 or less per 1,000 phones. This plan costs less per 1,000 phones than 55% of the 1,184 plans.GuGuData's CNY 124 (about $19) monthly plan is the cheapest paid plan per 1,000 phones. GuGuData's CNY 124 (about $19) monthly plan charges nothing per call. You get as many phones as GuGuData's rate limit allows. Neutrino API's On-Demand plan costs the least for 10,000 phones a month: $0.80.Trestle, Data247 and Abstract API are the best phone validation API providers in the Datacircle benchmark.
Plan: x402 per call OpenVerbs's only plan
Call:
POST / v1/ parse OpenVerbs's only call for this APIAPI: Phone validation API one of OpenVerbs's 9 APIs
- Amazon product API
- Amazon search API
- Local business search API
- Google Shopping search API
- Company hierarchy API
- Tech stack API
- Phone validation API
- Web scraping API
- Business verification API
POST /v1/ czechia - Business verification API
POST /v1/ finland - Business verification API
POST /v1/ france - Business verification API
POST /v1/ latvia - Business verification API
POST /v1/ norway - Business verification API
POST /v1/ poland
About this item
- Freshness. We don't know how fresh this plan's data is.
- 4 of the 9 fields on our checklist. Formats, Validity, Type, Place.
- Nothing to buy first. You pay per call.
- One call. You send
numbertoPOST /. You can also sendv1/ parse country. The call returns whether the number is valid. - Who can get it: with conditions. Keep data: no API terms. Use data: no API terms.
OpenVerbs: phone validation API alternatives
OpenVerbs alternatives: other phone validation API providers by price
We list other providers' plans closest to this plan in price per 1,000 phones.
| This planOpenVerbs, pay as you go | TokenVerify, $10 pack | RealValidito, $1,000 pack | SilverLining, pay as you go | PhoneValidator, top-up, Fake Number Check | |
|---|---|---|---|---|---|
| $ per 1,000 phones | $2.00 | $2.00 | $2.00 | $2.00 | $2.00 |
| Completeness | 44% | 33% | 78% | 44% | 22% |
| Billing | pay as you go | pay first | pay first | pay as you go | pay first |
| Pay | per call | $10 | $1,000 | monthly | any amount |
| Enough for | as many as you pay for | 5,000 calls | 500,000 results | as many as you pay for | as many as you pay for |
| Freshness | unknown | stored | unknown | unknown | unknown |
| Who can get it | anyone, with no account or API key, paying each call in USDC on Base (x402 or MPP) | anyone | self-serve signup in supported regions | anyone with an AWS account | anyone |
Sources
From each provider's own pricing page and docs, and from what providers tell us. We read this row from these pages on 2026-11-08.
Product details
The key fields this plan's answer can hold, then each filled column in its row on the sheet.
- Number, not in the answer
- Formats
- Validity
- Type
- Carrier, not in the answer
- Porting and roaming, not in the answer
- Place
- Risk, not in the answer
- Owner, not in the answer
| $ per 1,000 phones | $2.00 |
|---|---|
| Per | call |
| Billing | pay as you go |
| Aggregators | none |
|---|
| Also pays for | nothing else |
|---|
| $ per 1,000 | $2.00 |
|---|
| Their pitch | Parse, validate and format a phone number, E.164/national/international/RFC 3966, region and line type (syntactic validation, no carrier lookup). |
|---|
| What it checks | numbering plan |
|---|---|
| Keep data | no API terms |
| Use data | no API terms |
| Pay | per call |
|---|
| Batch | 1 |
|---|
| Answer | in the call |
|---|
| You send | number. Optional: country |
|---|---|
| Method | POST |
| Path | /v1/parse |
| Plan | x402 per call |
|---|---|
| Who can get it | anyone, with no account or API key, paying each call in USDC on Base (x402 or MPP) |
The 10 fields the plan's answer can hold
valid, possible, E.164 number, national format, international format, RFC 3966 format, region code, calling country code, line type, invalid reason