JSONPlaceholder vs US Autocomplete

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

Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%98.3%
P50 · ms401683
P95 · ms10961917
AuthnoneapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limit1000 req/window · 999 remaining · resets 1783509378Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

JSONPlaceholder vs US Autocomplete: common questions

Which is more reliable, JSONPlaceholder or US Autocomplete?

On our scheduled checks, JSONPlaceholder leads on measured uptime — JSONPlaceholder 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, JSONPlaceholder or US Autocomplete?

JSONPlaceholder has the lower median latency in our checks — JSONPlaceholder responds in 401 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 JSONPlaceholder and US Autocomplete need an API key?

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

Can I call JSONPlaceholder and US Autocomplete from the browser?

Yes — both JSONPlaceholder 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 JSONPlaceholder and US Autocomplete free for commercial use?

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