Currents vs Zenodo

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

Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%100%
P50 · ms5861698
P95 · ms11654935
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree — limits not published
Rate limitUnpublished30 req/window · 29 remaining · resets 1783516620
In directory since2026-07-052026-07-05
operationalpartialdownno data

Currents vs Zenodo: common questions

Which is more reliable, Currents or Zenodo?

On our scheduled checks, Currents leads on measured uptime — Currents at 100% versus Zenodo 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, Currents or Zenodo?

Currents has the lower median latency in our checks — Currents responds in 586 ms versus Zenodo at 1698 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 Currents and Zenodo need an API key?

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

Can I call Currents and Zenodo from the browser?

Only Zenodo 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 Zenodo free for commercial use?

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