Bootprint vs iDigBio

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

Uptime · 30d
Uptime · 90d100%92.2%
Uptime · 30d100%88.3%
P50 · ms671700
P95 · ms2913670
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 iDigBio: common questions

Which is more reliable, Bootprint or iDigBio?

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

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

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

Only iDigBio 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 iDigBio free for commercial use?

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