Coven exposes a small versioned HTTP API over a Unix socket. The current public contract isDocumentation Index
Fetch the complete documentation index at: https://docs.opencoven.ai/llms.txt
Use this file to discover all available pages before exploring further.
coven.daemon.v1 served under the /api/v1 prefix.
The daemon does not use OAuth, JWTs, bearer tokens, API keys, or browser cookies. Trust is same-user local access to the Unix socket at <covenHome>/coven.sock. See Auth posture before adding a new client, dashboard, remote bridge, or browser-facing transport.
Handshake
Always start with:apiVersion and capabilities before depending on session or event response shapes.
Endpoints
| Endpoint | Purpose |
|---|---|
GET /api/v1/api-version | Read the active API version and supported versions. |
GET /api/v1/health | Check daemon health and metadata. |
GET /api/v1/capabilities | Discover routable capabilities and owning adapters. |
POST /api/v1/actions | Send a known intent through the control plane. |
GET /api/v1/sessions | List sessions. |
POST /api/v1/sessions | Launch a session. |
GET /api/v1/sessions/:id | Fetch one session. |
GET /api/v1/events?sessionId=... | Read session events. |
POST /api/v1/sessions/:id/input | Forward input to a live session. |
POST /api/v1/sessions/:id/kill | Kill a live session. |
Error envelope
All error responses use:Versioning
TheapiVersion field is the contract clients pin against. Coven follows additive compatibility: new fields and new capabilities are added under existing versions; breaking changes require a new version. See API versioning.
Calling the socket
- curl
- Node
- Rust