The WorksBuddy API lets you read and write data across the suite and subscribe to events. Each agent (Lio, Taro, Evox, Sigi, Inzo, Revo, Ranko, and Ciao) exposes its own REST API, and the agents share data with each other, so a change made through one API can flow on to the others.
Base URLs
Each agent has its own base URL. Every path in an agent's reference is relative to its base URL.
| Agent | Base URL | Reference |
|---|---|---|
| Lio | https://api-lio.worksbuddy.ai/api/v1 | Lio API |
| Taro | https://api-taro.worksbuddy.ai/api/v1 | Taro API |
| Evox | https://evox.worksbuddy.ai/v1 | Evox API |
| Sigi | https://api-sigi.worksbuddy.ai/api/v1 | Sigi API |
| Inzo | https://api.inzo.worksbuddy.ai/api/v1 (sandbox: https://sandbox.api.inzo.worksbuddy.ai/api/v1) | Inzo API |
| Revo | https://api.worksbuddy.ai/revo/v1 | Revo API |
| Ranko | https://<your-ranko-host>/api/v1 | Ranko API |
| Ciao | https://api-ciao.worksbuddy.ai/api/v1/public | Ciao API |
Authentication
Every request must be authenticated. Most agents take an API key as a bearer token; Lio takes a bare key in the X-API-Key header.
Rate limits
Requests are rate limited per credential. Limits, the headers that report remaining quota, and the status returned when a limit is exceeded (429) are documented in each agent's API reference.