shipapis
StarSubmit an APISubmit API

RubyGems vs VerifyEd

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

APIRubyGemsNEW—VerifyEdNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublished100 req/window · 99 remaining · resets 1783522020
In directory since2026-07-052026-07-05
operationalpartialdownno data

RubyGems vs VerifyEd: common questions

Which is more reliable, RubyGems or VerifyEd?

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

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

Can I call RubyGems and VerifyEd from the browser?

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

Are RubyGems and VerifyEd free for commercial use?

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