shipapis
StarSubmit an APISubmit API

DummyJSON vs RubyGems

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

APIDummyJSONHEALTHY98RubyGemsHEALTHY94
Uptime · 30d
Uptime · 90d99.02%99.02%
Uptime · 30d100%98.3%
P50 · ms32311
P95 · ms11131639
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no keyFree — limits not published
Rate limit100 req/window · 99 remaining · resets 1783510243Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

DummyJSON vs RubyGems: common questions

Which is more reliable, DummyJSON or RubyGems?

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

DummyJSON has the lower median latency in our checks — DummyJSON responds in 32 ms versus RubyGems at 311 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 DummyJSON and RubyGems need an API key?

Neither needs a paid key — DummyJSON is callable with no signup, and RubyGems is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call DummyJSON and RubyGems from the browser?

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

DummyJSON has unclear commercial terms, and RubyGems 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.