Threads are created implicitly. Every call to
POST /v1/chat/completions with a computer_id either continues an existing thread (when thread_id is passed) or creates a new one and returns its ID. Use these endpoints to list, inspect, rename, archive, or delete threads - you rarely need to create them by hand.Endpoints
Base URL:
https://www.orgo.ai
Auth: Authorization: Bearer sk_live_... on every request.
List threads
Query parameters
string
required
UUID of the computer (the
id field from Create computer). Threads are scoped per-computer; to list across computers, call this endpoint once per computer.Response
array
Array of thread objects, most recent first.
Example
Create thread
POST /v1/chat/completions create one for you.
Request
string
required
UUID of the computer to attach the thread to.
string
Optional client-side identifier. Echoed back as
externalId in the response so clients can reconcile local and remote threads.Response
Returns201 Created.
string
The new thread’s UUID. Use this as
thread_id in subsequent chat completions.string
Mirror of
localId from the request. Omitted if not supplied.Example
Get thread
Response
string
Thread UUID.
string
active or archived.string
Title if set, otherwise omitted.
array
Full message history in chronological order.
Update thread
Request
string
New human-readable title.
array
Replaces the entire stored message history with this array. Use with care - this is a full overwrite, not an append.
boolean
Set to
true to archive. Archived threads are hidden from default list views but remain fetchable by ID.boolean
Set to
true to restore an archived thread.Response
string
Thread UUID.
string
Updated status (
active or archived).string
Updated title if set.
Example
Delete thread
PATCH with archive: true if you might need the conversation back.
Response
Generate title
Request
array
required
The messages to summarize. Only the first three are considered. Each message is
{ role, content } where content may be a string or an array of { type: "text", text } blocks.Response
text/plain stream in the assistant-ui format:
GET will include it in the title field.
Using threads with completions
Threads compose with chat completions - you almost never manage them directly in production code:Errors
Error responses are JSON with a single
error field: