API Reference
Base URL
https://api.yocaso.dev
Request Format
All endpoints are accessed through the KrakenD API gateway using REST-style paths:
POST /api/v1/<domain>/<service>/<method>
Content-Type: application/json
For example:
curl -X POST https://api.yocaso.dev/api/v1/llm/gateway/send-message \
-H "X-API-Key: sk_your_key_here" \
-H "Content-Type: application/json" \
-d '{"conversation_key": "conv_abc", "user_message": {"role": "user", "content": "Hello"}}'
Request and response bodies use protojson encoding (JSON representation of Protocol Buffer messages).
Authentication
Every request must include one of:
| Method | Header | Use Case |
|---|---|---|
| Secret key | X-API-Key: sk_... | Backend-to-backend |
| Publishable key + JWT | X-API-Key: pk_... + Authorization: Bearer <jwt> | Client apps |
| JWT only | Authorization: Bearer <jwt> | Dashboard |
See Authentication for details or the API Key Integration Guide for scopes, rate limits, and code examples.
Gateway Services
| Gateway | Base Path | RPCs | Description |
|---|---|---|---|
| LLM Gateway | /api/v1/llm/gateway/ | 25 | Threads, messages, MCP tools, memories, voice sessions |
| Storage Gateway | /api/v1/storage/gateway/ | 13 | Per-user file storage, upload/download URLs |
| Auth Gateway | /api/v1/api-keys/ | 7 | API key lifecycle management |
| Notification Gateway | /api/v1/notifications/ | 42 | Push, inbox, preferences, send, topics, subscribers, workflows, providers |
Total: 87 RPCs across 4 gateway services.