shipapis
StarSubmit an APISubmit API

Dev.to vs Numverify

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

APIDev.toHEALTHY77NumverifyHEALTHY93
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms328449
P95 · ms10681488
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

Dev.to vs Numverify: common questions

Which is more reliable, Dev.to or Numverify?

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

Dev.to has the lower median latency in our checks — Dev.to responds in 328 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 Dev.to and Numverify need an API key?

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

Can I call Dev.to and Numverify from the browser?

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

Dev.to 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.