OpenAlex vs SHARE

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

Uptime · 30d
Uptime · 90d1.0%100%
Uptime · 30d1.7%100%
P50 · ms3167353
P95 · ms3167759
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useyesunclear
Data licenseCC0Unverified
Free tierFree tier (~$1/day of usage); free API key available for moreFree — limits not published
Rate limitUsage-metered free tier (~$1/day per docs)Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

OpenAlex vs SHARE: common questions

Which is more reliable, OpenAlex or SHARE?

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

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

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

Can I call OpenAlex and SHARE from the browser?

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

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