The response object
A response is Jockey’s reply to a request, generated by reasoning over the content in a knowledge store.
The object is composed of the following fields:
id: A string representing the unique identifier of the response.knowledge_store_id: A string representing the unique identifier of the knowledge store the response was generated against.session_id: A string representing the session identifier for the conversation. Pass it in subsequent requests to continue the multi-turn conversation.type: A string representing the object type. The value is alwaysresponse.status: A string representing the status of the response. See the Response statuses section for the meaning of each value.output: An array of output items. By default, only the final message is included. To also receive function call items, setincludeto["intermediate_outputs"]in the request.incomplete_details: An object explaining why the response is not a whole answer. Always present; non-nullonly whenstatusisincomplete. See the Incomplete responses section.usage: An object containing token usage statistics, withinput_tokensandoutput_tokensfields.created_at: A string representing the date and time, in the RFC 3339 format, when the response was created.
Response statuses
The status field of a response has one of the following values:
in_progress: The response is being generated.completed: The response has been generated successfully.incomplete: The response is not a whole answer. Readincomplete_details.reasonto find out whetheroutputholds a partial answer or nothing at all.failed: The response generation has failed.
Incomplete responses
incomplete_details is always present and is null on every status except incomplete,
so null means “this answer was not truncated” rather than “this platform does not report
the reason”. When it is non-null, its reason says what stopped the answer:
max_output_tokens: the answer reached the output limit before it was finished. The text inoutputis a valid prefix of the answer — usually worth rendering, marked as cut off.
Treat a value you do not recognize as “not a whole answer, for a reason this client does not know” rather than as an error.