API Reference
The Co-mind.ai API follows RESTful conventions and is fully documented via our OpenAPI 3.1 specification. All endpoints listed below are auto-generated fromopenapi.yaml.
Base URL
/v1/ unless otherwise noted.
Authentication
All API requests (except/health and public auth endpoints) require a Bearer token:
- Personal Access Token (Recommended)
- JWT Token
Request Format
- Content-Type:
application/jsonfor all JSON request bodies - File uploads:
multipart/form-data - Character encoding: UTF-8
Response Format
All responses return JSON with consistent structure:Status Codes
| Code | Description |
|---|---|
200 | Success |
201 | Created |
204 | No Content (successful deletion) |
400 | Bad Request — invalid parameters |
401 | Unauthorized — invalid or missing token |
403 | Forbidden — insufficient permissions |
404 | Not Found — resource doesn’t exist |
409 | Conflict — capability not supported or duplicate |
415 | Unsupported Media Type |
429 | Rate Limited — retry after delay |
500 | Server Error — retry with backoff |
Streaming
Chat and completion endpoints support Server-Sent Events (SSE) streaming by setting"stream": true:
data: lines:
Rate Limiting
When you exceed rate limits, the API returns429 Too Many Requests. Implement exponential backoff in your client:
Endpoint Categories
The API is organized into these categories — browse them in the sidebar:Authentication
Login, SSO, token refresh, registration, password management.
Chat & Completions
OpenAI-compatible chat, text completion, and streaming.
Knowledge Bases
Create KBs, upload files, query for context, RAG chat.
Echo Engine
Audio transcription (STT), text-to-speech (TTS), recordings.
Researcher
Web search, content scraping, deep research, report synthesis.
Document Analyzer
Upload documents, extract data, human-in-the-loop review.
Admin
Tenant management, directory sync, sanitizer policies, audit logs.
Discovery
Models, backends, capabilities, health checks.

