CDNJS vs US Autocomplete

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

Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%98.3%
P50 · ms281683
P95 · ms9361917
AuthnoneapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree and open, no keyFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

CDNJS vs US Autocomplete: common questions

Which is more reliable, CDNJS or US Autocomplete?

On our scheduled checks, CDNJS leads on measured uptime — CDNJS at 100% versus US Autocomplete at 99.02% 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, CDNJS or US Autocomplete?

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

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

Can I call CDNJS and US Autocomplete from the browser?

Yes — both CDNJS and US Autocomplete send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are CDNJS and US Autocomplete free for commercial use?

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