Requesty
MiniMax logo

minimax-m2.7-highspeed

MiniMax/Open weights/2 providers

MiniMax-M2.7 is a next-generation large language model designed for autonomous, real-world productivity and continuous improvement. Built to actively participate in its own evolution, M2.7 integrates advanced agentic capabilities through multi-agent collaboration, enabling it to plan, execute, and refine complex tasks across dynamic environments. Trained for production-grade performance, M2.7 handles workflows such as live debugging, root cause analysis, financial modeling, and full document generation across Word, Excel, and PowerPoint. It delivers strong results on benchmarks including 56.2% on SWE-Pro and 57.0% on Terminal Bench 2, while achieving a 1495 ELO on GDPval-AA, setting a new standard for multi-agent systems operating in real-world digital workflows.More

Which id to call

minimax-m2.7-highspeed

Requesty routes this id across every provider serving minimax-m2.7-highspeed, picking on price and health and failing over automatically. The id stays valid when a provider changes underneath it.

From /1M input

$0.60

MiniMax

Context

205K

128K output

Endpoints

2

1 region

Regions

1

chat

Capabilities 4/8

VisionReasoningTool callingCachingWeb searchJSON schemaComputer useImage generation

2 endpoints / 1 region

Providers serving minimax-m2.7-highspeed

Provider prices, per 1M tokens. Pay as you go adds 5%, or 0% on your own keys.

Providers serving minimax-m2.7-highspeed, with pricing and measured performance. The best value in each column is highlighted.
RankPrivacy
1MiniMaxGlobal200K$0.60$2.40$0.06zdr
2Novita AIGlobal205K$0.60$2.40-zdr

A column is blank where no qualifying sample exists, and every row links to that provider's endpoint page.

model=

Which id to call

One base url, https://router.requesty.ai/v1, and one key for every id here.

minimax-m2.7-highspeed

Requesty routes this id across every provider serving minimax-m2.7-highspeed, picking on price and health and failing over automatically. The id stays valid when a provider changes underneath it.

OpenAI compatible

Call it in three lines

Change the base url, use your Requesty key, set the model to any id on the left. Existing OpenAI SDK code needs no other edit.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
from openai import OpenAI client = OpenAI( api_key="YOUR_REQUESTY_API_KEY", base_url="https://router.requesty.ai/v1", ) response = client.chat.completions.create( model="minimax-m2.7-highspeed", messages=[ {"role": "user", "content": "Explain quantum computing in one paragraph."}, ], ) print(response.choices[0].message.content)

5

More from MiniMax

Reference

minimax-m2.7-highspeed questions

Which providers serve minimax-m2.7-highspeed?

minimax-m2.7-highspeed is available from 2 providers through Requesty: MiniMax, Novita AI. All endpoints share one OpenAI-compatible API and one key, and Requesty fails over between them automatically.

How much does minimax-m2.7-highspeed cost?

Pricing starts at $0.60 per million input tokens and $2.40 per million output tokens on MiniMax, the cheapest endpoint. Prices vary by provider and region; the table above shows every endpoint. Those are the upstream provider rates: pay as you go adds 5% on top, or 0% if you bring your own provider keys.

Is minimax-m2.7-highspeed open weights?

Yes. minimax-m2.7-highspeed is an open-weights model from MiniMax, which is why multiple inference providers can host it. Provider choice affects price, latency, and data-privacy terms, all compared above.

What is the context window of minimax-m2.7-highspeed?

minimax-m2.7-highspeed supports up to 205K tokens of context, with up to 128K output tokens per response. Some providers expose a smaller window; check the per-endpoint context column above.

How do I use minimax-m2.7-highspeed with the OpenAI SDK?

Install the OpenAI SDK, set base_url to "https://router.requesty.ai/v1", set your API key to your Requesty key, and set the model to "minimax-m2.7-highspeed" or any endpoint id from the table above. The quickstart section shows Python, JavaScript and cURL snippets.

Should I call minimax-m2.7-highspeed by its managed id or a provider id?

Use the managed id, "minimax-m2.7-highspeed". Requesty picks which of the 2 providers serves each request based on price and health, and fails over when one degrades, so the id keeps working while the routing changes underneath it. Send a provider id like "minimaxi/minimax-m2.7-highspeed" only when you need one specific deployment and want no failover.

Route minimax-m2.7-highspeed through one endpoint

One key for 2 providers on this model and 600+ others. No markup on provider prices, automatic failover, caching built in.

Benchmark rankings