shipapis
StarSubmit an APISubmit API

Fake JSON API vs RubyGems

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

APIFake JSON APIHEALTHY88RubyGemsHEALTHY94
Uptime · 30d
Uptime · 90d99.02%99.02%
Uptime · 30d98.3%98.3%
P50 · ms865311
P95 · ms20061639
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Fake JSON API vs RubyGems: common questions

Which is more reliable, Fake JSON API or RubyGems?

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

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

Neither needs a paid key — Fake JSON API 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 Fake JSON API and RubyGems from the browser?

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

Fake JSON API 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.