Guides
Questions & citations
Ask a grounded question, understand the outcome, and follow its original evidence.
Ask a question
POST /api/questions accepts a question for a structured answer. POST /api/questions/stream accepts a question and requestKey for a durable streamed question.
The dashboard handles stream validation and saves independent question records. It does not treat a previous answer as an implicit multi-turn conversation.
{
"question": "When is the support team available?",
"requestKey": "22222222-2222-4222-8222-222222222222"
}Give each question its own key
requestKey is a UUID that identifies one durable question attempt. Keep the same key when retrying the identical question after an uncertain response.
Generate a new key when the question changes. Reusing a key for different input can return 409 idempotency_conflict. The UUID above is illustrative; do not reuse it for every question.
Understand the outcome
A completed answer includes validated source references. insufficient_evidence means the available sources do not provide enough support.
context_budget_exceeded is a technical model-capacity refusal. Provider failures and interrupted streams are also technical outcomes, not evidence that the answer is absent from your sources.
Inspect citations
A citation identifies a document version and source chunk. Open it to inspect the original passage and any available PDF locations.
Several passages can belong to one document. A valid source identifier and a semantically supported claim are different checks; inspect the passage when precision matters.
Read the complete stream
Streaming uses newline-delimited JSON: one event per line. A started event or a text delta is not a final successful answer.
Integrations must validate the terminal event and clean end of stream. Saved records can be read through POST /api/conversations/read with the same requestKey, subject to current source access.