shipapis
StarSubmit an APISubmit API

RubyGems vs Screenshotbase

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

APIRubyGemsHEALTHY94ScreenshotbaseDEAD0
Uptime · 30d
Uptime · 90d99.44%0.0%
Uptime · 30d100%0.0%
P50 · ms184—
P95 · ms1639—
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

RubyGems vs Screenshotbase: common questions

Which is more reliable, RubyGems or Screenshotbase?

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

RubyGems needs no key, while Screenshotbase requires a free API key. If you want to start calling without signup, reach for RubyGems first.

Can I call RubyGems and Screenshotbase from the browser?

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

Are RubyGems and Screenshotbase free for commercial use?

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