Mistral SDK Boundary Patterns

Overview

Prevent provider-specific shapes and volatile client behavior from spreading. Centralize configuration, normalize results and errors, and expose cancellation and usage as first-class fields.

Prerequisites

• A locked official client version and matching documentation.
• An application interface for chat, embeddings, and optional streams.
• Defined timeout, retry, observability, and redaction policies.

Current Contract

Mistral documents official Python and TypeScript clients, but signatures can move independently of application code. REST endpoints remain the verification boundary for the pinned client.

Authentication

Inject MISTRAL_API_KEY into one server-side client factory. Return no key or authorization metadata from the adapter.