Back to Documentation
API Reference
The Taiso API is an OpenAPI-described REST service. The authoritative reference is generated from the running server, so it is always current — the links below are the canonical source, not this page.
Live reference
- Swagger UI — browse and send authenticated requests from the browser.
- ReDoc — the same schema in a reading-oriented layout.
- openapi.json — the raw spec, for generating a client.
Base URL and versioning
Production is https://api.taiso.ai. Every endpoint is namespaced under /api/v2; the version is part of the path, so a future v3 will not change v2 behaviour.
Authentication
Send your API key as a bearer token on every request:
Authorization: Bearer <your-api-key>See Authentication for key creation, scoping, and rotation.
Endpoint groups
| Path | Purpose |
|---|---|
/api/v2/projects | Projects — the container for files, chats, and generated output |
/api/v2/files | File upload and retrieval |
/api/v2/chats | Server-side conversation state |
/api/v2/sops | SOP definitions, versioning, and rollback |
/api/v2/jobs | Asynchronous execution, status polling, cancellation |
/api/v2/agents | Agent definitions and invocation |
/api/v2/llm | Direct LLM calls, including streaming chat |
/api/v2/tools | External tools — web search, MCP, PDF, and others |
/api/v2/search | Search across project data |
/api/v2/assist | Assist endpoints |
/api/v2/users | Account and profile management |
/api/v2/health | Service health |
Long-running work
SOP and agent execution is asynchronous. Submitting work returns a job id; poll GET /api/v2/jobs/{id} until it reaches a terminal state. Jobs can also be cancelled while in flight.
Need help?
This page is a starting point. For anything it does not cover, reach out.