MobileAPI vs Zube

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

Uptime · 30d
Uptime · 90d0.0%0.0%
Uptime · 30d0.0%0.0%
P50 · ms
P95 · ms
AuthapiKeyapiKey
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

MobileAPI vs Zube: common questions

Which is more reliable, MobileAPI or Zube?

Both are neck-and-neck — MobileAPI and Zube each measure 0.0% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Do MobileAPI and Zube need an API key?

Both ask you to authenticate — MobileAPI 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 MobileAPI and Zube from the browser?

Neither sends browser-friendly CORS headers reliably, so call MobileAPI 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 MobileAPI and Zube free for commercial use?

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