OpenAlex vs Open Notify

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesyes
HTTPSyesno
Card requirednono
Commercial useyesunclear
Data licenseCC0n/a
Free tierFree tier (~$1/day of usage); free API key available for moreUnlimited (volunteer-run)
Rate limitUsage-metered free tier (~$1/day per docs)Please be gentle
In directory since2026-07-052026-05-02
operationalpartialdownno data

OpenAlex vs Open Notify: common questions

Which is more reliable, OpenAlex or Open Notify?

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

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

Can I call OpenAlex and Open Notify 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 OpenAlex and Open Notify free for commercial use?

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