KAEL API
The KAEL API is served from https://api.aethex.tech.
| Field | Value |
|---|---|
| Product maturity | Live / evolving |
| Documentation status | Active |
| Base URL | https://api.aethex.tech |
| Machine-readable contract | /static/custom/openapi.yaml |
| Last source review | 2026-06-26 |
API groups
| Group | Purpose |
|---|---|
| Health | Service health, ping, and active-session counts |
| Models and chat | Model catalog, non-streaming chat, and SSE streaming |
| Authentication | Session inspection, login, logout, email code, and verification |
| History | Save, list, load, and delete conversations |
| Memory | List, save, delete, and clear keyed memory |
| Identity and profile | Linked identity and usage summaries |
| Documents | Generate and manage KAEL-produced documents |
| Feed | Featured conversations and activity highlights |
| Integrations | Signed Discord interactions and deployment webhooks |
Public versus privileged routes
The machine-readable public contract intentionally excludes owner-only operations such as deployment, world-model mutation, operator creation, and tenant administration.
Those routes are operational interfaces—not browser APIs.
Streaming
POST /kael/stream uses Server-Sent Events:
- Model metadata is emitted first.
- Generated text arrives in JSON token events.
- Errors can arrive as JSON events.
[DONE]closes the logical stream.
See API Quickstart for a complete request.
Authentication
KAEL uses secure cookies for signed-in browser sessions. Tenant keys can be supplied to tenant-aware requests through the dedicated tenant field or header. Operator tokens are separate and must remain server-side.