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.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.Response
DELETE /v1/sessions/{id}
Permanently deletes a finished session and its trace. A running session answers409: cancel it first.
Response
POST /v1/sessions/{id}/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.
Shell
Response