shipapis
StarSubmit an APISubmit API

RubyGems vs What The Commit

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

APIRubyGemsNEW—What The CommitNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesno
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

RubyGems vs What The Commit: common questions

Which is more reliable, RubyGems or What The Commit?

On our scheduled checks, What The Commit leads on measured uptime — RubyGems at —% versus What The Commit at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do RubyGems and What The Commit need an API key?

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

Can I call RubyGems and What The Commit from the browser?

Only RubyGems is browser-friendly — it returns CORS headers over HTTPS. What The Commit needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are RubyGems and What The Commit free for commercial use?

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