# Atlas with MiniMax-M2.7-highspeed: The Fast Lane in 2026 > MiniMax-M2.7-highspeed costs $0.60 per Mtok input and $2.40 per Mtok output for priority serving on MiniMax's newest 230B MoE with a 204,800 token context. MiniMax-M2.7-highspeed is the fast lane for MiniMax's current agentic model. Same 230B MoE, same 204,800 token context, same 131,072 output cap as MiniMax-M2.7, at double the rate: $0.60 per Mtok input and $2.40 per Mtok output. Inside Atlas, MiniMax-M2.7-highspeed is what you run when a developer is sitting in the TUI waiting on reasoning tokens and the newest checkpoint is the one you want answering. ## Key takeaways - MiniMax-M2.7-highspeed costs $0.60 per Mtok input and $2.40 per Mtok output, double base MiniMax-M2.7. - MiniMax-M2.7-highspeed is the newest MiniMax checkpoint with priority serving, at the same price as the older M2.5-highspeed. - The 204,800 token context and 131,072 output cap carry over from base M2.7, so throughput is the only change. - At $2.40 per Mtok output, MiniMax-M2.7-highspeed undercuts Kimi K2 Turbo at $10.00 and Kimi K2.7 Code HighSpeed at $8.00. - MiniMax-M3 gives 1,000,000 tokens of context for $0.30 and $1.20, so highspeed trades context and cost for latency. ## What does MiniMax-M2.7-highspeed give Atlas that M2.5-highspeed does not? MiniMax-M2.7-highspeed is the newest MiniMax checkpoint available with priority serving, offered at the same $0.60 per Mtok input and $2.40 per Mtok output that the older MiniMax-M2.5-highspeed costs. Same price, newer weights, which makes MiniMax-M2.7-highspeed the default choice in MiniMax's speed tier. When two tiers share a price, the newer checkpoint wins by default. MiniMax-M2.7-highspeed carries the 204,800 token context and 131,072 output cap preserved from base MiniMax-M2.7, so throughput is the only variable that changes between the standard and highspeed lanes. That preservation matters for Atlas: the build agent still has a full 131,072 token budget to write a complete implementation, and Atlas computes a unified diff for every file edit and surfaces it for approval before writing, so the diff you review is whole rather than truncated by a speed tier that quietly clipped the output ceiling. ## Is MiniMax-M2.7-highspeed expensive for interactive coding? MiniMax-M2.7-highspeed keeps reasoning enabled, and its $2.40 per Mtok output still undercuts Kimi K2 Turbo at $10.00 and Kimi K2.7 Code HighSpeed at $8.00 by a wide margin for interactive work. Against the other fast tiers on the market, MiniMax-M2.7-highspeed is the inexpensive option. The comparison is worth internalizing before you dismiss the highspeed lane as a luxury. Speed tiers from other vendors ask $8.00 or $10.00 per Mtok output. MiniMax-M2.7-highspeed asks $2.40. If your reason for avoiding priority serving was that fast tiers are prohibitive, MiniMax-M2.7-highspeed is the counterexample. Atlas fans out work to subagents that can run in the foreground or in parallel background sessions, and even with that fan-out, a $2.40 per Mtok output rate on a reasoning model keeps an interactive session in normal-budget territory. ## When is MiniMax-M2.7-highspeed a waste of money? MiniMax-M2.7-highspeed costs twice base MiniMax-M2.7 for identical output quality, so it is only correct when a human is actually waiting on the tokens. A scheduled job, a CI agent, or an overnight refactor should run on the $0.30 per Mtok input and $1.20 per Mtok output tier. Configure atlas.json to reflect where attention actually is. Set `"model": "minimax/MiniMax-M2.7-highspeed"` for the interactive main loop and `"small_model": "minimax/MiniMax-M2.7"` so background work bills at half rate. Titles, summaries, and Atlas's parallel background subagents are all cases where nobody is watching a token stream arrive, and routing them through the standard tier halves their cost without changing a single output. Atlas lets you switch the active model and provider on the fly with favorites and recents, so before stepping away from a long run, cycle the main model down to base MiniMax-M2.7. ## What do you give up by choosing MiniMax-M2.7-highspeed over MiniMax-M3? MiniMax-M3 gives Atlas 1,000,000 tokens of context for $0.30 per Mtok input and $1.20 per Mtok output, so choosing MiniMax-M2.7-highspeed at $0.60 and $2.40 means explicitly trading context and cost for latency. MiniMax-M2.7-highspeed's window stops at 204,800 tokens. The tradeoff is coherent once you name it. A 1,000,000 token prompt is slow to fill no matter what it costs, so MiniMax-M3 and MiniMax-M2.7-highspeed are optimizing for opposite things: breadth versus responsiveness. If the task is a wide survey of an unfamiliar repository, MiniMax-M3 is right and latency is not the point. If the task is a tight edit loop where Atlas searches code with hybrid semantic and keyword retrieval fused by reciprocal rank fusion and you iterate a dozen times in an hour, MiniMax-M2.7-highspeed is right and 204,800 tokens is plenty. ## How do you confirm Atlas resolved MiniMax-M2.7-highspeed correctly? Run `atlas providers` to confirm MiniMax resolved through `@ai-sdk/anthropic` before you start a long session on MiniMax-M2.7-highspeed. MiniMax exposes an Anthropic-shaped API, so a provider that failed to load is the most common cause of a model id that will not resolve. The verification sequence is short. Export MINIMAX_API_KEY or run `atlas login` and select MiniMax, run `atlas models minimax` and select `MiniMax-M2.7-highspeed`, then check `atlas providers`. Doing this before a long session matters more on a paid speed tier than on a cheap one, because a misconfiguration that silently falls back to a different model means you are paying $0.60 per Mtok input and $2.40 per Mtok output for something you did not choose. Once resolved, Atlas's permission gating on allow, ask, and deny rules governs every tool call the model issues. ## Setup 1. Export MINIMAX_API_KEY, or run `atlas login` and select MiniMax. 2. Run `atlas models minimax` and select `MiniMax-M2.7-highspeed`. 3. Set `"model": "minimax/MiniMax-M2.7-highspeed"` in atlas.json, and `"small_model": "minimax/MiniMax-M2.7"` so background work bills at half rate. 4. Check `atlas providers` to confirm MiniMax resolved through `@ai-sdk/anthropic` before you start a long session. 5. Cycle the main model down to base MiniMax-M2.7 before any unattended or overnight run. ## FAQ ### how much does minimax-m2.7-highspeed cost MiniMax-M2.7-highspeed costs $0.60 per Mtok input and $2.40 per Mtok output, exactly double base MiniMax-M2.7's $0.30 and $1.20. ### minimax-m2.7-highspeed vs minimax-m2.5-highspeed Both cost $0.60 per Mtok input and $2.40 per Mtok output, but MiniMax-M2.7-highspeed is the newer checkpoint, which makes it the default choice in MiniMax's speed tier. ### does minimax-m2.7-highspeed have a smaller context window No. MiniMax-M2.7-highspeed preserves the 204,800 token context and 131,072 output cap from base MiniMax-M2.7. Throughput is the only variable that changes. ### is minimax-m2.7-highspeed cheaper than kimi speed tiers Yes. MiniMax-M2.7-highspeed's $2.40 per Mtok output undercuts Kimi K2 Turbo at $10.00 and Kimi K2.7 Code HighSpeed at $8.00 by a wide margin for interactive work. ### how do i set up minimax-m2.7-highspeed in atlas Export MINIMAX_API_KEY or run `atlas login`, run `atlas models minimax` and select `MiniMax-M2.7-highspeed`, set `"model": "minimax/MiniMax-M2.7-highspeed"` in atlas.json, then check `atlas providers` to confirm MiniMax resolved through `@ai-sdk/anthropic`. ### should background agents use minimax-m2.7-highspeed No. Set `"small_model": "minimax/MiniMax-M2.7"` so background work bills at half rate. Priority serving only helps when a human is waiting on the tokens. --- Canonical HTML: https://runatlas.sh/resources/models/minimax-m2-7-highspeed Source of truth: aeo_pages row `/resources/models/minimax-m2-7-highspeed` (segment: Models) (this file is generated from it, never hand-edited). Licence: Atlas is proprietary with a free core. It is not open source and there is no public source repository.