shipapis
StarSubmit an APISubmit API

GBIF vs Replicate

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

APIGBIFNEW—ReplicateNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

GBIF vs Replicate: common questions

Which is more reliable, GBIF or Replicate?

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

GBIF needs no key, while Replicate requires a free API key. If you want to start calling without signup, reach for GBIF first.

Can I call GBIF and Replicate from the browser?

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

Are GBIF and Replicate free for commercial use?

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