Currents vs Open Data Minneapolis

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
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

Currents vs Open Data Minneapolis: common questions

Which is more reliable, Currents or Open Data Minneapolis?

On our scheduled checks, Open Data Minneapolis leads on measured uptime — Currents at —% versus Open Data Minneapolis 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 Open Data Minneapolis need an API key?

Open Data Minneapolis needs no key, while Currents requires a free API key. If you want to start calling without signup, reach for Open Data Minneapolis first.

Can I call Currents and Open Data Minneapolis from the browser?

Only Open Data Minneapolis 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 Open Data Minneapolis free for commercial use?

Currents has unclear commercial terms, and Open Data Minneapolis 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.