RubyGems vs US Autocomplete

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

Uptime · 30d
Uptime · 90d99.02%99.02%
Uptime · 30d98.3%98.3%
P50 · ms311683
P95 · ms16391917
AuthnoneapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

RubyGems vs US Autocomplete: common questions

Which is more reliable, RubyGems or US Autocomplete?

Both are neck-and-neck — RubyGems and US Autocomplete each measure 99.02% 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, RubyGems or US Autocomplete?

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

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

Can I call RubyGems and US Autocomplete from the browser?

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

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