Leaf is an API for agricultural data. You connect to farm data providers like John Deere, Climate FieldView, CNHi, Trimble, and AgLeader, and Leaf gives you back clean, standardized data you can actually use.
What Leaf does
Farm machinery generates planting, harvest, application, and tillage data. That data lives in proprietary formats across different provider platforms, each with its own API, authentication flow, and data schema. Leaf handles all of it: pulling data from providers, converting proprietary machine file formats into a standard canonical schema, merging files into field operations, and mapping everything to field boundaries. You retrieve the processed data as GeoJSON or GeoParquet — same structure, your choice of format.
You get a single REST API that returns the same data format regardless of which brand of equipment or software a grower uses.
Who it’s for
Leaf is built for developers at agtech companies, crop insurance providers, farm management platforms, sustainability programs, and managed service providers. If your product needs grower field data from multiple sources, Leaf replaces the work of building and maintaining individual provider integrations.
What you can build
With Leaf, you can pull field boundaries, machine files, and field operations from any connected provider. You can also access satellite imagery (Sentinel and Planet), weather data (historical and forecast), and set up webhooks to react to new data as it arrives.
Common use cases:
- Crop insurance: Automate acreage reporting and production data collection at scale.
- Farm management (FMIS): Import field records, operation maps, and boundaries from all major brands into one platform.
- Sustainability programs: Collect tillage, planting, and application data to populate carbon models or verify practices.
- Managed services: Process data for multiple clients from a single integration.
How data flows through Leaf
At a high level: Providers → Machine files → Conversion → Field operations → Your app.
Growers connect their provider accounts (or upload files directly). Leaf pulls machine files, converts them into a standard canonical format, and merges them with field boundaries to create field operations. The converted data is accessible as either GeoJSON or GeoParquet. You retrieve the processed data through the API or get notified via webhooks.
For a deeper look at this pipeline, see Core Concepts.
What to do next
Last modified on March 24, 2026
