Verify Plant Names
Endpoints
Verify Plant Names
Validate botanical species names against 11 authoritative taxonomic databases with AI fallback. Queries GBIF, TNRS (WFO), POWO (Kew), iNaturalist, EOL, ALA, IP Australia PBR, UPOV, WikiSpecies, Wikidata, and Wikipedia in parallel. Returns unified taxonomic records with consensus scoring. Accepts input as: (1) JSON body with species_names array, (2) JSON body with file_url from TUS upload, or (3) multipart form-data with direct file upload.
POST
Verify Plant Names
Validate botanical species names against 11 authoritative taxonomic databases with Gemini AI fallback. Returns unified taxonomic records with consensus scoring.
Overview
This endpoint queries 11 botanical databases in parallel, consolidates results using a weighted consensus algorithm, and returns a unified taxonomic record per species. Names that no source can resolve are sent to Google Gemini AI as a corrective fallback. Sources queried: GBIF, TNRS (WFO), POWO (Kew), iNaturalist, EOL, ALA, IP Australia PBR, UPOV, WikiSpecies, Wikidata, Wikipedia.Input Options
This endpoint accepts input in three ways:1. JSON Body with Species Names Array
2. JSON Body with File URL (TUS Upload)
For files uploaded via TUS protocol. Names are pre-parsed by LLM, so no additional extraction is performed.3. Direct File Upload (Multipart)
Upload files directly without TUS:Request Body (JSON)
An array of species name strings to validate. Takes precedence over file inputs.
URL to a previously uploaded file (from TUS storage). Names are pre-parsed via LLM.Tip: You can use the file input dialog in this playground to test with a local file.
Original filename for context when using
file_url.Specific column name containing species names in spreadsheet files.
Specific sources to query. Defaults to all 11 non-Gemini sources. Gemini is always a fallback-only source.Available:
gbif, tnrs, powo, inaturalist, eol, ala, ip_australia, upov, wikispecies, wikidata, wikipediaInclude detailed taxonomic metadata in results.
Cache validation results for future queries.
Form Data (Multipart Upload)
Direct file upload. Supports: JSON, XLSX, XLS, CSV, PDF, TXT.
Column name containing species names for spreadsheet files.
Response
The response contains an array of unified taxonomic records and a summary.Array of unified taxonomic records, one per species name.
Batch validation summary.
Example Response
Authentication
Your API key for Basic/Pro plan authentication.
Bearer token for Teams plan platform integration.
Supported File Formats
| Format | Extension | Description |
|---|---|---|
| JSON | .json | Direct arrays of species names |
| Excel | .xlsx, .xls | Spreadsheets with species columns |
| CSV | .csv | Comma-separated values |
.pdf | Text extraction from documents | |
| Text | .txt | One species per line or comma-separated |
Error Handling
| Status Code | Description |
|---|---|
| 200 | Success |
| 400 | Bad request (invalid input, missing species names, invalid source) |
| 401 | Unauthorized (invalid or missing API key) |
| 403 | Forbidden (API key inactive, expired, or usage limit exceeded) |
| 500 | Internal server error |
Rate Limits
- API usage is tracked per API key
- Each species name processed counts as 1 usage unit
- Rate limits vary by subscription plan
- Batch processing is more efficient for large datasets
Authorizations
Standard API Key authentication.
Body
Object containing species names to validate or file reference.

