Open Notify vs OpenAlex

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

Uptime · 30d
Uptime · 90d71.6%1.0%
Uptime · 30d65.0%1.7%
P50 · ms2413167
P95 · ms42983167
Authnonenone
CORSyesyes
HTTPSnoyes
Card requirednono
Commercial useunclearyes
Data licensen/aCC0
Free tierUnlimited (volunteer-run)Free tier (~$1/day of usage); free API key available for more
Rate limitPlease be gentleUsage-metered free tier (~$1/day per docs)
In directory since2026-05-022026-07-05
operationalpartialdownno data

Open Notify vs OpenAlex: common questions

Which is more reliable, Open Notify or OpenAlex?

On our scheduled checks, Open Notify leads on measured uptime — Open Notify at 71.6% versus OpenAlex at 1.0% 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, Open Notify or OpenAlex?

Open Notify has the lower median latency in our checks — Open Notify responds in 241 ms versus OpenAlex at 3167 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 Open Notify and OpenAlex need an API key?

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

Can I call Open Notify and OpenAlex from the browser?

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

Are Open Notify and OpenAlex free for commercial use?

Open Notify has unclear commercial terms, and OpenAlex allows commercial use on its free tier. 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.