Stateless completion with a Mind
Send a conversation to a single Mind and get its next reply without any server-side state: you own the history and resend it every call. Omit messages (or send []) to get the Mind's greeting. Supports OpenAI-style response_format (structured output), user-defined tools / tool_choice (function calling; calls are returned, never executed), file/link attachments via messages[].metadata.attachedFiles, a model/provider override, language, sourcePolicy: "knowledge_only" to retrieve processed Mind knowledge with internal web tools and request attachments disabled (persona fallback is reported when no evidence matches), and citationMarkers to control inline [[CITE:n]] markers. Default responseMode: "sync" returns buffered JSON; responseMode: "stream" returns Server-Sent Events (start, heartbeat comments, then a single result frame with the same payload, then done) to keep the connection active during long generations. JSON is limited to 1 MiB, 100 messages, 128 content parts per message and 100 total attachments; body admission returns HTTP 400/413 before opening a stream. Client disconnects cancel generation and structured extraction where the provider supports cancellation. Access rule: you can chat with Minds you own, Minds shared with you directly or with your team, Minds inside an Audience you own, belong to, or that is shared with your team, and public Minds; anything else returns 403 Access denied. The Mind must be trained (readyToChat: true on GET /v1/minds/{mindId}/training) or you get 409 SPARK_NOT_READY. Each call consumes one synthetic response from your monthly allowance and counts against the 30 completions/minute rate limit.
Request
- Base URL: https://api.getminds.ai
- URL: https://api.getminds.ai/api/v1/minds/{mindId}/completion
- Auth: HTTP bearer
Path parameters
Mind UUID.
Request body
Response
Reply generated. application/json for responseMode: "sync" (default); text/event-stream for responseMode: "stream", where the result frame carries the identical MindCompletionResponse payload and failures after opening the stream (including 401/403/404/409/429) are reported as an error frame followed by done. Body size/shape failures return HTTP 400/413 before streaming.
Changes
No recorded changes to this operation across all 1 revision of this API.