Install Jentic One Beta

Connect the Pl@ntNet API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Pl@ntNet API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmyplantnet.org%2Fplantnet" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmyplantnet.org%2Fplantnet" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Pl@ntNet API.

Identify plants from a list of image URLs via GET /v2/identify/{project} for URL-friendly batch flows

Identify plants from uploaded image files via POST /v2/identify/{project} for direct camera input

Identify plant diseases from images via POST /v2/diseases/identify

Identify plant varieties from images via POST /v2/varieties/identify

List the supported projects (regional flora collections) via GET /v2/projects and the species in each project

GET STARTED

Start building with Pl@ntNet API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Pl@ntNet API for, with concrete tasks.

★ Mobile Plant Identification App

Power a consumer or field-research mobile app that identifies plants from a phone camera image. The app uploads the photo via POST /v2/identify/{project} and presents the top species candidates with confidence scores. Choosing the right project (e.g., western-europe, useful, weeds) tunes the model for the user's region, improving accuracy over a global default.

Call POST /v2/identify/western-europe with the user's uploaded JPEG and return the top three species candidates with confidence scores.

Crop Disease Detection

Detect plant disease from field photos via POST /v2/diseases/identify for agronomy and gardening applications. The integration pairs disease identification with /v2/diseases (the catalogue of identifiable diseases) to validate the response and surface the disease name, host species, and confidence to the grower.

Call POST /v2/diseases/identify with the uploaded leaf photo and join the response against GET /v2/diseases for the canonical disease description.

Quota-Aware Batch Identification

Run a large batch of plant identifications without exceeding the Pl@ntNet plan quota. The integration polls GET /v2/quota and GET /v2/quota/daily before each batch to determine remaining capacity, then calls GET /v2/identify/{project} with image URLs in chunks. /v2/quota/history feeds usage dashboards.

Call GET /v2/quota to check remaining identifications, batch the URL list into safe chunks, and call GET /v2/identify/{project} with each chunk.

Plant Image Vector Search

Build a similarity search index over a herbarium or field-photo archive using POST /v2/embeddings. Each image is converted to a vector and stored in a vector database; future queries embed the query image and retrieve the nearest neighbours. This unlocks 'find similar specimens' without retraining a custom model.

Iterate over the herbarium archive, call POST /v2/embeddings for each image, and write the resulting vectors into a vector database keyed by specimen ID.

AI Agent Botanical Concierge

An AI agent acts as a botanical concierge for citizen scientists. It searches Jentic for Pl@ntNet operations, loads the identify and diseases-identify schemas, checks quota, and runs identification on images attached to a chat message. Jentic isolates the api-key query parameter so the agent never sees the raw secret in URLs.

Search Jentic for 'identify a plant from a photo', execute POST /v2/identify/western-europe, and return the top species candidate with confidence score.

Key Endpoints

16 endpoints — jentic publishes the only available openapi specification for pl@ntnet api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/v2/identify/{project}

Identify a plant from uploaded images

GET

/v2/identify/{project}

Identify a plant from image URLs

POST

/v2/diseases/identify

Identify a plant disease from images

POST

/v2/varieties/identify

Identify a plant variety from images

GET

/v2/projects

List supported regional projects

GET

/v2/quota

Check quota consumption

POST

/v2/embeddings

Generate image embeddings

GET

/v2/_status

Check API health

POST

/v2/identify/{project}

Identify a plant from uploaded images

GET

/v2/identify/{project}

Identify a plant from image URLs

POST

/v2/diseases/identify

Identify a plant disease from images

POST

/v2/varieties/identify

Identify a plant variety from images

GET

/v2/projects

List supported regional projects

GET

/v2/quota

Check quota consumption

POST

/v2/embeddings

Generate image embeddings

GET

/v2/_status

Check API health

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Pl@ntNet by hand means holding its api-key, appending it to every request against my-api.plantnet.org, and building the multipart image uploads for identification yourself. Through Jentic you install once, import Pl@ntNet from the API Directory, store the key once, and your agent calls it.

