API Integration Guide
Mistral Medium 3.5 uses an OpenAI-compatible API. The model ID is mistral-medium-3.5 and the base URL is https://api.mistral.ai/v1. For teams already using the OpenAI Python SDK, switching requires changing two values and nothing else for basic requests:
from openai import OpenAI
client = OpenAI(
api_key="your-mistral-api-key",
base_url="https://api.mistral.ai/v1"
)
response = client.chat.completions.create(
model="mistral-medium-3.5",
messages=[
{"role": "user", "content": "Review this function for edge cases."}
]
)
print(response.choices[0].message.content)
Configurable reasoning uses the budget_tokens parameter. For conversational tasks, a value of 512 keeps latency low. For complex coding or analytical tasks, values between 2048 and 8192 give the model enough compute to work through multi-step reasoning before responding:
response = client.chat.completions.create(
model="mistral-medium-3.5",
messages=[{"role": "user", "content": "Refactor this module to be fully testable."}],
extra_body={"budget_tokens": 4096}
)
Vision input follows the standard multimodal message format. The model accepts both base64-encoded images and URL references. Because the vision encoder handles variable aspect ratios natively, you do not need to resize screenshots before sending them:
response = client.chat.completions.create(
model="mistral-medium-3.5",
messages=[{
"role": "user",
"content": [
{"type": "image_url", "image_url": {"url": "data:image/png;base64,..."}},
{"type": "text", "text": "What bug does this UI screenshot show?"}
]
}]
)
Tool calling uses the standard function calling schema. Define tools as JSON schemas in the tools array, and the model returns structured tool_calls when it decides to invoke a function. The finish_reason field in the response tells your agentic loop whether to execute tools and continue, or return the final answer. The request shape is close enough to the OpenAI standard that existing agent scaffolding built for GPT-5.5 works with Mistral Medium 3.5 after a one-line base URL change.
Pricing: Where Medium 3.5 Fits in the 2026 Market
API pricing is $1.50 per million input tokens and $7.50 per million output tokens. This is a significant increase from the previous Mistral Medium 3 pricing — some analyses put the increase at roughly 4x per token — but the benchmark improvement positions the model against frontier-tier competitors rather than mid-tier alternatives.
- Claude Opus 4.7: $5.00/M input, $25.00/M output
- Mistral Medium 3.5: $1.50/M input, $7.50/M output
- Mistral Small 4: substantially cheaper, appropriate for tasks that do not require 77.6% SWE-Bench capability
The pricing criticism at launch centers on the jump from Medium 3. For teams routing medium-complexity tasks to the previous model, the cost increase without changing routing logic is real. The counterargument is that Medium 3.5 handles tasks that previously required a Large model call, and the consolidated workload is cheaper overall when routing costs are accounted for. Self-hosted inference eliminates per-token costs entirely for teams with appropriate GPU infrastructure, which is a significant factor in total cost of ownership for high-volume production workloads.
Vibe Remote Coding Agents
Vibe is Mistral's coding agent IDE, and the April 29 update introduced remote execution mode: coding sessions run on Mistral's cloud infrastructure rather than the developer's local machine. This changes the economics of long-running coding tasks substantially. In the previous local-only mode, a 60-minute refactoring task occupied a terminal session for the full duration. With remote agents, the task runs in the cloud and the developer's CLI is immediately free.
Starting a remote agent session from the CLI:
mistral vibe --remote "Refactor the auth module to support OAuth 2.0 PKCE flow, add unit tests, and open a draft PR"
If you have an existing local Vibe session mid-task, the teleport feature moves session state — context, task progress, and file changes accumulated so far — to a cloud instance. The local CLI disconnects and you receive a webhook or email notification when the session completes. Multiple remote sessions run in parallel: a team can run separate refactoring, test-writing, and documentation tasks simultaneously across different cloud instances without resource contention.
When a session finishes, Vibe can automatically open a draft pull request with a summary of what the agent changed, which tests passed, and which edge cases it flagged but did not resolve. This is a similar pattern to the Claude Code subagent coordination approach, applied natively to the Mistral ecosystem. Remote compute pricing was not announced at launch; Mistral has indicated billing will be per compute-minute rather than per output token, making long-running tasks more predictable to cost.
Le Chat Work Mode: Agentic Task Execution in the Browser
Le Chat's Work Mode is a production release of multi-step agentic task execution inside Mistral's chat interface. Standard Le Chat is a conversational interface requiring back-and-forth input. Work Mode accepts a task description and executes it end-to-end without needing intermediate prompts.
The execution model uses parallel tool calling: multiple tools run simultaneously rather than sequentially. In a single Work Mode session, the agent can read an email thread, add a calendar event, draft a reply, create a Jira ticket from the action items, and post a summary to Slack — with the total latency closer to the longest single operation than the sum of all operations combined.
Integrations at launch include Google Workspace (Gmail, Calendar, Drive), Jira, Slack, GitHub, and Notion. Each integration uses OAuth and does not expose credentials to the model weights — the model issues tool calls and Mistral's infrastructure handles the actual API requests to connected services. For developers, Work Mode is also available programmatically through the Mistral Agents API, letting you embed the same parallel tool execution into custom products. See our guide on agentic AI governance for architectural context on deploying multi-step agents in production.
Self-Hosting Mistral Medium 3.5
The model weights are available on HuggingFace at mistralai/Mistral-Medium-3.5-128B under a modified MIT license. Hardware requirements: a minimum of four A100 80GB GPUs for basic inference, with eight GPUs recommended for concurrent production workloads with good throughput.
Starting a vLLM inference server with tool calling and reasoning support enabled:
vllm serve mistralai/Mistral-Medium-3.5-128B --tensor-parallel-size 8 --tool-call-parser mistral --enable-auto-tool-choice --reasoning-parser mistral
The --reasoning-parser mistral flag instructs vLLM to separate the model's internal reasoning trace from the final output in the response body — required if you want to log or display reasoning steps in your application. The --tool-call-parser mistral flag enables structured function calling output compatible with Mistral's tool calling format.
SGLang is an alternative inference backend with better batch efficiency at high request concurrency. For low-resource setups, Ollama supports quantized versions of Medium 3.5 that run on fewer GPUs at reduced quality — the quality reduction is more noticeable in multi-step coding tasks than in simple question-answering. For enterprise infrastructure, NVIDIA NIM containers are available with pre-configured tensor parallelism and quantization profiles for H100 clusters, which simplifies production deployment without manual vLLM parameter tuning.
When to Choose Mistral Medium 3.5
The model fits best in three scenarios. First, workloads that require coding capability at the frontier tier but are subject to data sovereignty or compliance constraints that prohibit closed-weight APIs. The modified MIT license permits commercial self-hosting without usage reporting. Second, production workflows that genuinely mix text, code, and image inputs in a single context — the native vision encoder and dense architecture handle this without model-switching overhead. Third, teams already invested in the Mistral ecosystem who want to use Work Mode and Vibe remote agents without adding new infrastructure.
Where Medium 3.5 is not the first choice: pure-text reasoning tasks with no coding or vision component, where Mistral Small 4 handles the workload at 10–20% of the per-token cost. The 4x price increase from Medium 3 is also a factor for teams with high-volume inference needs whose workloads do not require the full 77.6% SWE-Bench capability profile.
Quick decision rule: If your task involves code + images + long context and you need open-weight deployment, Medium 3.5 is the strongest option currently available. If it's pure text at high volume, route to Mistral Small 4 first and escalate only when Small 4 quality is insufficient.
Summary
Mistral Medium 3.5 is a 128B dense open-weight model that scores 77.6% on SWE-Bench Verified, ships under a modified MIT license, and is priced at $1.50 per million input tokens. The Vibe remote agent system makes long-running async coding tasks practical without tying up local resources. Le Chat Work Mode brings parallel multi-step agentic execution to the browser with OAuth-connected integrations. Self-hosting on four A100 GPUs eliminates per-token costs for high-volume workloads. For developers evaluating open-weight coding-capable models in May 2026, this release establishes a new cost-performance threshold: near-frontier benchmark numbers at roughly one-third the API cost of the top closed-weight alternatives.
Comments · 0
Beta: comments are stored locally on your device and not visible to other readers.
No comments yet. Be the first to share your thoughts.