AI DevelopmentEnterprise

Mistral Medium 3.5: the Open Model for Enterprise Agents

August 16, 2026
9 min read
Mistral Medium 3.5 open model enterprise guide
Share:

In late April 2026 Mistral AI released Medium 3.5, a 128B dense model that merges instruction-following, reasoning, and coding into a single set of open weights. Since May it is the default model in Le Chat and powers remote coding agents in Mistral Vibe.

In this guide I break down the verified spec sheet, what actually improves over Medium 3 and Devstral 2, real API pricing, and a 5-minute quickstart — plus the honest limits you should know before betting a production workload on it.

1. What Mistral Actually Shipped

Mistral Medium 3.5 is the company’s first flagship merged model: one dense 128B checkpoint with a 256K context window that handles chat, reasoning, and agentic coding without switching models. Mistral trained the vision encoder from scratch for variable image sizes, and reasoning effort is now configurable per request — the same model can answer a quick reply or grind through a long multi-tool run.

License Nuance: Modified MIT ≠ Apache 2.0

Medium 3.5 ships as open weights under a Modified MIT license, not Apache 2.0 like Large 3. For most builds that is still permissive, but enterprise lawyers care about the difference: read the exact terms on the model card before assuming self-hosting conditions identical to Large 3.

Why it matters for enterprise teams: you get an EU vendor with EU data centers, open weights you can self-host on as few as four GPUs, and a hosted API behind the mistral-medium-latest ID. That trio — sovereignty story, exit option, and managed API — is exactly what procurement checklists ask for.

2. Spec Sheet

Everything below comes from Mistral’s official docs card and pricing page, not third-party rumor. This is the ficha you can paste into an architecture decision record.

🧠

Parameters

dense · 128B

Single dense 128B model merging instruction-following, reasoning, and coding. No MoE routing to tune, no separate reasoning checkpoint.

📏

Context

256K tokens

256K context window with structured outputs, function calling, document QnA, and Agents & Conversations API support.

📜

License

Modified MIT · open weights

Open weights on Hugging Face under a Modified MIT license. Also served on NVIDIA NIM and build.nvidia.com for prototyping.

💰

API Price

La Plateforme · per 1M tokens

$1.5 input / $7.5 output per million tokens via API id mistral-medium-latest. Batch cuts 50%, cached inputs cut up to 90%.

🖥️

Self-Host

4+ GPUs

Mistral reports self-hosting on as few as four GPUs. Compare with Large 3’s 675B MoE footprint before sizing hardware.

🏁

Benchmarks

official blog · May 2026

77.6% on SWE-Bench Verified — ahead of Devstral 2 and Qwen3.5 397B A17B per Mistral — plus 91.4 on τ³-Telecom for agentic calls.

Enterprise Price Math

At $1.5/$7.5 it costs 3x Large 3’s $0.5/$1.5 rate — you pay the premium for agentic reliability, not raw chat. Route classification and extraction to Small 4 ($0.15/$0.6) or Ministral 3B ($0.1/$0.1) and reserve Medium 3.5 for multi-tool runs where retries are the real cost.

3. What Improves Over the Previous Generation

Medium 3.5 does not replace the whole lineup — it takes the top agentic slot. Here is how it maps against what came before.

🆚 vs Medium 3 and Devstral 2

One model instead of two

Medium 3 handled general chat while Devstral 2 owned coding agents. Medium 3.5 merges both and replaces Devstral 2 inside the Vibe CLI.

SWE-Bench Verified: 77.6%

Mistral’s headline number beats Devstral 2 outright. If your bottleneck is agent success rate on real repos, this is the upgrade that moves the metric.

Configurable reasoning effort

Per-request reasoning control means one deployment serves both snappy chat and deep agentic runs — previously two latency profiles.

🆚 vs Mistral Large 3

Cheaper to serve yourself

Large 3 is a 675B MoE (41B active) under Apache 2.0 — stronger general flagship at $0.5/$1.5, but far heavier to self-host than a 128B dense model.

Agentic-first tuning

Large 3 wins on breadth; Medium 3.5 is tuned for long-horizon tasks, synchronous tool-calling, and structured output agents can consume.

License trade-off

Large 3’s Apache 2.0 is the cleaner enterprise license. If legal simplicity beats agentic scores for your workload, Large 3 stays the pick.

🏢 Where It Sits in the 2026 Lineup

Mistral Small 4

$0.15/$0.6 · routing & chat

Ministral 3 (3B/8B/14B)

$0.1+ · edge & on-device

Magistral

transparent reasoning family

Devstral

superseded by 3.5 in Vibe

Voxtral

speech & transcription

Mistral OCR

document extraction

Upgrade Rule of Thumb

If you run Devstral 2 or Medium 3 in an agent loop today, trial Medium 3.5 first — same vendor, same API shape, measurable success-rate delta. If you run Large 3 for general chat, don’t migrate: you’d pay 3x per token for agentic tuning you won’t use.

4. Quickstart: Call It in 5 Minutes

You need a La Plateforme API key from console.mistral.ai. The model ID is mistral-medium-latest. Below is the exact pattern from Mistral’s docs — install, chat completion, and the curl equivalent.

⚙️ Setup Steps

1. Create the key

Sign up at console.mistral.ai, generate an API key, and export it as MISTRAL_API_KEY. Never hardcode it.

2. Install the SDK

pip install mistralai gives you the official Python client with chat, agents, batch, and structured outputs.

3. Send the first completion

Point model at mistral-medium-latest and keep messages in the standard OpenAI-compatible chat shape.

4. Add tools when ready

Function calling and the Agents API use the same client — start plain, then layer tools once evals pass.

🔌 Two Ways to Run It

Hosted API

