Currents vs Micro User Service

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeyapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Currents vs Micro User Service: common questions

Which is more reliable, Currents or Micro User Service?

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

Both ask you to authenticate — Currents uses an API key and Micro User Service 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 Currents and Micro User Service from the browser?

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

Are Currents and Micro User Service free for commercial use?

Currents has unclear commercial terms, and Micro User Service 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.