shipapis
StarSubmit an APISubmit API

Fake JSON API vs Numverify

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

APIFake JSON APIHEALTHY88NumverifyHEALTHY93
Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d98.3%100%
P50 · ms865449
P95 · ms20061488
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

Fake JSON API vs Numverify: common questions

Which is more reliable, Fake JSON API or Numverify?

On our scheduled checks, Numverify leads on measured uptime — Fake JSON API at 99.02% versus Numverify at 100% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, Fake JSON API or Numverify?

Numverify has the lower median latency in our checks — Fake JSON API responds in 865 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 Fake JSON API and Numverify need an API key?

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

Can I call Fake JSON API and Numverify from the browser?

Only Fake JSON 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 Fake JSON API and Numverify free for commercial use?

Fake JSON 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.