shipapis
StarSubmit an APISubmit API

CDNJS vs Numverify

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

APICDNJSHEALTHY95NumverifyHEALTHY93
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms281449
P95 · ms9361488
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree and open, no keyFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

CDNJS vs Numverify: common questions

Which is more reliable, CDNJS or Numverify?

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

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

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

Can I call CDNJS and Numverify from the browser?

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

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