Data attribution and terms of use

This content is not available in your language yet.

The attribution header

Every response built on satellite data carries:

X-Data-Attribution: Contains modified Copernicus Sentinel data 2026

Copernicus Sentinel data is free and open, and commercial use of derived products - including reselling them - is permitted, on one condition: the attribution travels with the data. When you show, store or redistribute values derived from our API (an NDVI chart in a credit file, a damage percentage in a claim system, a risk class in a portfolio report) keep the sentence “Contains modified Copernicus Sentinel data [year]” next to it. Damage certificates and this documentation carry the same line.

The year in the header is the year of the response; the sentence itself is stable, so a UI can display the header value verbatim.

Sources behind each product

Product	Source	Licence
Indices (NDVI, NDWI, EVI)	Copernicus Sentinel-2 L2A, 10 m	Copernicus Sentinel data terms
SAR events, backscatter, soil moisture	Copernicus Sentinel-1 GRD	Copernicus Sentinel data terms
Thermal, water stress	Copernicus Sentinel-3 SLSTR LST; NASA POWER for the norm	Copernicus terms; NASA POWER is public domain
Weather forecast, history, indicators	Open-Meteo (ECMWF, national models), NASA POWER	provider terms; history from 1981
Parcels, cadastre lookup	LT Registru centras / LPIS, LV Kadastrs, PL GUGiK	the respective national open data licences
Risk, yield, damage, CAP, parametric index	derived from the sources above plus national CAP rules	our methodology, versioned in `method_version`

What the numbers are

Our values are derived satellite estimates, not ground measurements. They come with the metadata needed to argue with them - quality, valid_pct, confidence, method_version, config_hash, the scenes used - and they are withheld (value: null with a reason, or a 422) rather than guessed when the record does not support a number. Agrovisio is not responsible for decisions taken on the basis of the data; the decision remains yours.

A damage certificate is a technical report produced by a documented, versioned methodology and reproducible from the stored result. It is not an expert’s opinion in the legal sense and does not replace a loss adjuster where the policy requires one.

Method versions are never changed retroactively. A recomputation with new thresholds gets a new method_version; a score, an evaluation or an assessment quoted a year ago can be reproduced from its method_version, config_hash and scene ids.

Your obligations

Lawful basis. You must have a lawful basis to monitor every parcel you register (a loan agreement, an insurance policy, a service contract with the holding). A parcel geometry with a cadastral number can identify a natural person and is treated as personal data.
No names in identifiers. external_ref is your identifier, not the farmer’s name. Send a policy or contract number. We never store borrower or policyholder names, and the API has no field for them.
Data processing agreement. Agrovisio acts as data processor and you as data controller; a DPA is signed before a live key is issued. All processing and storage happens in the EU.
Deletion. On request every parcel and result of your account is deleted within 30 days. The satellite cache keyed by geometry hash is not linked to any client and is kept.
Aggregated improvement. We may use anonymised, aggregated results to improve methodologies and to build the reference populations that percentile ranks are computed against. No client-identifiable data is shared.

Service levels

	Starter / Growth	Scale / Enterprise
Availability (monthly)	99.0 %	99.5 % with credits
p95 latency, standard reads	< 800 ms	< 400 ms
Sentinel-2 / Sentinel-1 freshness	< 48 h after the scene	< 24 h
Support response	2 business days	4 business hours
Version support after deprecation notice	12 months	24 months

SLA credits: below 99.5 % availability 10 % of the monthly fee, below 99.0 % 25 %. Live status is on /status; incidents are announced on status.agrovisio.ai.

Versioning

The API version is in the path (/v1/). Adding a field is never a breaking change - clients must ignore unknown fields. Removing a field or changing its meaning gets a new version, announced at least 12 months before the old one is switched off. From the announcement on, every response of the deprecated version - success or error - carries the standard headers:

Deprecation: @1798761600                       # RFC 9745, when it was announced
Sunset: Mon, 01 Jan 2029 00:00:00 GMT          # RFC 8594, when it stops answering
Link: <https://docs.agrovisio.ai/changelog>; rel="deprecation",
      <https://api.agrovisio.ai/v2>; rel="successor-version"

/v1/openapi.json mirrors this in x-agrovisio-lifecycle (today: deprecated: false, minimum_notice_days: 365) and flags every operation deprecated: true once a version is retired. A supported version sends none of these headers, so a warning in your logs when they appear is a safe default. method_version changes independently of the API version and is returned with every computed result. Changes are listed in the changelog and its RSS feed.