Mirobody Platform does not sell LLM tokens — you bring your own. This page defines the BYOK protocol.Documentation Index
Fetch the complete documentation index at: https://docs.mirobody.ai/llms.txt
Use this file to discover all available pages before exploring further.
Security guarantees
- Never persisted — LLM keys are not written to any database.
- Never logged — middleware scrubs
X-LLM-*from log copies at ingress. - Per-request isolation — keys live only in-memory for the current request, then discarded.
Protocol
Only the LLM-dependent endpoints require BYOK; everything else needs onlyAuthorization.
- REST
- WebSocket
Pick a backend
Aliyun DashScope
China cluster first choice. One key covers DeepSeek (Flash/Pro), Kimi, Qwen.
Volcengine
China cluster alternative. Doubao models.
OpenAI
Global cluster default (no SLA on the China cluster).
Google Gemini
Global cluster alternative.
Which endpoints need BYOK
| Endpoint | LLM use |
|---|---|
POST /api/chat | Main chat |
POST /api/v1/food/analyze | Food image recognition |
POST /api/v1/holywell/journal/create | Journal AI processing |
POST /api/v1/holywell/journal/reprocess | Re-run journal AI |
POST /api/v1/holywell/journal/update | Only when the body carries new text_input or files |
WS /ws/upload-health-report | Report parsing + summary |
WS /ws/upload-with-llm-analysis | End-to-end LLM analysis |
Authorization.
Errors
| Scenario | HTTP | code | msg |
|---|---|---|---|
Missing X-LLM-Api-Key on an AI endpoint | 400 | -10 | X-LLM-Api-Key header is required for this endpoint. |
| Upstream LLM returns 401 | 200 (SSE) | - | data: {"type":"error","content":"LLM auth failed: ..."} |
| Upstream LLM network error | 200 (SSE) | - | data: {"type":"error","content":"LLM upstream error: ..."} |