GBIF vs iDigBio

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

GBIF vs iDigBio: common questions

Which is more reliable, GBIF or iDigBio?

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

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

Can I call GBIF and iDigBio from the browser?

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

GBIF has unclear commercial terms, and iDigBio 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.