Developer Center
Build on our automation platform.
REST APIs, ROS2 drivers, vision SDKs and PLC libraries — everything you need to integrate our cells into your MES, WMS or ERP.
Get started in three steps
Our cells ship with an open integration surface — a documented HTTP fleet API, native ROS2 launch packages and fieldbus function blocks. Everything below runs on the same platform we deliver in production.
Request the integration kit
The kit contains API specs, ROS2 drivers, PLC function blocks and a simulation workspace for your cell topology.
Run the simulator
Validate mission dispatch, docking and safety zones against a digital twin before touching hardware.
Go to production
Deploy the same artifacts to the live cell. Onboarding is measured in days, not quarters.
# Typical integration flow
1. Provision fleet service → /fleet/v1
2. Register mission templates
3. Bind station triggers (PLC / MQTT / HTTP webhook)
4. Dry-run in simulator → verify cycle + interlock
5. Go live and monitor via telemetry APIFleet orchestration API
REST over HTTPS, JSON payloads, stateless auth tokens. The same endpoints drive dispatch, docking, charging and telemetry.
| Method | Endpoint | Description |
|---|---|---|
| POST | /api/fleet/v1/missions | Dispatch a mission to a vehicle or zone |
| GET | /api/fleet/v1/vehicles | List vehicles with status and pose |
| GET | /api/fleet/v1/vehicles/{id}/state | Live state: battery, path, task, interlocks |
| POST | /api/vision/v1/inspect | Trigger inspection and return result schema |
| POST | /api/notify/v1/webhooks | Register webhooks for mission & alarm events |
POST /api/fleet/v1/missions
{
"site": "zh-sh",
"mission": "deliver-part",
"priority": 5,
"vehicles": ["agv-07"],
"waypoints": ["W1", "DOCK-2"],
"payload": { "part_no": "A-1142", "qty": 1 }
}
→ 202
{ "mission_id": "m_9f2c81", "eta_s": 84, "status": "queued" }ROS2 & SDK
Robotic cells ship with ROS2 Humble launch packages and a Python SDK so your engineers keep their toolchain. Simulator worlds and telemetry adapters are part of the integration kit.
# Python SDK — dispatch and await a docking mission
from roboai import FleetClient
fleet = FleetClient("https://cell-01.local", token="…")
job = fleet.dispatch("dock-and-deliver", vehicle="agv-07")
print(job.status()) # queued → moving → dockedFieldbus & PLC integration
Cells expose a deterministic handshake interface for machine safety and line control — no black-box integration required.
Supported protocols
- EtherNet/IP · PROFINET · Modbus TCP
- MQTT / Sparkplug B telemetry
- OPC UA (information model provided)
Line integration scope
- Mission request / release handshake
- Safety interlocks & e-stop feedback
- Part-present & quality-pass gating
Engineering notes
Written by our integration engineers for yours. PDFs are included in the integration kit on request.
AGV traffic management and deadlock avoidance ›
Zone reservation vs. path blocking, request ordering under mixed fleets, and how deadlocks are broken with provably starvation-free priority rules.
Vision-guided docking: calibration that survives the floor ›
Marker-to-camera calibration, drift compensation after maintenance, and achievable repeatability under floor change and lighting variation.
Safety architecture for mobile manipulators ›
Mapping ISO 13849 performance levels onto AGV + arm cells: safety-rated speed limits, zone interlocks and validated stopping distances.
Release notes
Platform 0.6.0
2026-09- Fleet API v1 stable preview — dispatch, telemetry, webhooks
- ROS2 driver supports mission feedback topics
Platform 0.5.0
2026-08- Simulator workspace released with sample cell layouts
- OPC UA information model published
Talk to the engineers who build the platform
Tell us your line layout and controllers — we will return an integration specification with API contracts and safety notes.
Request integration spec