Read a thread and its messages
Returns one thread the caller owns, plus every message in it in order. Attachment metadata is included in the message entries; the bytes are fetched via a separate endpoint so a client that does not need them does not pay the bandwidth.
Returns one thread the caller owns, plus every message in it in order. Attachment metadata is included in the message entries; the bytes are fetched via a separate endpoint so a client that does not need them does not pay the bandwidth.
Authorization
bearerAuth A bearer token. The Account routes accept a Privy access token; the MCP transport accepts an sk- API key issued by POST /account/api-keys.
In: header
Path Parameters
The id of the thread to read.
Response Body
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/inference/threads/string"{ "thread": { "id": "string", "title": "string", "model": "string", "createdAt": "2019-08-24T14:15:22Z", "updatedAt": "2019-08-24T14:15:22Z" }, "messages": [ { "id": "string", "role": "user", "parts": [ null ], "createdAt": "2019-08-24T14:15:22Z", "attachments": [ { "id": "string", "name": "string", "mimeType": "string" } ] } ]}Create a new thread POST
Mints a new thread for the authenticated caller. The thread starts with no messages; the title is set when the first user message lands. The optional `model` field locks the thread to that model id; threads default to the server's default model when the field is omitted.
Rename a thread PATCH
Replaces the thread's title. The rename is total, not incremental.