NotCheap MAKE EVERY CREDIT COUNT
Analyze Your Costs

Mistral Vibe Pricing: Subscription, Coding and API Costs

Share this guide

Mistral Vibe Pro costs $14.99 a month before tax. It unlocks high-tier assistant capabilities and deep coding tools. Metered developer usage across Mistral Studio, API endpoints, and Vibe Code all draws against one unified, shared allowance. Before you upgrade, compare the team features you actually need and look at your real console usage. That will tell you whether a fixed seat subscription or periodic pay-as-you-go credit fits your budget better.

All subscription tiers and billing mechanics were verified 25 October 2026. The coding benchmarks and workload volumes below are concrete engineering scenarios, not vendor productivity claims.

What happened to Le Chat?

If you're wondering where Le Chat went, Mistral's Vibe documentation covers the full rebrand of its productivity and coding platform. Under the Vibe banner, Vibe Work is the interactive web and mobile assistant, and Vibe Code handles agentic programming in your terminal, IDE, and browser. Mistral Studio carries on as the developer console, where you manage API keys, evaluate model weights, and keep an eye on token consumption.

It pays to keep these three surfaces straight when you open your monthly invoice. A chat in Vibe Work, an automated coding session in Vibe Code, and an API integration in your codebase can all hang off one organization. That doesn't mean every interaction gets unlimited usage. Double-check which organization workspace receives the billable event.

Subscription choices

PlanPublished monthly price, before taxWhen to consider it
Free$0Explore the assistant and limited coding access
Pro$14.99More assistant access and regular coding workflows
Education$5.99 for eligible verified studentsCheck eligibility and the limited offer period
Team$24.99 per userShared workspace and administration
EnterpriseQuoteContractual deployment and governance requirements

On the live pricing page, Mistral shows a $50 monthly total for the default two-seat Team tier. Slide the user selector to five seats and you'll see roughly $125. That matches five times $24.99 ($124.95 before interface rounding). There's no extra $50 base workspace fee stacked on top of the seat total.

Five individual Pro subscriptions would come to $74.95, but individual licenses don't give you shared admin controls, unified workspace billing, or centralized security governance. So the real question is whether those collaboration features are worth roughly $50 more each month. Headcount alone doesn't make the decision for you.

Included usage is shared

The official subscription guide explains that included monthly usage is pooled across Mistral Studio, raw API endpoints, and Vibe Code. That allowance is always used up first, before any prepaid wallet balance is touched. You can see your organization's active grant and live consumption in the Subscription admin dashboard.

The public Pro marketing card highlights $25.50 per month in included API credits, and the Education tier shows a $15.00 grant. Always confirm the allowance shown in your own account settings. A headline credit doesn't translate into a fixed number of finished coding tasks. Model choice, prompt context length, output verbosity, and concurrent developer usage all decide how long that balance lasts.

It helps to think of your subscription fee and your included usage as two separate things. Paying $14.99 is real cash leaving your card. The included allowance is spending room inside Mistral's ecosystem. It isn't refundable, it can't pay external cloud bills, and you shouldn't add it to your plan price as if it were a second charge.

A coding workload you can recalculate

Let's model a real workload on Mistral Medium 3.5 to see how metered consumption behaves. Mistral's model pricing table lists $1.50 per million uncached input tokens, $0.15 per million cached input tokens, and $7.50 per million output tokens under standard processing (excluding batch or regional markups).

Say a developer coding session uses 50,000 uncached input tokens, 150,000 cache-hit input tokens, and 12,000 output tokens across its automated code refactoring steps:

CalculationResult
Uncached input: 0.05 million × $1.50$0.0750
Cached input: 0.15 million × $0.15$0.0225
Output: 0.012 million × $7.50$0.0900
Gross usage value per session$0.1875
40 sessions: 40 × $0.1875$7.50
Without cache hits: 40 × (0.20M × $1.50 + 0.012M × $7.50)$15.60

Prompt caching cuts execution cost dramatically. The practical catch is that you should confirm cache hits in your telemetry rather than assuming them just because a repo was queried earlier. Without caching, those same 40 sessions climb to $15.60.

That $7.50 is the gross metered consumption of the 40 sessions, not necessarily what lands on your invoice. Suppose your organization has $5.00 of its monthly included allowance left. The plan absorbs the first $5.00, and only the remaining $2.50 falls to prepaid overage. If you have at least $7.50 of grant remaining, the whole batch is covered at no extra cost.

This is exactly why we won't promise that Pro covers 40 sessions with room to spare. Heavy context dumps, deep multi-file refactors, or concurrent API scripts can drain your allowance much faster. Start with one representative developer task, log its actual token burn, and extrapolate capacity from real numbers.

Prepaid cash, consumption and spending controls

Per Mistral's billing documentation, API and Vibe Code calls that go beyond your included allowance need active pay-as-you-go billing backed by a positive prepaid wallet balance. If that balance hits zero, later API calls fail with an HTTP 402 error. Usage metering can lag by several minutes, though, so rapid parallel requests can push your balance slightly negative before the gateway stops traffic.

Here's a simple scenario. You deposit a $20.00 top-up and rack up $8.00 in metered overage. In cash terms, you transferred $20.00, consumed $8.00, and still have a $12.00 active balance for future requests. On a Pro subscription, your total cash outlay is $34.99 ($14.99 plan fee + $20.00 deposit), while your net consumed expense is $22.99 ($14.99 fee + $8.00 overage). The remaining $12.00 is working capital sitting in your account, not a sunk cost.

Take a look at your auto-recharge rules and organization spending caps. Mistral enforces budget caps before sales tax, while wallet deductions include applicable VAT/sales tax. That means tax can nibble your balance down slightly before you reach the raw usage cap. Keep a small buffer so your workflows don't get interrupted at a bad moment.

Our purchasing rule

Subscribe to Pro if you or your engineers use the web assistant and Vibe Code daily. For background batch processing or occasional API tasks, measure your monthly token volume first, because your included allowance may cover the work entirely. Team plans make sense when centralized governance and shared workspaces are mandatory, and Enterprise is for strict data compliance needs. Please don't buy a higher tier just for a shiny marketing credit badge.

For production applications, budget model endpoints separately from seat licenses. Keep document parsing, voice synthesis, and language reasoning on separate balance sheets, and verify output accuracy before swapping models. Our API cost comparison and Mistral model guide go deeper if you're planning a custom build.

Common questions

Is Vibe Pro an unlimited API subscription?

No. Developer API and Vibe Code requests draw from a shared monthly grant, followed by prepaid credits when pay-as-you-go is enabled. Check the Subscription panel in your console for your real-time allowance.

Does the Team card add a separate $50 base fee?

No. The live pricing selector shows roughly $125 for five users ($24.99 per seat), not $175. Still, verify your currency, local tax, and the final checkout screen before you confirm payment.

Does a prepaid balance guarantee no overrun?

No. Processing latency can delay reporting, so high-concurrency jobs may take the wallet slightly negative before rate limits kick in. Set strict organization spending caps alongside your auto-recharge settings.

Should I select a plan for privacy reasons?

Look at the current data retention policies and commercial terms for the specific tool surface you use. Don't assume privacy terms from the company's location or the word Pro. Read the privacy policy and check your workspace data controls directly.

PASS IT ON

Useful for your team?

Share this guide with a colleague.