shipapis
StarSubmit an APISubmit API

HTTPie vs RubyGems

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

APIHTTPieNEW—RubyGemsNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
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

HTTPie vs RubyGems: common questions

Which is more reliable, HTTPie or RubyGems?

On our scheduled checks, RubyGems leads on measured uptime — HTTPie at —% versus RubyGems 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 HTTPie and RubyGems need an API key?

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

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

Are HTTPie and RubyGems free for commercial use?

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