Mistral Authentication and Installation

Overview

Create a reviewable authentication boundary before any inference call. Separate workspace access, secret custody, application authorization, and billing so possession of a key never implies permission to spend or process arbitrary data.

Prerequisites

• A named workspace administrator, application owner, and spend owner.
• An approved server-side secret manager and environment-specific rollback route.
• A runtime and official client selected from current first-party documentation.

Current Contract

Mistral API requests use Bearer authentication at https://api.mistral.ai. Studio-created keys are displayed once. Free mode can include usage; current billing and limits must be read from the account rather than encoded.

Authentication

Store the credential as MISTRAL_API_KEY and send it only in the Authorization: Bearer header from a trusted server. Never place it in source, browser bundles, URLs, prompts, logs, screenshots, fixtures, or support archives.