DeepLeaf Docs

Guides and trainings · docs.deepleaf.org

API reference

Crop Health — /identification

Machine callers identify a plant from a photo on the canonical API host. Agronomist chat diagnosis stays on the chat `/v1` path unless you later unify products; this path is the Crop Health service behind the edge.

Public hosts

  • Canonical: https://api.deepleaf.org/identification
  • Dual-run alias (same edge site): https://api.deepleaf.io/identification

The edge rewrites /identification → /identify on Crop Health Cloud Run. Call the public path; do not dial the Cloud Run URL from partner apps.

Call shape

POST multipart form with field image (required). Optional query lang — single code (e.g. en) or comma-separated (e.g. en,ar,fr) for common names.

curl https://api.deepleaf.org/identification?lang=en \
  -F "image=@leaf.jpg"

A missing body yields a validation 4xx from the service — that still proves the rewrite. A 500 with an /identification path on the upstream host means the rewrite did not run.

Core dual-run

Legacy Core (GraphQL on io.deepleaf.io, CDP in Sweden) keeps serving existing Crop callers. Point new and migrated traffic at https://api.deepleaf.org/identification. Do not decommission Core CDP until the Phase 7 cohort drain.

Keys and related docs

Agronomist /v1 keys live in the developers console. Crop Health on this path is the image identify service; chat diagnose remains under Agronomist /v1.

API reference · Guide: Crop Health · Upstream health (operators)