Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
agrio website screenshot

agrio

Agrio is a precision plant protection solution that helps growers and crop advisors forecast, identify, and treat plant diseases, pests, and nutrient deficiencies. With Agrio APIs, developers can access AI-powered plant disease diagnosis from images, crop advisory data, weather pattern analysis, pest and disease predictions, and satellite vegetation monitoring to build accurate crop advisory tools.

agent ready

Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.

Kin Score

API Evangelist profiles agrio the way a machine reads it — 48 machine-readable artifacts across 5 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 — agrio scores 58.2/100 (developing), with a separate agent-readiness read of 48/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.

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 58.2/100 · developing
Contract Quality 20.6 / 25
Developer Ergonomics 5.2 / 20
Commercial Clarity 7.9 / 20
Operational Transparency 4.1 / 13
Governance 10.4 / 12
Discoverability 10.0 / 10
Agent readiness — 48/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 15 / 15
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile agrio

Each block below is one kind of artifact we hold for agrio. 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 5

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.

agrio Balance API

Account credit balance and usage monitoring.

agrio Credit API

Credit management for API usage.

agrio Crops API

Supported agricultural crop types.

agrio Diagnose API

Plant disease and pest diagnosis from images.

agrio Diagnosis API

Diagnosis results and disease identification data.

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 six things the Kin Score reads for commercial clarity.

Published pricing tiers and plan structures.

Agrio Plans Pricing

3 plans

PLANS

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.

Agrio Rate Limits

5 limits

RATE LIMITS

FinOps 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.

Agrio Finops

FINOPS

Features 6

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.

AI Image Diagnosis

Computer vision algorithms identify plant diseases, pests, and nutrient deficiencies from uploaded photos with confidence scores.

AgrioShield Pest Prediction

Predictive algorithms forecast disease pressure before or between scouting events to enable proactive intervention.

Satellite Imagery Alerts

Remote sensing AI detects vegetation issues from satellite data, enabling early detection before visible symptoms appear.

Ranked Diagnoses

Returns multiple ranked diagnoses with confidence scores, common names, and scientific names for disambiguation.

Credit-Based Usage

API usage is metered using a credit system; one credit is consumed per diagnosis request.

Supported Crop Catalog

Discoverable catalog of supported crop types for building targeted diagnosis workflows.

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.

Agrio Context

7 classes · 16 properties

JSON-LD

Spectral 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.

agrio API Rules

5 rules · 3 warnings

SPECTRAL

agrio API Rules

26 rules · 9 errors · 15 warnings

SPECTRAL

JSON Schema 7

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.

Credit Balance

3 properties

JSON SCHEMA

Crop

3 properties

JSON SCHEMA

Diagnose Request

2 properties

JSON SCHEMA

Diagnosis Result

4 properties

JSON SCHEMA

Diagnosis

3 properties

JSON SCHEMA

Error Response

3 properties

JSON SCHEMA

Supported Crops Response

1 properties

JSON SCHEMA

Scroll within the panel for all 7 ·

JSON Structure 7

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.

Agrio Credit Balance Structure

3 properties

JSON STRUCTURE

Agrio Crop Structure

3 properties

JSON STRUCTURE

Agrio Diagnose Request Structure

2 properties

JSON STRUCTURE

Agrio Diagnosis Result Structure

4 properties

JSON STRUCTURE

Agrio Diagnosis Structure

3 properties

JSON STRUCTURE

Agrio Error Response Structure

3 properties

JSON STRUCTURE

Agrio Supported Crops Response Structure

1 properties

JSON STRUCTURE

Scroll within the panel for all 7 ·

Examples 7

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 7 ·

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.

Agrio Authentication

http · 1 scheme

SECURITY

Agrio Domain Security

TLSv1.2 · HSTS · DMARC

SECURITY

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.

Agrio Agentic Access

3 operations · 1 acting

3 operations · 1 acting

AGENTIC

Use Cases 5

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 Advisory Tool Integration

Embed AI plant disease diagnosis into existing crop advisory and farm management applications.

In-Field Disease Identification

Enable agronomists and farmers to photograph plant symptoms and receive immediate AI-powered diagnosis.

Early Warning Systems

Use AgrioShield alerts to notify growers when disease or pest conditions become favorable before visible symptoms appear.

Precision Agriculture Platforms

Integrate Agrio diagnosis into precision agriculture platforms for targeted treatment recommendations.

Research and Development

Access Agrio plant disease data for agricultural research and development of new advisory models.

Integrations 2

Pre-built integrations with other platforms tell you where this provider already fits in a stack.

Pre-built integrations with other platforms and tools.

Weather Data Systems

Agrio APIs integrate weather pattern data to enhance pest and disease prediction models.

Satellite Imagery Providers

Remote sensing data from satellite providers is used for vegetation monitoring and anomaly detection.

Resources

Every other property we hold for agrio — 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 1

Portal, sign-up, and the first successful call

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 2

Pagination, idempotency, versioning, errors, and events

Access & Security 2

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Company 3

The organization behind the API

← All providers · Data indexed from github.com/api-evangelist/agrio · machine-readable index on apis.io