Platform & API

One platform under every service.

Sensors, cameras, harvest logs and orders land in one place, with the same IDs, timestamps and zones. That is what makes the models work.

Architecture

FieldSensors on Modbus / 4-20 mA, PoE cameras
EdgeIndustrial controller (owns actuators), gateway with offline buffer, on-site AI inference
DataTime-series store, image object store, event and label log
ModelsYield, vision, demand and route models
ActDashboards, alerts, set-point proposals, API

Planned API

The API is in design. The endpoints below are planned and will change before release.

Status: planned, not yet available

GET  /v1/sites/{site_id}/zones
GET  /v1/zones/{zone_id}/readings?metric=vpd&from=…&to=…
GET  /v1/cameras/{camera_id}/frames?date=…
GET  /v1/forecasts/yield?site_id=…&horizon=4w
POST /v1/events   { "type": "harvest", "row": "A-07", "kg": … }
GET  /v1/lots/{lot_id}/trace

Principles

Safety first

Controllers keep running and fall back to fixed schedules if the cloud or a sensor fails.

Open protocols

Modbus, MQTT and standard formats, so hardware is not locked to one vendor.

Data residency

Hosting region and security certifications: to come.

Want early API access?

Tell us what you would build. We are shaping the API with early partners.

Book a discovery call Explore services