Zero infra. Pay $1.5/$7.5 per 1M tokens, get batch and caching discounts, run in EU data centers.

Self-hosted weights

Pull the Modified-MIT weights from Hugging Face or NVIDIA NIM. Realistic from four GPUs upward.

Install

pip install mistralai

Python — first agentic-ready call

import os
from mistralai import Mistral

client = Mistral(api_key=os.environ["MISTRAL_API_KEY"])

res = client.chat.complete(
    model="mistral-medium-latest",
    messages=[
        {"role": "system", "content": "You are a senior backend engineer."},
        {"role": "user", "content": "Refactor this function for clarity and add types: def f(d): return [x for x in d if x]"},
    ],
)
print(res.choices[0].message.content)

cURL — same call, no SDK

curl https://api.mistral.ai/v1/chat/completions \
  -H "Authorization: Bearer $MISTRAL_API_KEY" \
  -H "Content-Type: application/json" \
  -d ’{"model": "mistral-medium-latest", "messages": [{"role": "user", "content": "Hello from the terminal"}]}’

5. Where It Earns Its Price in Production

Medium 3.5 is not a general-chat bargain — it is an agent workhorse. These are the workloads where teams report the premium paying off.

🤖

Async Coding Agents

The native habitat: Vibe remote agents run cloud sessions in parallel — refactors, test generation, dependency upgrades, CI triage — then open a PR for human review.

📋

Long-Horizon Work Mode

Le Chat’s Work mode runs multi-step research and cross-tool workflows (mail, calendar, docs, Jira, Slack) on Medium 3.5 with approvals for sensitive actions.

📄

Structured Document Pipelines

Document QnA plus structured outputs make it a strong extractor-to-JSON stage before your database — provided you validate the schema downstream.

🇪🇺

GDPR-Sensitive EU Workloads

La Plateforme runs in EU data centers, which simplifies procurement where routing prompts through US providers is a compliance problem.

🪜

Tiered Routing Anchor

Use Small 4 or Ministral for classification and drafts, escalate only failing cases to Medium 3.5. Measure cost per accepted result, not per token.

6. Honest Limits

I tested the docs and the pricing page so you don’t have to learn these the expensive way. None of these are dealbreakers — all of them affect your budget or architecture.

⚠️ Hard Limits

  1. 1. Output pricing stings at scale: $7.5 per 1M output tokens is 5x Large 3. Verbose agents need max_tokens discipline and concise system prompts.
  2. 2. 256K context is not frontier-long anymore. Retrieval and chunking still matter past ~100K tokens of real-world recall.
  3. 3. Public-preview rough edges: pin versions and run your own evals before promoting any preview checkpoint to a customer-facing path.

💸 Costs to Watch

  1. Reasoning tokens: configurable effort is great, but deep reasoning burns output tokens at the most expensive tier. Log usage per run.
  2. Retry math: a cheaper model with 2 retries can beat Medium 3.5 on cost per accepted result for easy tasks. Benchmark your own distribution.
  3. Enterprise APIs: regional controls, SLAs, and premium support run 75% above list on select APIs — model that before quoting clients.

🧭 Review Cadence

  1. Month 1: run a 200-prompt eval split against Large 3 and Small 4; keep whichever wins cost-per-accepted-result per task class
  2. Month 2: re-check the Modified MIT terms and Hugging Face gating before expanding self-hosted footprints
  3. Month 3: revisit Mistral’s lineup — Small 4, Ministral 3, and Magistral move fast enough to obsolete your routing table

7. Verdict

Medium 3.5 is the first Mistral release I’d default to for agent loops instead of chat: 77.6% SWE-Bench Verified in a 128B dense model you can actually self-host, with an EU-hosted API behind it. The $7.5 output price means you deploy it surgically, not everywhere.

✅ Use It When

  • Agents call tools in loops and success rate dominates cost
  • You need open weights with a managed-API fallback
  • EU data residency simplifies your compliance review
  • You’re already on Devstral 2 or Medium 3 agents
  • Self-hosting on ~4 GPUs fits your infra budget
  • Structured outputs feed downstream code directly

❌ Skip It When

  • Workload is plain chat or summarization at volume
  • Output-heavy pipelines with no retry budget analysis
  • You need Apache 2.0 license simplicity
  • Context routinely exceeds 200K effective tokens
  • A smaller model already passes your evals
  • You can’t pin versions in a preview cycle

Verdict

For enterprise agent work, Medium 3.5 is Mistral’s best open-weight option in 2026: trial it on your hardest 200 agentic prompts, route everything else down-tier, and let cost per accepted result — not hype — decide what stays.

Conclusion

Mistral Medium 3.5 consolidates Mistral’s agent story into one 128B open-weight model: 256K context, 77.6% SWE-Bench Verified, $1.5 input / $7.5 output, self-hostable from four GPUs. It replaces Devstral 2 in Vibe and becomes the Le Chat default for a reason — long-horizon reliability.

Start hosted with mistral-medium-latest tonight, measure against Large 3 and Small 4 on your own prompts, and only then decide what to self-host. That’s the whole enterprise playbook in one paragraph.

Recap: The Three Numbers

Model

  • • 128B dense, 256K context
  • • Modified MIT open weights
  • • mistral-medium-latest

Price

  • • $1.5 in / $7.5 out per 1M
  • • Batch −50%, cache up to −90%
  • • Enterprise APIs +75%

Start

  • • pip install mistralai
  • • console.mistral.ai key
  • • Eval 200 prompts first
Diego Rodriguez

Diego Rodriguez

Senior Full-Stack & AI Engineer

Diego has 10+ years of experience building production-grade AI-powered applications, from LLM orchestration and RAG pipelines to ML-driven risk detection and algorithmic trading systems.

Learn more about Diego