Consuming AgInsights APIs 🌱
Overview
AgInsights APIs provide science-based agronomic model predictions using satellite imagery, weather data, and machine learning trained on extensive agricultural datasets. All models use a unified endpoint architecture where you send field data and specify which predictions you need.
When to Use
AgInsights APIs are designed for agricultural technology providers, agronomists, and farm management platforms who need:
- Crop growth stage predictions - Track phenological development to optimize spray timing, fertilizer application, and harvest planning
- Yield predictions - Estimate relative yield potential for variable rate applications and harvest logistics
- Productivity zones mapping - Create management zones for variable rate applications and targeted interventions
- Field variability analysis - Assess uniformity patterns to enable precision agriculture practices
- Seed density recommendations - Determine optimal seeding rates based on field characteristics
Use these APIs when you have field location data and need agronomic predictions without building and maintaining your own models.
How It Works

The unified prediction endpoint processes:
- Field location (Point coordinates)
- Crop information (type, variety, planting date)
- Model selection (one or more models per request)
- Optional parameters (soil, irrigation, historical periods)
Returns structured predictions with confidence metrics and temporal information.
Available Models
| Model | Purpose | Model Card |
|---|---|---|
| Growth Stage | Phenological stage predictions | Details |
| Relative Yield | Yield potential estimates | Details |
| Productivity Zones | Field variability mapping | Details |
| Seed Density | Seeding rate recommendations | Details |
| Variability Index | Field uniformity analysis | Details |
API Documentation
For complete API reference including request/response schemas, authentication, and interactive testing:
📚 AgInsights API Documentation - Unified interactive API documentation with examples for all models
The unified API documentation includes:
- All 5 model types with request/response examples
- Model-specific payload structures
- Authentication requirements
- Error codes and handling
- Interactive testing interface
Unified Endpoint
All agronomic model predictions use a single endpoint:
| Attribute | Value |
|---|---|
| Base URL | https://api.insights.cropwise.com |
| Endpoint | /v2.0/predictions |
| Method | POST |
| Content-Type | application/json |
| Authentication | Bearer token (see Cropwise Authentication) |
Prerequisites
Before using AgInsights APIs:
- Authentication - Obtain access token via Cropwise Authentication
- Field Data - Retrieve field coordinates using Fields API
- Crop Information - Fetch crop type and planting date using Crops API
- Model Selection - Review model cards to select appropriate models
Best Practices
| Practice | Benefit |
|---|---|
| Batch multiple fields per request | Reduce API calls and improve throughput |
| Cache predictions with timestamps | Avoid redundant requests for same field/date |
| Check model-specific requirements | Each model has unique optional parameters |
Common Use Cases
Growth Stage Tracking
Predict when corn reaches V6 stage for side-dress nitrogen application.
See the Growth Stage - Corn example in the AgInsights API documentation for complete request/response details.
Yield Potential Mapping
Estimate relative yield across fields to plan harvest logistics.
See the Relative Yield example in the AgInsights API documentation for complete request/response details.
Management Zone Creation
Generate productivity zones for variable rate seeding.
See the Productivity Zones examples in the AgInsights API documentation for complete request/response details.
Error Handling
Standard HTTP status codes:
| Status | Meaning | Action |
|---|---|---|
| 200 | Success | Process prediction results |
| 400 | Bad Request | Validate request parameters against model requirements |
| 401 | Unauthorized | Refresh access token |
| 403 | Forbidden | Verify account has model access |
| 429 | Too Many Requests | Implement backoff and retry later |
Detailed error responses include validation messages for troubleshooting.
Rate Limiting
No specific rate limits currently enforced on AgInsights endpoints. However, underlying Cropwise services may have limits that affect your requests.
For production applications:
- Implement exponential backoff for 429 errors
- Monitor response times and adjust concurrency
- Contact support if consistently hitting limits
Next Steps
Explore these resources to integrate AgInsights predictions:
API Reference - Interactive documentation with all model examples:
- AgInsights Unified API - Complete API documentation with examples for all models
Core Services Integration - Set up farm data:
- Getting Started with Cropwise - Initialize organizations
- Authentication Guide - Obtain access tokens
- Fields API - Manage field geometries
- Best Practices - Integration patterns
Support - Contact Us