--- title: "Mistral Studio / La Plateforme free inference" description: "$10 in credits refresh on a published schedule. See verified limits, model IDs, privacy terms, and primary sources for Mistral Studio / La Plateforme." canonical_url: "https://freeinferencing.com/provider/mistral/" md_url: "https://freeinferencing.com/provider/mistral.md" last_updated: "2026-09-19" --- # Mistral Studio / La Plateforme > $10 in credits refresh on a published schedule. ## Classification - **Directory:** Current - **Free access:** Monthly credits - **Status:** Available now - **Confidence:** High - **Payment card:** No - **Account:** Required - **Equivalent paid value:** At least $10.00/mo - **API endpoint:** `https://api.mistral.ai/v1` ## Models mentioned - `mistral-moderation-2603` - `labs-leanstral-2603` - `mistral-small-2603` - `mistral-medium-3-5` - `mistral-large-2512` - `ministral-14b-2512` - `ministral-8b-2512` - `ministral-3b-2512` ## Limits and terms ```yaml monthly_api_credit_usd: 10 dimensions: - requests_per_second - tokens_per_minute - tokens_per_month numeric_limits: dashboard_only ``` ## What happens to your prompts? **Not private.** Free-mode inputs and outputs are eligible for model improvement and training by default unless the user opts out. Privacy is audited separately from price. Review the current governing terms before sending sensitive or regulated data. ## Data governance and agreements ```yaml data_governance: review_status: reviewed plan_scope: Mistral Studio and API. Free, pay-as-you-go, enterprise, Labs, and stateful features have materially different data-use and retention rules. prompt_retention: Free-mode inputs and outputs may be retained for model improvement unless the user opts out. Paid stateless API traffic can qualify for zero data retention when approved; stateful features necessarily store application data. response_retention: Follows the same plan, endpoint, and feature-specific rules as prompts. ordinary_logging: Mistral processes technical and usage logs for service delivery, security, abuse prevention, and legal compliance; zero-data-retention eligibility does not eliminate all account or operational metadata. model_training: Free Mistral Studio and API usage may be used to train and improve models by default, with an opt-out. Pay-as-you-go API usage is opted out by default. Labs models may use data for training regardless of the general setting. product_improvement: Depends on plan and opt-out status. Free usage is eligible by default; paid API traffic is excluded by default, subject to feature and model exceptions. human_or_operator_access: Content retained for improvement, safety, support, or legal reasons may be accessed by authorized personnel under Mistral's controls; no universal operator-blind commitment applies to free mode. subprocessors_and_routing: Mistral and its listed subprocessors process service data under the privacy policy and DPA; third-party integrations can add separate terms. deletion_controls: Users can opt out of training in privacy controls. Zero data retention is available only for eligible paid stateless endpoints and requires approval; stored conversations, files, fine-tunes, and other stateful resources must be deleted through their feature controls. caveat: Mistral's general API privacy documentation and its free-mode documentation are easy to read as conflicting. The narrower free-mode disclosure controls this audit's free-tier finding, and Labs models remain an explicit exception. agreements: terms_of_service: https://legal.mistral.ai/terms privacy_policy: https://legal.mistral.ai/terms/privacy-policy?language=en-US data_processing_addendum: https://legal.mistral.ai/terms/data-processing-addendum ``` ## Eligibility ```yaml account_required: true payment_method_required: false intended_use: evaluation_and_prototyping ``` ## API compatibility and modalities - **Compatibility:** OpenAI Style Rest - **Modalities:** Safety ## Before you build with Mistral Studio / La Plateforme ### Read the classification narrowly This record describes the bounded offer supported by evidence on 2026-09-19; it does not guarantee permanence, production suitability, uptime, latency, model quality, or access from every account and region. “Monthly credits” should be interpreted together with the Current directory placement, High confidence, No payment-card status, and the plan-specific sources below. ### Resolve the live model route The snapshot records 8 model IDs. Match the exact ID against the provider's current catalog before using it in code because zero-price routes, aliases, context limits, and feature support can rotate while an older documentation page remains online. ### Match the quota to the workload shape Translate the allowance into peak requests per minute, input and output tokens, concurrency, retries, and every daily or monthly ceiling that applies to the intended account. The first limit reached by the workload is the practical ceiling. A large token pool can still fail interactive bursts, and a high request limit can still fail long-context work. Include tool calls and retry traffic, test the largest realistic payload, and treat research, experimental, and community access as conditional on their eligibility and fair-use terms. ### Preserve billing and privacy boundaries The recorded payment-card requirement is No, and account access is required. Confirm both in the live signup flow, set provider-side budgets when charges are possible, and observe the balance or usage fields after a complete request. The prompt-handling classification is **Not private** because Free-mode inputs and outputs are eligible for model improvement and training by default unless the user opts out. Re-read the terms for the exact route and plan before sending sensitive, regulated, or proprietary content. ### Follow the evidence, then re-check it This record links 13 first-party sources covering the offer, catalog, limits, pricing, terms, privacy, or adoption evidence available to the audit. Prefer the newest and most specific governing document or live catalog when sources disagree. A dated finding can become stale even when the page remains online, so retain the source and snapshot that supported the decision and submit a correction when a provider changes a material term. ### Plan fallback without policy drift A fallback should preserve modality, context length, streaming, structured output, tools, safety controls, and data terms, not only API syntax. Decide which errors may retry, cap retry storms, and prevent an exhausted free route from silently switching to a billable model. Rotating aliases and free pools can change behavior without changing the endpoint, so retain the response model field and test at least one substitute route before the primary offer becomes unavailable. ### Monitor the offer as a dependency Capture the model ID, response model, rate-limit headers, usage fields, latency, HTTP status, and provider request identifier. Watch authorization failure, quota exhaustion, catalog removal, policy revision, and balance movement as separate failure modes. Re-check the live catalog and governing sources on a schedule proportionate to the workload's importance, and keep an owner and exit path for any production dependency on volatile free capacity. ### Test one complete request before scaling Start with the smallest permitted request using the exact credential, model ID, endpoint, region, and account type intended for deployment. Record the status, headers, usage fields, response model, latency, and dashboard balance movement. Then exercise an invalid model, quota exhaustion, or rate limit so failure is explicit and cannot silently switch to a paid route. Validate streaming, structured output, and tool calls separately because a free model can expose fewer features than its paid counterpart. Keep a budget ceiling outside the application whenever billing is possible, and do not send sensitive data until the observed route matches the reviewed agreement. ## Primary sources - [Mistral pricing](https://mistral.ai/pricing): Official Pricing - [Inference pricing](https://docs.mistral.ai/inference/pricing): Official Docs - [Model catalog](https://docs.mistral.ai/models): Official Docs - [September 2024 release](https://mistral.ai/fr/news/september-24-release/): Announcement - [Mistral Terms of Service](https://legal.mistral.ai/terms): Official Terms - [Mistral Privacy Policy](https://legal.mistral.ai/terms/privacy-policy?language=en-US): Official Privacy - [Mistral Data Processing Addendum](https://legal.mistral.ai/terms/data-processing-addendum): Official Dpa - [Zero Data Retention](https://docs.mistral.ai/admin/monitor-comply/zero-data-retention): Official Docs - [Privacy and data controls](https://docs.mistral.ai/admin/monitor-comply/privacy-data-controls): Official Docs - [Mistral confirms Le Chat surpassed 1M downloads in 14 days (2025-02)](https://www.eweek.com/news/mistral-ai-le-chat-app-downloads/): Reputable Reporting - [PyPI download stats for mistralai](https://pypistats.org/packages/mistralai): Package Registry Stats - [2025 Stack Overflow Developer Survey technology section](https://survey.stackoverflow.co/2025/technology): Independent Survey - [Amazon Bedrock models at a glance listing the Mistral AI model family](https://docs.aws.amazon.com/bedrock/latest/userguide/model-cards.html): Official Docs ## Sitemap See the full [semantic sitemap](/sitemap.md) for every page and markdown mirror.