Crawlee vs Zenodo

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

Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%100%
P50 · ms4801698
P95 · ms12934935
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublished30 req/window · 29 remaining · resets 1783516620
In directory since2026-07-052026-07-05
operationalpartialdownno data

Crawlee vs Zenodo: common questions

Which is more reliable, Crawlee or Zenodo?

On our scheduled checks, Crawlee leads on measured uptime — Crawlee 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, Crawlee or Zenodo?

Crawlee has the lower median latency in our checks — Crawlee responds in 480 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 Crawlee and Zenodo need an API key?

Neither needs a paid key — Crawlee 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 Crawlee and Zenodo from the browser?

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

Are Crawlee and Zenodo free for commercial use?

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