GBIF vs OpenAlex

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

Uptime · 30d
Uptime · 90d100%1.0%
Uptime · 30d100%1.7%
P50 · ms7373167
P95 · ms16913167
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedCC0
Free tierFree — limits not publishedFree tier (~$1/day of usage); free API key available for more
Rate limitUnpublishedUsage-metered free tier (~$1/day per docs)
In directory since2026-07-052026-07-05
operationalpartialdownno data

GBIF vs OpenAlex: common questions

Which is more reliable, GBIF or OpenAlex?

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

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

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

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

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