Bootprint vs GBIF

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms67737
P95 · ms2911691
Authnonenone
CORSnoyes
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

Bootprint vs GBIF: common questions

Which is more reliable, Bootprint or GBIF?

Both are neck-and-neck — Bootprint and GBIF each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, Bootprint or GBIF?

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

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

Can I call Bootprint and GBIF from the browser?

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

Are Bootprint and GBIF free for commercial use?

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