shipapis
StarSubmit an APISubmit API

ItsThisForThat vs RubyGems

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

APIItsThisForThatHEALTHY98RubyGemsHEALTHY94
Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%98.3%
P50 · ms242311
P95 · ms5551639
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublished (docs ask you not to hammer it)Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

ItsThisForThat vs RubyGems: common questions

Which is more reliable, ItsThisForThat or RubyGems?

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

Which is faster, ItsThisForThat or RubyGems?

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

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

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

Are ItsThisForThat and RubyGems free for commercial use?

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