shipapis
StarSubmit an APISubmit API

VerifyEd vs Zube

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

APIVerifyEdNEW—ZubeNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeyapiKey
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree tier — API key required
Rate limit100 req/window · 99 remaining · resets 1783522020Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

VerifyEd vs Zube: common questions

Which is more reliable, VerifyEd or Zube?

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

Both ask you to authenticate — VerifyEd uses an API key and Zube uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call VerifyEd and Zube from the browser?

Neither sends browser-friendly CORS headers reliably, so call VerifyEd and Zube from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are VerifyEd and Zube free for commercial use?

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