Kaggle vs Mediastack

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms250449
P95 · ms5661356
AuthapiKeyapiKey
CORSyesno
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

Kaggle vs Mediastack: common questions

Which is more reliable, Kaggle or Mediastack?

Both are neck-and-neck — Kaggle and Mediastack 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, Kaggle or Mediastack?

Kaggle has the lower median latency in our checks — Kaggle responds in 250 ms versus Mediastack at 449 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 Kaggle and Mediastack need an API key?

Both ask you to authenticate — Kaggle 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 Kaggle and Mediastack from the browser?

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

Are Kaggle and Mediastack free for commercial use?

Kaggle 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.