Agromonitoring
Agromonitoring is a technology company specializing in satellite-based agricultural monitoring. Using Sentinel-2 and Landsat imagery combined with weather and soil data, Agromonitoring provides vegetation index time series (NDVI, EVI, DSWI, LSWI), current weather, multi-day forecasts, and soil conditions for registered field polygons. The platform enables precision agriculture workflows including crop health assessment, irrigation optimization, yield prediction, and climate risk monitoring.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Agromonitoring the way a machine reads it — 78 machine-readable artifacts across 6 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Agromonitoring scores 32.8/100 (thin), with a separate agent-readiness read of 31/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-10 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Agromonitoring's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/agromonitoring/"
title="Agromonitoring on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/agromonitoring.svg"
alt="Agromonitoring Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/agromonitoring/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/agromonitoring/"
title="Agromonitoring on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/agromonitoring/card.svg"
alt="Agromonitoring Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Agromonitoring
Each block below is one kind of artifact we hold for Agromonitoring. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 6
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Agromonitoring NDVI History API
Historical NDVI vegetation index data
Agromonitoring Polygons API
Create and manage field polygon definitions
Agromonitoring Satellite Imagery API
Access satellite imagery and vegetation index data
Agromonitoring Soil API
Soil temperature and moisture data
Agromonitoring UV Index API
UV radiation index data
Agromonitoring Weather API
Current, forecast, and historical weather data
Postman Collections 6
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Open Collections 8
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONAgromonitoring Agro NDVI History API
OPEN COLLECTIONAgromonitoring Agro NDVI History Polygons API
OPEN COLLECTIONAgromonitoring Agro NDVI History Satellite Imagery API
OPEN COLLECTIONAgromonitoring Agro NDVI History Soil API
OPEN COLLECTIONAgromonitoring Agro NDVI History UV Index API
OPEN COLLECTIONAgromonitoring Agro NDVI History Weather API
OPEN COLLECTIONAgromonitoring Agro API
OPEN COLLECTIONScroll within the panel for all 8 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Agromonitoring Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Agromonitoring Finops
FINOPSFeatures 7
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Field Polygon Management
Register, retrieve, and delete georeferenced agricultural field polygons using GeoJSON geometry
Satellite Imagery Search
Search Sentinel-2 and Landsat satellite archives for cloud-free imagery over registered fields
Vegetation Index Time Series
Access NDVI, EVI, EVI2, NRI, DSWI, and LSWI historical time series to track crop health and stress
Current Weather Data
Real-time weather conditions including temperature, humidity, wind speed, pressure, and cloud cover
Weather Forecasting
Multi-day weather forecasts to support irrigation scheduling and field operation planning
Soil Monitoring
Soil temperature at surface and 10cm depth plus volumetric soil moisture content
UV Index Data
Solar UV radiation index to assess sun exposure and radiation stress on crops
Scroll within the panel for all 7 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Agromonitoring Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Agromonitoring API Rules
SPECTRALAgromonitoring API Rules
SPECTRALJSON Schema 11
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
ErrorResponse
JSON SCHEMAGeoJson
JSON SCHEMANdviRecord
JSON SCHEMAPolygon
JSON SCHEMAPolygonCreateRequest
JSON SCHEMASatelliteImage
JSON SCHEMASoilData
JSON SCHEMATemperatureRange
JSON SCHEMAUvIndexData
JSON SCHEMAVegetationStats
JSON SCHEMAWeatherData
JSON SCHEMAScroll within the panel for all 11 ·
JSON Structure 11
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Agromonitoring Errorresponse Structure
JSON STRUCTUREAgromonitoring Geojson Structure
JSON STRUCTUREAgromonitoring Ndvirecord Structure
JSON STRUCTUREAgromonitoring Polygon Structure
JSON STRUCTUREAgromonitoring Polygoncreaterequest Structure
JSON STRUCTUREAgromonitoring Satelliteimage Structure
JSON STRUCTUREAgromonitoring Soildata Structure
JSON STRUCTUREAgromonitoring Temperaturerange Structure
JSON STRUCTUREAgromonitoring Uvindexdata Structure
JSON STRUCTUREAgromonitoring Vegetationstats Structure
JSON STRUCTUREAgromonitoring Weatherdata Structure
JSON STRUCTUREScroll within the panel for all 11 ·
Examples 11
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Scroll within the panel for all 11 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 6
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Crop Health Monitoring
Track vegetation index trends over the growing season to identify stress, disease, or nutrient deficiencies early
Irrigation Management
Combine soil moisture, weather forecast, and NDVI data to optimize irrigation scheduling and reduce water usage
Yield Prediction
Use satellite-derived vegetation indices across the growing season to build yield prediction models
Field Boundary Mapping
Register precise field polygon boundaries for targeted data retrieval and zonal analysis
Precision Agriculture
Apply variable-rate inputs using spatial variability data from satellite imagery and vegetation indices
Climate Risk Assessment
Monitor weather extremes, drought, and soil conditions to assess climate-related agricultural risks
Integrations 3
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
OpenWeatherMap
Agromonitoring uses OpenWeatherMap weather infrastructure for current and forecast data
Sentinel-2
European Space Agency Sentinel-2 satellite data is a primary imagery source
Landsat
NASA/USGS Landsat imagery is available as an additional satellite data source
Resources
Every other property we hold for Agromonitoring — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/agromonitoring · machine-readable index on apis.io
This is an independent, third-party profile of Agromonitoring, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.