Mistral Deployment Integration

Overview

Prepare a platform-neutral runtime boundary. Separate application health from provider readiness, keep credentials server-side, and make overload, provider failure, and rollback predictable.

Prerequisites

• An immutable artifact, lockfile, release SHA, and deployment owner.
• An environment-scoped secret, egress policy, and tenant authorization design.
• Capacity, timeout, queue, spend, observability, canary, and rollback policies.

Current Contract

The API is https://api.mistral.ai with Bearer auth. Model and workspace capacity are runtime dependencies; application startup should not require a paid inference call.

Authentication

Inject the key into a trusted server and restrict egress. Never pass it to browser, build output, health response, or an edge runtime without protected secret semantics.