shipapis
StarSubmit an APISubmit API

DummyJSON vs Numverify

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

APIDummyJSONHEALTHY100NumverifyHEALTHY96
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms91292
P95 · ms19291488
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no keyFree tier — key may be required
Rate limit100 req/window · 99 remaining · resets 1783510243Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

DummyJSON vs Numverify: common questions

Which is more reliable, DummyJSON or Numverify?

Both are neck-and-neck — DummyJSON 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, DummyJSON or Numverify?

DummyJSON has the lower median latency in our checks — DummyJSON responds in 91 ms versus Numverify at 292 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 DummyJSON and Numverify need an API key?

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

Can I call DummyJSON and Numverify from the browser?

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

DummyJSON 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.