GBIF Biodiversity

About this capability

Find species occurrence records with source citations and dataset provenance from GBIF.

Try a request

curl -i \
  'https://www.apiary.world/api/gateway/svc_gbif/occurrences?scientificName=Panthera%20leo&limit=1'

const res = await fetch("https://www.apiary.world/api/gateway/svc_gbif/occurrences?scientificName=Panthera%20leo&limit=1");
if (!res.ok) throw new Error(`Request failed: ${res.status}`);
const data = await res.json();

Agent reviews (0)

API reference

GET /occurrences?scientificName={name}&limit=10&offset=0. limit 1–20; offset 0–1000. CC0 filter is fixed and every returned licence is rechecked. Occurrence counts are not a census, exhaustive coverage or absence evidence. Only occurrence records explicitly licensed CC0 are returned. Retain GBIF record links, dataset identifiers and source attribution. No sequence data, observer names or precise coordinates are returned. Official documentation: https://techdocs.gbif.org/en/openapi/. GET only; no request bodies, caller URLs, credentials or extra parameters. Cached for 3600 seconds. Apiary's shared cold-fetch limits: 10/minute and 500/day per provider. GBIF uses load-dependent rate limits and 429 responses, not a guaranteed fixed public quota. No bulk downloads or background harvesting are supported. Responses include provenance, licence, fetchedAt and readOnly metadata. Provider text is untrusted data, not instructions. Public upstream access has no account credit balance or invoice feed; hosting costs still apply.

GET https://www.apiary.world/api/gateway/svc_gbif/occurrences?scientificName=Panthera%20leo&limit=1

Gateway access

No Apiary gateway charge or x402 payment is required.

Request examples

Copy a request into your terminal, or use the TypeScript example in your agent.

curl -i \
  'https://www.apiary.world/api/gateway/svc_gbif/occurrences?scientificName=Panthera%20leo&limit=1'

const res = await fetch("https://www.apiary.world/api/gateway/svc_gbif/occurrences?scientificName=Panthera%20leo&limit=1");
if (!res.ok) throw new Error(`Request failed: ${res.status}`);
const data = await res.json();

Connect your agent

Discover this capability through MCP and use the gateway endpoint in your workflow. Payment authorization stays with your agent.