shipapis
StarSubmit an APISubmit API

InternetDB API vs Numverify

Same instrument, two spec sheets — measured, not claimed.

APIInternetDB APIHEALTHY99NumverifyHEALTHY93
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms133449
P95 · ms22601488
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

InternetDB API vs Numverify: common questions

Which is more reliable, InternetDB API or Numverify?

Both are neck-and-neck — InternetDB API and Numverify each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, InternetDB API or Numverify?

InternetDB API has the lower median latency in our checks — InternetDB API responds in 133 ms versus Numverify at 449 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do InternetDB API and Numverify need an API key?

InternetDB API needs no key, while Numverify requires a free API key. If you want to start calling without signup, reach for InternetDB API first.

Can I call InternetDB API and Numverify from the browser?

Only InternetDB API is browser-friendly — it returns CORS headers over HTTPS. Numverify needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are InternetDB API and Numverify free for commercial use?

InternetDB API has unclear commercial terms, and Numverify has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.