Wikipedia REST vs Zenodo

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useyesunclear
Data licenseCC BY-SA 4.0Unverified
Free tierUnlimited within etiquetteFree — limits not published
Rate limit200/sec global courtesy cap30 req/window · 29 remaining · resets 1783516620
In directory since2026-05-092026-07-05
operationalpartialdownno data

Wikipedia REST vs Zenodo: common questions

Which is more reliable, Wikipedia REST or Zenodo?

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

Neither needs a paid key — Wikipedia REST is callable with no signup, and Zenodo is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Wikipedia REST and Zenodo from the browser?

Yes — both Wikipedia REST and Zenodo send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are Wikipedia REST and Zenodo free for commercial use?

Wikipedia REST allows commercial use on its free tier, 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.