The MiniMax M1 80k API worked through our longest analysis prompts without us trimming the context.
MiniMax M1 80k is MiniMax-M1 in its 80K thinking-budget setting — an open-weight, hybrid lightning-attention reasoning model with a 1M-token context window, giving it deep room to reason over long documents, math, hard coding, and agentic tool use. Served on RouterBase over an OpenAI-compatible endpoint at $0.40 / 1M input and $2.20 / 1M output, 5% under list; it is the deeper-thinking sibling of the 40k variant.
MiniMax M1 80k API — Long-Context Reasoning with an 80K Thinking Budget
The MiniMax M1 80k API serves MiniMax-M1 in its 80K thinking-budget setting — an open-weight hybrid-attention reasoning model with a 1M-token context window.
MiniMax M1 is an open-weight, hybrid-attention reasoning model: its lightning-attention design scales long reasoning efficiently, and it reads up to a 1M-token context. The MiniMax M1 80k API runs the 80K thinking-budget variant, giving the model more room to reason step by step before it answers — the deeper-thinking sibling of the 40k setting. That makes it a strong fit for long-context analysis, math, hard coding, and agentic tool use, where the extra thinking pays off.
You reach the MiniMax M1 80k API through RouterBase on the OpenAI chat-completions protocol; set the model to minimax-m1-80k and your client is unchanged. The MiniMax M1 80k API bills $0.40 per 1M input tokens and $2.20 per 1M output — 5% under list, on one key that reaches the whole catalog.
What the MiniMax M1 80k API gives you
Room to think, and room to read.
Hybrid lightning attention
MiniMax M1 uses a hybrid lightning-attention design, so the MiniMax M1 80k API scales long reasoning without the usual cost curve.
80K thinking budget
The MiniMax M1 80k API gives the model an 80K-token thinking budget — more room to reason than the 40k setting.
1M-token context
A 1M-token window lets the MiniMax M1 80k API hold long documents, codebases, and tool traces in one call.
Reasoning, math, code
Extended thinking makes the MiniMax M1 80k API strong on long-context analysis, math, and hard coding.
Agentic tool use
Reliable function calling makes the MiniMax M1 80k API a solid backbone for tool-using agents.
Open weights, hosted
MiniMax M1 is open-weight; the MiniMax M1 80k API gives you managed access without running it yourself.

First call to the MiniMax M1 80k API in three steps
Wire it once, then feed it the long, hard problems.
Create a key
One RouterBase key reaches the MiniMax M1 80k API and every other model in the catalog.
Point and name
Send any OpenAI client to routerbase.com/v1 with model=minimaxai/minimax-m1-80k. Streaming and function calling work out of the box.
Feed it long context
The MiniMax M1 80k API takes up to a 1M-token context and returns usage per response, so cost stays visible on every call.
Pay only for what you use
RouterBase passes through partner-tier pricing. Compared against the model's official published API rate.
Teams building on the MiniMax M1 80k API
Long context and extended thinking, put to work.
The 80K thinking budget got the MiniMax M1 80k API to solutions the shorter setting missed.
A 1M-token window let the MiniMax M1 80k API read our whole spec in one pass.
At $0.40 in, the MiniMax M1 80k API gave us deep reasoning without a flagship bill.
Function calling held up, so our agents run their hardest steps on the MiniMax M1 80k API.
On long math chains, the MiniMax M1 80k API stayed coherent where others drifted.
Hybrid attention meant long context on the MiniMax M1 80k API did not blow up our latency.
Switching to the MiniMax M1 80k API was one string, and the extended reasoning was worth it.
We route deep-reasoning tasks to the MiniMax M1 80k API and keep everything on one key.
MiniMax M1 80k API — common questions
What to know before you route traffic to it.
RouterBase's hosted access to MiniMax-M1 in its 80K thinking-budget setting — an open-weight hybrid-attention reasoning model — over an OpenAI-compatible endpoint.