MiniMax M2.5 High Speed
MiniMax M2.5 High Speed is the throughput-optimized variant that retains M2.5's full planning and software engineering capabilities.
View API reference- Input and output price
- Prices from: Input $0.60, Output $2.40, Per 1M tokens
- 24h uptime
- Loading AI Gateway uptime
import { streamText } from 'ai'
const result = streamText({ model: 'minimax/minimax-m2.5-highspeed', prompt: 'Why is the sky blue?'})Copy link to headingPlayground
Try out MiniMax M2.5 High Speed by MiniMax. Usage is billed to your team at API rates. Free users (those who haven't made a payment) get $5 of credits every 30 days.
MiniMax M2.5 High Speed
MiniMax M2.5 High Speed
Copy link to headingProviders
Route requests across multiple providers. Copy a provider slug to set your preference. Visit the docs for more info. Using a provider means you agree to their terms, listed under Legal.
Copy link to headingUptime24 hours
Direct request success rate on AI Gateway and per-provider. Visit the docs for more info.
Copy link to headingThroughput24 hours
P50 throughput on live AI Gateway traffic, in tokens per second (TPS). Visit the docs for more info.
Copy link to headingLatency24 hours
P50 time to first token (TTFT) on live AI Gateway traffic, in milliseconds. View the docs for more info.
Getting started
Call MiniMax M2.5 High Speed through AI Gateway with the AI SDK generateText and streamText functions, or through the OpenAI Chat Completions, OpenAI Responses, and Anthropic Messages APIs by changing the base URL. AI Gateway authenticates the request and routes it to an available provider.
Install the AI SDK (pnpm add ai dotenv), create an API key from the API Keys page, and set it as AI_GATEWAY_API_KEY in your environment. Full setup is covered in the text generation quickstart.
import { generateText } from 'ai';import 'dotenv/config';
async function main() { const result = await generateText({ model: 'minimax/minimax-m2.5-highspeed', prompt: 'Why is the sky blue?', });
console.log(result.text);}
main().catch(console.error);Top-level parameters
The same MiniMax M2.5 High Speed request in each API format AI Gateway supports.
import { generateText } from 'ai';import 'dotenv/config';
async function main() { const result = await generateText({ model: 'minimax/minimax-m2.5-highspeed', system: 'You are a concise technical assistant.', prompt: 'Summarize the tradeoffs between static generation and SSR.', maxOutputTokens: 1024, });
console.log(result.text);}
main().catch(console.error);Standard parameters like prompt, messages, temperature, and tools work as documented in the AI SDK docs. These are the parameters with model-specific behavior.
| Parameter | Type | Required | Description |
|---|---|---|---|
model | string | Yes | Model ID in the form creator/model, e.g. minimax/minimax-m2.5-highspeed. AI Gateway routes the request to an available provider. |
maxOutputTokens | number | No | Hard cap on generated tokens. MiniMax M2.5 High Speed supports up to 131,100 output tokens. Reasoning tokens count toward this limit. |
reasoning | 'provider-default' | 'none' | 'minimal' | 'low' | 'medium' | 'high' | 'xhigh' | No | Provider-agnostic reasoning effort, available in AI SDK 7 or later. Maps to the provider’s native reasoning configuration; reasoning settings under providerOptions take precedence when both are set. See the Reasoning section below. |
providerOptions | Record<string, JSONValue> | No | AI Gateway routing options under gateway, plus any provider-native options under the provider’s own namespace — see the table below. |
Input limits
| Input | Formats | Sources | Max count | Max size | Limits |
|---|---|---|---|---|---|
| Text | — | — | — | — | Prompt and response share the 205K-token context window |
Provider options
Set AI Gateway routing options under providerOptions.gateway. For provider-specific options, pass them under the provider’s namespace as documented by the AI SDK.
Learn more in the AI SDK provider docs.
import { generateText } from 'ai';import 'dotenv/config';
async function main() { const result = await generateText({ model: 'minimax/minimax-m2.5-highspeed', prompt: 'Why is the sky blue?', providerOptions: { gateway: { only: ['minimax', 'novita'], }, }, });
console.log(result.text);}
main().catch(console.error);These AI Gateway routing options apply to every model. Provider-specific options pass through under the provider’s own namespace (for example providerOptions.anthropic) exactly as documented by the AI SDK.
| Parameter | Type | Required | Description |
|---|---|---|---|
providerOptions.gateway.only | string[] | No | Restrict routing to these provider slugs. Requests fail over only within the listed providers. |
providerOptions.gateway.order | string[] | No | Preferred provider order. Listed providers are tried first; unlisted providers remain available as fallbacks. |
providerOptions.gateway.sort | 'cost' | 'ttft' | 'tps' | No | Rank candidate providers by price, time to first token, or tokens per second instead of the default routing order. |
providerOptions.gateway.zeroDataRetention | boolean | No | Route only to providers with a zero-data-retention policy for this model. |
Routing across providers
AI Gateway serves the same model through multiple providers and fails over automatically. order expresses a preference while keeping every provider eligible; only is a hard allowlist — if none of the listed providers are available the request fails instead of falling back.
Options under a provider's own namespace (for example providerOptions.anthropic) are forwarded to that provider with the request. Providers ignore option namespaces that don't apply to them, so it is safe to set provider options alongside gateway routing options.
Reasoning
AI Gateway bridges reasoning across every API format. The AI SDK exposes a provider-agnostic top-level reasoning level (none, minimal, low, medium, high, or xhigh); the Chat Completions and Responses formats take the same effort under reasoning.effort; and the Anthropic Messages format uses a native thinking token budget. Whichever you send, the gateway maps it to the target model’s native configuration, converting between effort levels and token budgets as needed. Reasoning-related settings under providerOptions take full precedence over the top-level reasoning value and are never merged. Reasoning tokens typically count toward your output-token usage, though how they’re reported and billed varies by provider.
Learn more in the AI Gateway reasoning guide.
import { generateText } from 'ai';import 'dotenv/config';
async function main() { const result = await generateText({ model: 'minimax/minimax-m2.5-highspeed', prompt: 'Explain the Monty Hall problem step by step.', reasoning: 'high', });
console.log(result.text);}
main().catch(console.error);Tool calling
Expose tools the model can call. Define each tool’s inputs with a Zod schema.
import { generateText, tool } from 'ai';import { z } from 'zod';import 'dotenv/config';
async function main() { const result = await generateText({ model: 'minimax/minimax-m2.5-highspeed', prompt: 'What is the weather in San Francisco?', tools: { getWeather: tool({ description: 'Get the current weather for a location', inputSchema: z.object({ location: z.string() }), execute: async ({ location }) => ({ location, temperatureC: 18 }), }), }, });
console.log(result.text);}
main().catch(console.error);Copy link to headingMore models by MiniMax
| Model |
|---|
| 1M | 0.7 s | 158 tps | $0.26/M | $1.02/M | Read$0.06/M | — | +2 |   +2 | 05/31/2026 | |||||
| 205K | 1.1 s | 54 tps | $0.30/M+1 more | $1.20/M+1 more | Read$0.06/M Write$0.38/M | — |  | 03/18/2026 | ||||||
| 205K | 0.9 s | 65 tps | $0.60/M | $2.40/M | Read$0.06/M Write$0.38/M | — | | 03/18/2026 | ||||||
| 1M | 0.6 s | 78 tps | $0.27/M+1 more | $0.95/M+1 more | Read$0.03/M Write$0.38/M | — |   +1 | 02/12/2026 | ||||||
| 205K | 0.5 s | 140 tps | $0.30/M | $1.20/M | Read$0.03/M Write$0.38/M | — | | 12/23/2025 | ||||||
| 205K | 0.8 s | 82 tps | $0.30/M | $1.20/M | Read$0.03/M Write$0.38/M | — | | 10/27/2025 |
Copy link to headingAbout MiniMax M2.5 High Speed
MiniMax M2.5 High Speed targets autonomous coding agents that run for extended periods and need fast token generation. See live metrics on this page for current throughput. For cost estimates, use and your expected token volumes rather than a fixed hourly figure.
The "highspeed" label doesn't indicate a distilled or reduced-capability model. MiniMax M2.5 High Speed retains the full architectural planning mode of standard M2.5. It decomposes problems into specifications before writing code, handles the complete development lifecycle across Web, Android, iOS, Windows, and Mac platforms, and matches the same reported SWE-Bench Verified score as standard M2.5.
The tradeoff is straightforward: you pay roughly twice as much per token in exchange for generating tokens roughly twice as fast on paper. For batch jobs where wall-clock time doesn't matter, standard M2.5 is more economical. For interactive sessions, streaming UIs, and agent loops where latency compounds, the highspeed variant can win.
Copy link to headingWhat To Consider When Choosing a Provider
- Configuration: The highspeed variant lists at roughly double the standard M2.5 input and output rates on many providers. AI Gateway's per-request cost tracking lets you measure whether the throughput gain pays for itself in your workload before you commit at scale.
- Zero Data Retention: Zero Data Retention is offered on a per-provider and model basis. See the documentation for details.
- Authentication: AI Gateway authenticates requests using an API key or OIDC token. You do not need to manage provider credentials directly.
Copy link to headingWhen to Use MiniMax M2.5 High Speed
Best for
- Long-running coding agents: Autonomous sessions that span multi-minute or multi-hour workflows
- Streaming pair-programming: Chat interfaces where token delivery speed is user-visible
- High-concurrency services: Per-request latency accumulates across simultaneous users
- Wall-clock time priority: Halving inference time justifies a 2x per-token cost increase
Consider alternatives when
- Fast tasks anyway: Your tasks complete in seconds regardless of throughput, so the speed premium has no practical impact
- Cost over latency: Per-token cost is a harder constraint than latency and standard M2.5 delivers the same output for less
- Multi-agent coordination: You need the features introduced in M2.7
Copy link to headingConclusion
MiniMax M2.5 High Speed occupies a clear niche: same model, faster output, higher price. It's the right pick when your agent or application is bottlenecked on token generation speed and the cost difference is justified by reduced wall-clock time or improved user experience.
Copy link to headingFrequently Asked Questions
Is there any quality difference between MiniMax M2.5 High Speed and standard M2.5?
None. Both variants share the same architecture, planning capabilities, and benchmark scores. The "highspeed" designation reflects inference throughput only.
What development tasks does MiniMax M2.5 High Speed cover?
MiniMax M2.5 High Speed handles the full development lifecycle: specification writing, code generation, debugging, and deployment across Web, Android, iOS, Windows, and Mac platforms.
How does the pricing compare to standard M2.5?
Check the pricing panel on this page for today's numbers. AI Gateway tracks rates across every provider that serves MiniMax M2.5 High Speed.
What throughput can I expect?
Live throughput metrics display on this page and update based on real traffic.
Should I use MiniMax M2.5 High Speed or M2.7 Highspeed?
If you don't need M2.7's multi-agent orchestration or dynamic tool search, MiniMax M2.5 High Speed is more cost-effective at comparable speeds.
Can I try this model before integrating it?
Yes. Use the playground on this page to evaluate output quality and perceived speed interactively.