shipapis
StarSubmit an APISubmit API

CDNJS vs Hunter

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

APICDNJSHEALTHY95HunterHEALTHY96
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms281362
P95 · ms936859
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 Hunter: common questions

Which is more reliable, CDNJS or Hunter?

Both are neck-and-neck — CDNJS and Hunter 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 Hunter?

CDNJS has the lower median latency in our checks — CDNJS responds in 281 ms versus Hunter at 362 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 Hunter need an API key?

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

Can I call CDNJS and Hunter from the browser?

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

Are CDNJS and Hunter free for commercial use?

CDNJS has unclear commercial terms, and Hunter 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.