Voidly vs Zenodo

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

Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%100%
P50 · ms12381698
P95 · ms38944935
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useyesunclear
Data licenseCC BY 4.0Unverified
Free tierFree (keyless data endpoints; Hydra ML endpoints need a key)Free — limits not published
Rate limitUnpublished30 req/window · 29 remaining · resets 1783516620
In directory since2026-07-052026-07-05
operationalpartialdownno data

Voidly vs Zenodo: common questions

Which is more reliable, Voidly or Zenodo?

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

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

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

Yes — both Voidly 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 Voidly and Zenodo free for commercial use?

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