> ## Documentation Index
> Fetch the complete documentation index at: https://docs.verdant-ai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Climate data with its evidence intact

> Query versioned climate data through one contract, directly from HTTP or an agent.

Verdant serves climate data with explicit units, spatial support, missingness, and source lineage. An agent describes the data it needs; the response includes the values and the evidence needed to interpret them.

Daily maximum and minimum temperature and precipitation are available for Australia from SILO, the contiguous United States from NOAA nClimGrid-Daily, and global land from NOAA CPC. Published versions are served directly; anything not published yet is acquired from the source on request. The catalog also includes study evidence such as CSIRO observed irrigation programs (2003–2005). Different datasets have different meanings and are not interchangeable.

<Steps>
  <Step title="Discover">Read capabilities and the dataset catalog to learn which operations and coverage actually exist.</Step>
  <Step title="Resolve">Check a query against published data. Pin the returned immutable dataset version.</Step>
  <Step title="Query">Receive data directly as JSON or CSV, with provenance and checksums.</Step>
</Steps>

<CardGroup cols={2}>
  <Card title="Make your first query" icon="terminal" href="/quickstart">Return real climate values in an HTTP response.</Card>
  <Card title="Connect an agent" icon="robot" href="/agents/mcp">Use Mintlify documentation search and Verdant data tools.</Card>
</CardGroup>

<Note>
  Reading published data is free and needs no API key. New data is acquired, validated and published asynchronously, paid per acquisition with MPP (see the [request lifecycle](/concepts/request-lifecycle)). The capabilities endpoint is the authoritative feature inventory; valid syntax alone does not mean data is available.
</Note>

The [OpenAPI 3.1 specification](https://api.verdant-ai.com/api/v1/openapi.json) and this reference are generated from the same shared runtime schemas. `/api/v1` defines the major contract version. Additive fields may appear; clients should ignore fields they do not recognize.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.