Favicon for minimax

MiniMax: MiniMax M3

MiniMax-M3 is a multimodal foundation model from MiniMax. It supports text, image, and video inputs with text output, a 1M-token context window, and is suited for long-horizon agentic work, coding, and tool use. It is built on MiniMax Sparse Attention (MSA), which replaces full attention with KV-block selection to cut per-token compute at long context — roughly 1/20 the cost of the previous generation at 1M tokens, with substantially faster prefill and decode while retaining quality across most tasks.

Trained as a native multimodal model on interleaved data and tuned for multi-turn, production-like collaboration via an interactive user-simulator framework, the model is oriented toward sustained, multi-step tasks rather than single-turn execution.

Modalities
In / out price
$0.23 / $0.96per 1M
Context
1.0M
Released
May 31, 2026

Providers

Different companies host the same model. OpenRouter routes your request to one of them based on the routing mode you pick: Balanced (price + speed), Nitro (fastest), or Floor (cheapest).

Pricing

The average price customers actually pay for this model, next to the prices providers post. Caching and discounts mean the price actually paid is often well below the listed one.

Weighted average

Input
$0.07703/M tokens
Output
$1.142/M tokens
Price history
No effective price data for this selection

Performance

Throughput is how fast the model writes (tokens per second — higher is better). Latency is total round-trip time (lower is better). TTFT is time-to-first-token — how long before you see anything appear (lower is better).

Throughput
111tok/s

P50, best across providers

Latency
0.54s

P50, best provider

AutoExacto benchmarks
GPQA DiamondTAU-BenchDeepInfra94.5%--Parasail90.7%74.6%MiniMax90.5%74.1%ModelRun90.4%74.2%Together91.4%72.9%Parasail (Fast)91.1%70.0%
+9 more providers

Uptime

Uptime is the percentage of the past 3 days that at least one provider was responding to requests. Availability is the percentage of time that inference was successfully served. OpenRouter continuously monitors and uses the next-best provider when one returns an error.

Uptime (3d)The model was reachable. Request routed to a provider.
100.00%
Availability (3d)The model returned inference from any provider. Errors and empty responses count against it.
99.54%

Availability over the last 3 days

Last 72 hours
Availability 99.54%
3 Days Ago2 Days AgoYesterdayNow

Availability over the last 24 hours

OpenRouter Availability
99.57%
Without Routing
91.00%

When an error occurs in an upstream provider, we can recover by routing to another healthy provider, if your request filters allow it. You can access per-provider uptime data programmatically through the Endpoints API. Learn more about our load balancing and provider routing options.

Benchmarks

Scores on standardized evaluations and this model’s own outputs on shared benchmark prompts. Higher percentages are better — and each rank shows where this model lands among the models evaluated on that source.

Apps

Public apps that send the most traffic to this model. Good signal for what real production workloads look like — and a hint at which use cases this model is best suited for.

2.
Favicon for https://nousresearch.com
Hermes Agent
418Btokens
3.
Favicon for https://openclaw.ai/
OpenClaw
130Btokens
4.
Favicon for https://kilocode.ai/
Kilo Code
57.1Btokens
5.
Favicon for https://mira.tg/
Mira
42.2Btokens
Top 5 Apps
43.7B
Rest of OpenRouter
28.3B

Activity

Token volume and request traffic to this model over time.

API

Drop-in code to call this model. OpenRouter's API is OpenAI-compatible — most SDKs work by just swapping the base URL. The only thing that changes between models is the model slug below.

Not currently available through EU in-region routing. In-region routing docs

Frequently asked questions