GBIF vs Not Human Search

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms737239
P95 · ms1691911
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

GBIF vs Not Human Search: common questions

Which is more reliable, GBIF or Not Human Search?

Both are neck-and-neck — GBIF and Not Human Search 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, GBIF or Not Human Search?

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

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

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

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