Permission scoping

Pl@ntNet puts the project in the URL path (/v2/identify/{project}), so a rule can pin your agent to one project. You choose the operations it may call, so you can allow plant identification and disease identification while leaving embeddings generation out unless you add it.

Credential isolation

Your Pl@ntNet api-key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'identify a plant from a photo' or 'check a plant disease', and Jentic returns the matching Pl@ntNet operation with its multipart input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Pl@ntNet API through Jentic.

Why is there no official OpenAPI spec for Pl@ntNet API?

Pl@ntNet does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Pl@ntNet API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Pl@ntNet API use?

The Pl@ntNet API uses an `api-key` query parameter on every request. Through Jentic, the api-key is stored in the encrypted vault and appended to the URL at execution time, so the raw key never appears in agent context or in request logs.

Can I identify plants from a photo with the Pl@ntNet API?

Yes. Either call GET /v2/identify/{project} with image URLs as query parameters or POST /v2/identify/{project} with a multipart upload. The response returns the top candidate species with scores; choose the regional project that best matches the photo location for higher accuracy.

How do I check my Pl@ntNet quota through Jentic?

Search Jentic for 'check Pl@ntNet quota', load the GET /v2/quota schema, and execute it. For finer detail, also call GET /v2/quota/daily and GET /v2/quota/history - useful for batching large identification jobs without exceeding the plan limit.

Does Pl@ntNet identify plant diseases?

Yes. POST /v2/diseases/identify accepts uploaded images and returns identified diseases with confidence scores. Pair with GET /v2/diseases for the canonical disease catalogue and host-species metadata.

What are the rate limits for the Pl@ntNet API?

Pl@ntNet enforces plan-based quotas rather than per-second rate limits. Use GET /v2/quota and GET /v2/quota/daily before large batches and back off when the remaining count nears zero. Contact Pl@ntNet support to upgrade plans for higher monthly identification budgets.

Can I limit what my agent is allowed to do with the Pl@ntNet API?

Yes. Because you run Jentic One yourself, your own rules decide which Pl@ntNet operations and which credentials your agent may use. You can allow plant identification (POST and GET /v2/identify/{project}) and disease identification (POST /v2/diseases/identify) while leaving image embeddings (POST /v2/embeddings) out unless you add it. Since Pl@ntNet puts the project in the URL path (/v2/identify/{project}), a rule can also pin the agent to a single regional project.

Myplantnet Pl@ntNet API

Name: Pl@ntNet API
Brand: Pl@ntNet API
Availability: InStock

AI ReadinessFoundational (D)46/100

See full scorecard

Agent-ready OpenAPI document · curated by JenticAI/MLVisionapiKey16 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Identify plants, plant diseases, and plant varieties from photos and check API quota using a Pl@ntNet api-key query parameter.

Use for: I need to identify a plant from a photo, Find what disease is affecting a tomato leaf in this image, Check how much Pl@ntNet quota we have left this month, List the regional Pl@ntNet projects available

Not supported: Does not handle generic image classification, animal identification, or text generation - use for plant, plant disease, and plant variety identification from images only.

Jentic publishes the only available OpenAPI specification for Pl@ntNet API, keeping it validated and agent-ready. Pl@ntNet is a citizen-science platform that identifies plants from photos using a community-trained image-classification model. The API exposes 16 endpoints covering plant identification (by URL or upload), disease and variety identification, species and project listings, image embeddings, and quota and subscription introspection. Authentication is an api-key query parameter on https://my-api.plantnet.org, with quota tracking via /v2/quota and /v2/quota/daily.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

30%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4

32%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

52%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1

15%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B+Signals: 1

70%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Pl@ntNet API to your agent

Capabilities

Start building with Pl@ntNet API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Myplantnet Pl@ntNet API

Jentic AI Readiness Score

Pl@ntNet API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness