shipapis
StarSubmit an APISubmit API

Currents vs Mediastack

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

APICurrentsNEW—MediastackNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeyapiKey
CORSnono
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 Mediastack: common questions

Which is more reliable, Currents or Mediastack?

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

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

Neither sends browser-friendly CORS headers reliably, so call Currents and Mediastack from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are Currents and Mediastack free for commercial use?

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