Currents vs Datasette

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms586293
P95 · ms1165892
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 Datasette: common questions

Which is more reliable, Currents or Datasette?

Both are neck-and-neck — Currents and Datasette each measure 100% 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.

Which is faster, Currents or Datasette?

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

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

Can I call Currents and Datasette from the browser?

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

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