shipapis
StarSubmit an APISubmit API

Numverify vs RubyGems

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

APINumverifyHEALTHY93RubyGemsHEALTHY94
Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%98.3%
P50 · ms449311
P95 · ms14881639
AuthapiKeynone
CORSnoyes
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

Numverify vs RubyGems: common questions

Which is more reliable, Numverify or RubyGems?

On our scheduled checks, Numverify leads on measured uptime — Numverify 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, Numverify or RubyGems?

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

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

Can I call Numverify and RubyGems from the browser?

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

Are Numverify and RubyGems free for commercial use?

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