Base URL:
https://www.orgo.ai/api
Auth: Authorization: Bearer $ORGO_API_KEY on every request. Both surfaces require an account-wide key. A workspace-scoped key is refused on every thread endpoint.
The /v1 surface
List threads
Create thread
201 Created. You rarely need this. A completion with no thread_id creates one for you.
Get thread
Delete thread
GET. The creator also needs write access to the computer’s workspace. A Can chat member gets 403 even for a thread they created.
Errors
type is one of invalid_request, authentication_error, permission_error, or not_found.
The /chat surface
Access on this surface is by workspace, not by author. Any member of the computer’s workspace can read its threads. Updating a thread and generating a title need write access to the workspace, so a Can chat member gets 403. The
/run endpoints are the exception and are restricted to the thread’s creator.
List threads
status client-side if you want to hide them.
The computer’s UUID. This surface does not accept an instance id: a non-UUID value returns 500. Omitting it returns 400.
Create thread
201 Created.
Client-side identifier. Echoed back as
externalId so clients can reconcile local and remote threads. When omitted, externalId is absent from the response.Get thread
Update thread
archive: true is applied first, otherwise unarchive: true, otherwise title and messages together. A body with none of these fields is accepted and changes nothing.
true sets status to archived. Nothing else changes: archived threads still appear in the list response, so filter on status client-side. Any other value is ignored.true sets status back to regular. Ignored when archive: true is also present. Any other value is ignored.Delete thread
PATCH with archive: true if you might need the conversation back.
Generate title
The messages to summarize. Only the first three are read, and the joined text is truncated to 1000 characters. Each message is
{ role, content } where content may be a string or an array of { type: "text", text } blocks. A missing or empty array returns 400.text/plain:
GET returns it in title.
Run state
GET reports whether a run is in progress on this thread right now. Use it to decide between rendering a finished transcript and re-attaching to a live one.
running answers for the single server process that handled your request. With several processes behind the load balancer, a run in progress elsewhere reports running: false. Treat true as reliable and false as “not here”.DELETE stops a run you started. It returns 200 in both outcomes:
/run methods are restricted to the thread’s creator; a workspace teammate gets 403.
Errors
Error responses on this surface carry a single string
error field: