Skip to main content
You can start using the Climatifai API without registering or sending any authentication headers. Most endpoints are publicly accessible — just point your requests at your API host. The examples below use https://your-api-host as a placeholder; replace it with the base URL of your deployment.
1

Check the API is running

Send a GET request to /health to confirm the service is up.
A healthy instance returns:
If you receive a connection error, verify that the host and port are correct and that the service has started.
2

Get a crop aptitude score

The /agri/advisor endpoint scores how well a specific crop fits the climate at a given location. Pass a latitude, longitude, crop ID, and season.
The response includes a 0–100 score, an aptitude label, a per-factor breakdown, and a recommendation in Spanish:
Supported crop_id values: maiz, trigo, cafe, soya, vid, frijol, papa, arroz, cana, tomate, cebolla, ajo, girasol, sorgo, algodon, quinua, aguacate. English aliases such as maize, wheat, and coffee are also accepted.Supported season values: annual, lluvias (wet season), secas (dry season).
3

Get fire hotspots near a location

The /fires/hotspots endpoint returns active fire detections from NASA FIRMS VIIRS within a radius around your coordinates. The lookback window is 1–5 days.
The response lists each detected hotspot with its coordinates, fire radiative power (FRP), acquisition time, satellite, and confidence level:
The source parameter defaults to VIIRS_SNPP_NRT. The server supplies the NASA FIRMS API key — you do not need one.
4

Try the GraphQL playground

The API includes a fully interactive GraphiQL playground at /graphql. Open it in your browser to explore all available queries, including advisor, climate, hotspots, fireRisk, alerts, compare, and more.
Here is a sample query to score a crop and check fire risk in one request:
The playground provides schema documentation in the sidebar and autocomplete as you type.