shipapis
StarSubmit an APISubmit API

OpenQR vs RubyGems

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

APIOpenQRNEW—RubyGemsNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeynone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

OpenQR vs RubyGems: common questions

Which is more reliable, OpenQR or RubyGems?

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

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

Can I call OpenQR and RubyGems from the browser?

Yes — both OpenQR and RubyGems send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are OpenQR and RubyGems free for commercial use?

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