Route requests to
Ministral 3 14B
with Merge Gateway

Apply your own routing policies, reduce token costs automatically, and see every routing decision in real time with Merge Gateway.

What Ministral 3 14B costs to run

| Vendor | Input / 1M tokens | Output / 1M tokens | Zero data retention | | --- | ---: | ---: | --- | | Amazon Bedrock | $0.2000 | $0.2000 | Yes | | Mistral | $0.2000 | $0.2000 | No |

Test Ministral 3 14B
with Gateway’s Simulator

See a prompt's output, token spend, latency, and more with Ministral 3 14B.

Route requests to Ministral 3 14B in minutes

To get started in seconds, add our Gateway Implementation skill to your project, or pick your preferred SDK below. Check out our other quick start skills here.
Install the Merge Gateway SDK
Python
Copied!
1$ pip install merge-gateway-sdk
Send a request
Python
Copied!
1from merge_gateway import MergeGateway
2
3client = MergeGateway(api_key="YOUR_API_KEY")
4
5response = client.responses.create(
6    model="openai/gpt-5.2",
7    input=[
8        {"type": "message", "role": "system", "content": "You are a helpful programming tutor. Explain the concepts clearly with practical examples."},
9        {"type": "message", "role": "user", "content": "Explain the concept of recursion in programming with a simple set of examples."},
10    ],
11)
12
13print(response.output[0].content[0].text)
Try a diffrent model
Swap the model string to route to a different provider. No other code changes needed.
Anthropic
Copied!
1response = client.responses.create(
2    model="anthropic/claude-sonnet-4-20250514",
3    input=[
4        {"type": "message", "role": "system", "content": "You are a helpful programming tutor. Explain the concepts clearly with practical examples."},
5        {"type": "message", "role": "user", "content": "Explain the concept of recursion in programming with a simple set of examples."},
6    ],
7)
Point to Gateway
Python
Copied!
1from openai import OpenAI
2
3client = OpenAI(
4    api_key="YOUR_API_KEY",
5    base_url="https://api-gateway.merge.dev/v1/openai",
6)
Send a request
Use the standard chat.completions.create method. No provider prefix needed on the model name.
Python
Copied!
1response = client.chat.completions.create(
2    model="gpt-5.2",
3    messages=[
4        {"role": "system", "content": "You are a helpful programming tutor. Explain the concepts clearly with practical examples."},
5        {"role": "user", "content": "Explain the concept of recursion in programming with a simple set of examples."},
6    ],
7)
8
9print(response.choices[0].message.content)
Install packages
Copied!
1npm install merge-gateway-ai-sdk-provider ai
Create the provider
TypeScript
Copied!
1import { createMergeGateway } from "merge-gateway-ai-sdk-provider";
2
3const gateway = createMergeGateway({
4  apiKey: "YOUR_API_KEY",
5});
Send a request
Use generateText to send a request. Model names use the provider/model format.
TypeScript
Copied!
1import { generateText } from "ai";
2
3const { text } = await generateText({
4  model: gateway("openai/gpt-4o"),
5  prompt: "Explain the concept of recursion in programming with a simple set of examples.",
6});
7
8console.log(text);
If you already have @ai-sdk/openai installed, point it at Gateway with a base URL change:
TypeScript
Copied!
1import { createOpenAI } from "@ai-sdk/openai";
2
3const gateway = createOpenAI({
4  apiKey: "YOUR_API_KEY",
5  baseURL: "https://api-gateway.merge.dev/v1/ai-sdk",
6});
7
8// All generateText/streamText calls work unchanged
Install the Merge Gateway SDK
Anthropic SDK
Copied!
1from anthropic import Anthropic
2
3client = Anthropic(
4    api_key="YOUR_API_KEY",
5    base_url="https://api-gateway.merge.dev/v1/anthropic",
6)
7
8message = client.messages.create(
9    model="claude-sonnet-4-20250514",
10    max_tokens=1024,
11    messages=[
12        {"role": "user", "content": "Explain the concept of recursion in programming with a simple set of examples."},
13    ],
14)
15
16print(message.content[0].text)

Explore other models available in Merge Gateway

model logo
Amazon Nova 2 Lite
model logo
Amazon Nova 2 Sonic
model logo
Amazon Nova Lite
model logo
Amazon Nova Micro
model logo
Amazon Nova Premier
model logo
Amazon Nova Pro
model logo
Claude 3.7 Sonnet
model logo
Claude Haiku 4.5 (20251001)
model logo
Claude Opus 4.6
model logo
Claude Opus 4.7
model logo
Claude Opus 4.8
model logo
Claude Sonnet 4.5
model logo
Claude Sonnet 4.6
model logo
Claude Sonnet 5
model logo
Codestral
model logo
Codestral 25.08
model logo
Command R 08-2024
model logo
Command R+ 08-2024
model logo
Command R7B 12-2024
model logo
DeepSeek R1
model logo
DeepSeek V3
model logo
DeepSeek V3.2
model logo
DeepSeek V4 Flash
model logo
DeepSeek V4 Pro

