Mistral Chat, Streaming, and Structured Output

Overview

Select the simplest chat mode satisfying the product contract. Treat non-streaming text, streaming events, and structured output as different state machines with shared safety and usage controls.

Prerequisites

• A model policy based on current account-visible evidence.
• A bounded prompt/data class and maximum output policy.
• A parser, schema validator, cancellation path, and synthetic fixtures.

Current Contract

Chat uses POST /v1/chat/completions. Streaming and response-format options are endpoint capabilities, not guarantees for every model; validate the current schema and selected model.

Authentication

Use server-side Bearer auth through the approved adapter. Never forward credentials or raw headers to users, tools, or browser code.