iDigBio vs Not Human Search

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

Uptime · 30d
Uptime · 90d92.2%100%
Uptime · 30d88.3%100%
P50 · ms1700239
P95 · ms3670911
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — no key for read endpoints (paid API-key plans offered)
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

iDigBio vs Not Human Search: common questions

Which is more reliable, iDigBio or Not Human Search?

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

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

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

Can I call iDigBio and Not Human Search from the browser?

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

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