Ministral 3 14B FAQ

In case you have any other questions on Ministral 3 14B, we've answered a few more below. It's worth noting that the information below was written in July, 2026 and is subject to change.

Heading

What other models does Mistral AI offer?

Mistral AI ships small edge models alongside general-purpose, coding, and reasoning lines. Here are some other models Mistral AI supports:

  • Ministral 3 8B: the mid-size edge model in the same line, for on-device and low-latency workloads
  • Mistral Small: a compact, open-weight general model that sits above the Ministral edge tier
  • Mistral Nemo: a small, open-weight 12B model for affordable, self-hostable inference
  • Mistral Medium 3.5: the mid-tier general model, balancing quality and cost with multimodal input

How does Ministral 3 14B differ from Mistral AI's other models?

Ministral 3 14B is the largest model in Mistral's edge-focused line, built for on-device and low-latency inference rather than frontier cloud reasoning.

  • Edge focus: tuned to run close to the user with low latency, unlike the larger hosted-first general models
  • Size: the 14B tier is the most capable of the Ministral edge models, above the 8B and 3B options
  • Capabilities: supports function calling for its class, which suits agentic tasks at the edge
  • Position vs Mistral Small: narrower general-purpose breadth than Small, traded for a footprint that fits local and constrained deployments

Reach for Ministral 3 14B when you want the strongest Ministral edge model for on-device or latency-sensitive tasks rather than a large cloud model.

What models should I consider using alongside Ministral 3 14B?

No single model is optimal for every task. Here are models worth pairing with Ministral 3 14B depending on what your product needs:

  • Mistral Small as the step up when a task needs more general-purpose breadth than an edge model provides
  • Claude Opus 4.8 for the hardest reasoning or coding tasks that need frontier quality in the cloud
  • Ministral 3 8B for lighter edge workloads where the 14B tier is more than you need
  • Mistral Nemo as another small, open-weight model to benchmark against

What are the challenges of using Ministral 3 14B in my product?

Like any production LLM, Ministral 3 14B comes with tradeoffs worth planning for:

  • Quality ceiling: as an edge-scale model, it trails larger cloud models on complex reasoning and long-form generation, so plan an escalation path
  • Deployment operations: running it on-device or at the edge means owning packaging, updates, and hardware constraints
  • Provider dependency: if you use the hosted version, relying only on Mistral is fragile during outages or retirements
  • Cost at scale: cheap per token in the cloud, but very high volumes still compound, so budgeting stays relevant
  • Task fit: best on focused edge tasks, so route heavy reasoning to a larger model rather than pushing it past its range

Why should I use Merge Gateway to route LLM requests with Ministral 3 14B and every other model?

Using Ministral 3 14B through Merge Gateway gives you access to the model itself and the infrastructure layer around it:

  • One API, every provider: Reach Ministral 3 14B and every other major LLM through a single endpoint and API key, swapping the model string to change providers without touching application code
  • Intelligent routing and automatic failover: Merge routes around Mistral outages automatically, and an edge-to-cloud quality ladder is easy to express as a policy that can cut spend 40 to 60%
  • Cost governance: Set hard or soft project budgets so spend stays in plan, with every request attributed to a model, project, and tag in one billing dashboard
  • Build Your Own Router: Define what "best" means with curated benchmarks or your own evals, and the router keeps light tasks on the edge model and escalates only when needed
  • Security and compliance controls: Apply DLP rules and prompt injection protection before requests reach Mistral, and enforce per-project model and region policies outside your application

How can I start routing requests to Ministral 3 14B via Merge Gateway?

Getting Ministral 3 14B running through Merge Gateway takes a few minutes:

1. Create an account and get your API key from the dashboard.

2. Install the Merge Gateway SDK: run pip install merge-gateway-sdk (Python) or npm install merge-gateway-sdk (Node). Alternatively, if you're already using the OpenAI SDK, set base_url = "https://api-gateway.merge.dev/v1/openai" and your existing code works as-is.

3. Make your first request using the provider/model format. For Ministral 3 14B, the model string is mistral/ministral-14b-2512 (confirm the exact slug in the dashboard). Swap the model string to route to any other provider without changing anything else.

4. Configure a routing policy in the dashboard to set failover behavior, cost limits, and optimization strategy. Your first policy can be as simple as naming Ministral 3 14B as primary with one fallback.

Full setup instructions and SDK references are in the Merge Gateway docs.

Try Ministral 3 14B through Merge Gateway

Route, observe, and control AI requests across providers from one API.