Mistral Bounded First Request

Overview

Prove the smallest useful chat path without turning a quickstart into production authority. Build offline, use synthetic text, capture content-free evidence, and stop after one approved response.

Prerequisites

• A configured server-side MISTRAL_API_KEY reference.
• A current model identifier selected from account-visible evidence.
• Approval for one billable request and a non-sensitive synthetic prompt.

Current Contract

The current chat surface is POST /v1/chat/completions. A request includes a model and messages; response and usage shapes come from the current endpoint schema. Model aliases and availability are mutable.

Authentication

Resolve the key only at runtime through the trusted client boundary. Do not print the key, headers, prompt, or response content in the receipt.