Data API for IT and data teams
Register, copy a sandbox key, call the API. Twenty Lithuanian parcels with five years of modelled history are already there — synthetic but phenologically realistic and clearly marked, so you can build the whole integration before you go live; live keys return measured data. No sales call, no card.
Create parcels by GeoJSON polygon or cadastral number, bulk import as an async job. NDVI, NDWI and EVI at 10 m with cloud masking, a quality class per observation and a five-year baseline; batch calls for up to 500 parcels.
When radar scenes are available, a sharp change seen through cloud is flagged as a beta signal of possible lodging, harvest, mowing, tillage or regrowth, with its evidence scenes. Detection thresholds are still being calibrated, so check the signal in the field. Backscatter series and relative soil moisture.
Seven-day forecast, daily history from 1981 and seasonal agroclimate per parcel. Land surface temperature and a water-stress index from Sentinel-3 at ~1 km, for parcels from 5 ha; smaller ones get 422 insufficient_resolution.
Expected yield per parcel with a confidence interval, updated as the season develops.
A 0–100 parcel score with named components and weights, ranked portfolio lists, aggregated summaries and batch refresh. Model version in every answer.
Async pre/post assessment for storm, hail, drought and flood: damage percentage with interval, affected hectares, severity zones and a sha256-verifiable PDF certificate from confidence 0.50.
Direct payment and eco-scheme calculation and optimisation across a holding, crop rotation checks; parametric triggers drafted, backtested over past seasons, published and evaluated per season.
Long operations return 202 and finish with an HMAC-SHA256-signed webhook; Idempotency-Key on every POST. Sandbox key in minutes, two live keys with rotation and an IP allowlist, usage and billing in the portal; going live is approved by Agrovisio.
Technical facts you can check against the sandbox before you sign anything.
20 parcels
Twenty shared Lithuanian parcels with five years of modelled history and five prepared damage cases. Never billed.
method_version and config_hash on every analytical answerMethods are versioned independently of the API and never altered retroactively, so a historical call stays reproducible.
insufficient_data instead of a guessMasked observations are null with a reason; unsupported assessments end in an explicit state and are not billed.
12 months
Versioned URL path, additive changes only within a version, a Sunset header before removal. Python and TypeScript SDKs, Postman and OpenAPI 3.1 come from the same document.
Public and the same for everyone. You pay for the monthly peak of monitored parcels, never for requests. An annual contract carries a 15 % discount.
Sandbox
0 EUR
free, no card, never billed
Starter
490 EUR
per month
Growth
1 900 EUR
per month
Scale
4 900 EUR
per month
Enterprise
from 9 000 EUR
per month, contract
The only charges on top of the plan. The unit price is fixed at the moment of the event and written into the usage record, so a later price change never rewrites history.
| Unit | Price | When it is charged |
|---|---|---|
| Damage assessment | 35 EUR per assessment | Enterprise: 22 EUR from the 500th assessment in a calendar year. Charged only when the job completes with confidence of at least 0.40. |
| Damage certificate (PDF) | Included | Issued when confidence is at least 0.50. Not a separate charge. |
| Historical backfill | 0.03 EUR per parcel per year of history | Beyond the history included with a live parcel. |
| Parametric index definition | 600 EUR per index per year | Charged once, at publish. Backtests included. |
| Integration support | 1 200 EUR one-off | Optional. Waived on an annual contract. |
| Dedicated environment | 1 500 EUR per month | Enterprise option. |
All prices exclude VAT. You enter your billing details in the portal and pay by invoice. Going live is a request in the portal that Agrovisio approves; until then every call runs on the free sandbox.
Three rules cover the whole invoice. They are the same rules the API applies in GET /v1/account, so you can see the number before the invoice does.
Once a day we count your active parcels and keep the maximum for the period: parcels_peak = MAX(parcels_peak, active). The parcel line on the invoice uses that peak, not an average. Deleting parcels frees quota for new ones but does not lower a peak already reached, so import what you intend to monitor.
Damage assessments, backfill years and published index definitions are the only metered actions. Each is written as a usage event with its price before the response is sent, and Idempotency-Key replays return the stored result without a second charge.
Anything done with a sandbox key. Ordinary API calls, however many. Damage assessments that end as insufficient_data or below confidence 0.40. Retries that replay an Idempotency-Key. Calls that never reach an endpoint (403, 422, 429).
You do not need this form to start: the sandbox key comes from the portal. Write to us for volume above the Scale plan, a dedicated environment, a data-processing agreement or a product you need that is not listed.
Mention the number of parcels and the products you intend to use.