shipapis
StarSubmit an APISubmit API

RubyGems vs What The Commit

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

APIRubyGemsHEALTHY94What The CommitHEALTHY79
Uptime · 30d
Uptime · 90d99.02%99.02%
Uptime · 30d98.3%98.3%
P50 · ms3111312
P95 · ms16394279
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?

Both are neck-and-neck — RubyGems and What The Commit 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 What The Commit?

RubyGems has the lower median latency in our checks — RubyGems responds in 311 ms versus What The Commit at 1312 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 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.