Steps

POST https://openet-api.org/geodatabase/metadata/ids with a geometry array of [lon,lat,lon,lat,...] polygon vertices (or an asset_id) to get every OpenET field id whose boundary intersects the polygon; the response is delivered as a compressed .zip.
As of December 2025, field ids are 11-digit numeric codes; pass version: 2.0 only if you need the older FIPS-prefixed id format for legacy compatibility.
POST https://openet-api.org/geodatabase/metadata/properties with those field_ids to get each field's area (hectares), USDA CDL crop-type code by year, and last-modified date.
POST https://openet-api.org/geodatabase/timeseries with date_range, interval ("monthly"), field_ids, models (e.g. ["ensemble"]), variables (e.g. ["et","eto","etof"]), and file_format ("json" for large field lists, since csv isn't practical at scale) to get precomputed monthly series per field.
POST https://openet-api.org/geodatabase/metadata/boundaries with field_ids if you need back RFC 7946 GeoJSON geometries to render or re-verify the field boundaries.

Known gotchas

A single geodatabase/timeseries query only returns data from one US state at a time, even though multi-model/multi-variable requests are supported — a farm boundary straddling a state line needs two separate calls.
Data in the geodatabase is stored in metric units (mm, hectares) regardless of the units you might request from the raster/point endpoint — don't assume unit consistency across OpenET's two API families.

Retrieve field-level evapotranspiration time series via the OpenET API.

Create, update, and query field, farm, and boundary records across connected ag equipment brands using Leaf Agriculture's Field Boundary Management API.

docs.withleaf.io · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Look up OpenET agricultural field IDs within a farm boundary and pull precomputed ET timeseries for those fields

Steps

Known gotchas

Related routes

Give your agent this knowledge — and 15,500+ more routes

Need this verified for your stack — or a route we don't have yet?