Lookup.im API vs Zenodo

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

Uptime · 30d
Uptime · 90d99.02%99.02%
Uptime · 30d100%100%
P50 · ms11581698
P95 · ms35814935
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublished30 req/window · 29 remaining · resets 1783516620
In directory since2026-07-052026-07-05
operationalpartialdownno data

Lookup.im API vs Zenodo: common questions

Which is more reliable, Lookup.im API or Zenodo?

Both are neck-and-neck — Lookup.im API and Zenodo each measure 99.02% 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, Lookup.im API or Zenodo?

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

Zenodo needs no key, while Lookup.im API requires a free API key. If you want to start calling without signup, reach for Zenodo first.

Can I call Lookup.im API and Zenodo from the browser?

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

Are Lookup.im API and Zenodo free for commercial use?

Lookup.im API 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.