Skip to main content
A session is one piece of agent work: an ask, an automation run, a chat, or the set-up run. GET /v1/sessions/{id} reads one (see Endpoints). The endpoints on this page list them and act on them. Each has an MCP twin with the same payload: list_sessions, cancel_session, delete_session and add_context. See the tool reference.

GET /v1/sessions

Read-only. No credits. MCP tool: list_sessions.
Sessions, newest first.
Shell
Response
status is the three-word vocabulary (complete, running, failed); state is the finer stored word. A cancelled session reads failed under status and cancelled under state.

POST /v1/sessions/{id}/cancel

No credits. Works on a spent balance. MCP tool: cancel_session.
Stops a running session before its next step. Credits already spent on it stay spent. Idempotent: cancelling twice is the same as cancelling once. If the run already finished, the call returns that real ending unchanged; a cancel never rewrites a finished run.
Response

DELETE /v1/sessions/{id}

Destructive. MCP tool: delete_session.
Permanently deletes a finished session and its trace. A running session answers 409: cancel it first.
Response

POST /v1/sessions/{id}/context

Spends credits only with run: true. MCP tool: add_context.
Gives a session text or links it cannot find itself. The agent reads it as a message in the thread. Send text, urls, or both.
  • run: false (default): nothing starts. The session’s next turn reads the context, and a run already in flight picks it up when its current turn ends.
  • run: true: the session is queued again to act on it now. That is a new turn, and it costs credits.
A cancelled session refuses new context.
Shell
Response