MiniMax M2.7 Highspeed API
LLMThe MiniMax M2.7 Highspeed API serves the same M2.7 model on MiniMax's latency-tuned route, at twice the standard token rate.
- Input · USD / 1M tokens$0.14 USDOfficial price
$0.7 USD - Output · USD / 1M tokens$0.56 USDOfficial price
$2.8 USD - Savings80%
- Context200K
- View tool pricing and billing rules
What are we making today?
Bring an idea, a question, or a first draft.
01
What this model is for
The MiniMax M2.7 Highspeed API serves the same M2.7 model on MiniMax's latency-tuned route, at twice the standard token rate.
MiniMax M2.7 Highspeed is the second 200K text id from MiniMax, catalogued as MiniMax-M2.7-highspeed with tool use and a fast marker. It serves the same M2.7 model as the standard entry, and the catalog marks it as a fast tier. Its listed input and output rates sit above those of MiniMax M2.7, while cached input is listed at the standard rate.
This is the id for loops where somebody is watching the answer arrive: a developer waiting on an inline edit, an operator reading a live hypothesis, a chat copilot inside a support console. It keeps the 200K window of the standard model rather than the 1M window of M3 and M3.1 Flash, so it fits prompts that are already narrow. Keep such sessions short, cache the shared system prompt, and move anything batch-shaped to a cheaper id.
Best-fit coding workloads
Inline edits while coding
Ask for small changes to the file a developer is looking at, with the surrounding interfaces in context, and let a tool call apply the patch. Tip: resend only the edited region between turns so the prompt stays small on a 200K budget.
Live debugging calls
Work through a failing request one hypothesis at a time while an engineer reads each answer and decides the next probe. Tip: ask for one experiment per turn instead of a full plan, so the person can stop as soon as the cause appears.
Support console copilot
Draft a reply from a customer record that sits in the system prompt, turn after turn, inside an agent console a person is using. Tip: keep the record and instructions first and unchanged, then append the conversation, so the repeated prefix qualifies as cached input.
02
Hands-on notes
Checked on 2026-10-27 through the OmniaKey API with one standard coding prompt (median of 3 runs) and three capability probes.
- Output tokens for our standard coding prompt, reasoning included
- 1,440
- Cost of that output at current prices
- $0.0008
- JSON mode
- Passed
- Tool calling
- Passed
- Image input
- Not listed
03
Technical specification
Catalog facts and integration details verified for this route.
- Model ID
- MiniMax-M2.7-highspeed
- Context
- 200K
- Inputs and tools
- Tool use · Fast responses
- API endpoint
- /v1/chat/completions
- Cache hit / 1M
- $0.014 USD
- Coding clients
- Claude Code · Codex · Cursor · Cline · Aider
Limits to plan around
- Input and output are listed above MiniMax M2.7 for the same model, so batch jobs and overnight backfills belong on the standard id or on M3.1 Flash.
- The window stays at 200K while MiniMax M3 and M3.1 Flash list 1M, so repository-wide prompts still need chunking here.
- The catalog lists tool use without a vision entry, so an image has to be converted to text before it can be part of a turn.
- The fast marker is a catalog capability, not a measurement of your own traffic. Size timeouts and retry budgets from your runs, and do not assume a streaming turn will finish within a fixed wall-clock limit.
04
Compare nearby models
Compare workload fit and current listed token rates before choosing a route.
| Model | Best for | Context | Input | Output |
|---|---|---|---|---|
| MiniMax M2.7 HighspeedThis page MiniMax-M2.7-highspeed | Interactive 200K sessions where a person waits on each turn and the catalog's fast tier matters. | 200K | $0.14 USD Official price $0.7 USD | $0.56 USD Official price $2.8 USD |
| MiniMax M2.7 MiniMax-M2.7 | The same M2.7 behaviour for background jobs, in the lower listed input and output tier. | 200K | $0.07 USD Official price $0.35 USD | $0.28 USD Official price $1.4 USD |
| MiniMax M3 minimax-m3 | Long material that needs a 1M window with tool calls, on the standard listed tier. | 1M | $0.07 USD Official price $0.35 USD | $0.28 USD Official price $1.4 USD |
| MiniMax M3.1 Flash minimax-m3.1-flash | Volume work that needs both 1M context and a fast marker at a lower listed rate. | 1M | $0.0333 USD Official price $0.1665 USD | $0.1333 USD Official price $0.6665 USD |
05
SDK quickstarts
Use one base URL and model ID from cURL, Python, or TypeScript.
curl https://api.omniakey.com/v1/chat/completions \
-H "Authorization: Bearer $OMNIAKEY_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "MiniMax-M2.7-highspeed",
"messages": [
{"role": "user", "content": "Review this pull request"}
],
"stream": true
}'06
Estimate token cost
Enter expected input and output tokens to compare current listed rates.
- OmniaKey estimate
- $0.0252
- Official-rate estimate
- $0.126
- Estimated savings
- $0.1008
Estimate covers input and output tokens only. Cache usage, retries, tools, and client-side token accounting can change the final charge.
07
Related coding guides
Deeper selection, setup, and troubleshooting guidance for this model family.
08
Sources and verification
Model facts and links were checked on 2026-10-27. Provider documentation remains the authority for upstream behavior.
Frequently asked questions
How much does MiniMax M2.7 Highspeed cost on OmniaKey?
OmniaKey currently charges $0.14 USD per 1M input tokens and $0.56 USD per 1M output tokens, in USD. Direct provider rates are separate and may change with input context length.
What is the context window for MiniMax M2.7 Highspeed?
The listed context window is 200K. Actual usable limits can also depend on the client and upstream request format.
What is the difference between M2.7 and M2.7 Highspeed?
Both serve the M2.7 model with a 200K window and tool use, and both list the same five clients. Highspeed adds the catalog's fast marker and lists higher input and output rates, while cached input keeps the standard rate. Use Highspeed when a person is waiting, and the standard id for anything that runs unattended.
How is MiniMax M2.7 Highspeed billed?
Charges cover input tokens and output tokens, with cached input billed at its own rate, and they draw on the account balance. The current rates are in the price table on the model page. Because the prefix you reuse can be cached, a stable system prompt is the cheapest thing in a long interactive session.
Does MiniMax M2.7 Highspeed take a 1M prompt?
No. The catalog lists 200K for this id, the same as MiniMax M2.7, while MiniMax M3 and M3.1 Flash list 1M. Split large repositories or long document sets, or use one of the 1M ids. Leave space for the answer inside the 200K limit rather than filling it exactly.
Which clients can call the MiniMax-M2.7-highspeed id?
Claude Code, Codex, Cursor, Cline and Aider are all listed. Any OpenAI-compatible client also works against https://api.omniakey.com/v1/chat/completions with the key as a bearer token. Copy the id from the model page, since the capitals and the hyphen before highspeed are part of it.
Can it see screenshots during a debugging session?
Vision is not listed for this id, so an image cannot be read directly. Paste the error text and the relevant log lines, or convert a screenshot with optical character recognition first. When the picture itself carries the information, pair this model with a vision model that reads the image and passes on a description.