AIRO developer documentation
Everything you need to add route optimization to an ERP, a WMS or an AI assistant. The REST API takes orders, vehicles and a depot as JSON and returns optimized routes. The MCP connector exposes the same engine to Claude and ChatGPT.
Choose how to integrate
| You want to… | Use | Start here |
|---|---|---|
| Optimize routes from your ERP, WMS or scripts | REST API | /docs/api |
| Get notified when a plan is ready | Signed webhooks | /docs/api/webhooks |
| Plan from Claude or ChatGPT | MCP connector | /docs/mcp |
| Click through it yourself | Web portal | /waitlist |
How it works
- Your system sends orders, vehicles and a depot (JSON). The engine validates them and answers 202 immediately.
- A deterministic OR-Tools engine geocodes, builds a travel-time matrix and optimizes routes. No language model is involved.
- You poll the optimization or receive a signed webhook, then read routes, KPIs and unassigned orders, or download Excel/CSV.
Principles
- Idempotent: every optimization requires an Idempotency-Key, so retries never run or bill twice.
- Actionable errors: validation problems point at the exact order, with a message you can show to a user.
- Your data stays yours: uploaded and submitted data is never used to train AI models and never sent to an LLM.
- OpenAPI 3 spec at /v1/openapi.json for client generation.
API access opens with billing. Join the waitlist to be invited; keys are created in the portal under Connect AI.