MiniMax M2 APIOPEN WEIGHTS205K context

Pricing & specs mirror our live pricing as of July 2026 (pay-as-you-go).

What is MiniMax M2?

MiniMax-M2 is a compact, high-efficiency large language model optimized for end-to-end coding and agentic workflows. With 10 billion activated parameters (230 billion total), it delivers near-frontier intelligence across general reasoning,...

MiniMax M2 on the release timeline

MiniMax M2 pricing

Pay-as-you-go on DataLLM Lab — these are our live list prices (identical to the pricing page):

On output price, MiniMax M2 is cheaper than 59% of the 309 models in the catalog. It is served by 3 providers; the best combined rate at our last snapshot was ≈ $0.26 / $1.02 per 1M via Minimax, with upstream quantizations fp8.

What MiniMax M2 costs per month

Cost = input price × input volume + output price × output volume. The same five workloads run on every model page, so any two compare directly.

MiniMax M2 vs alternatives

Specs

How to call MiniMax M2

Copyfrom openai import OpenAI
client = OpenAI(base_url="https://api.datallmlab.com/v1", api_key="YOUR_DATALLM_LAB_KEY")
resp = client.chat.completions.create(
    model="minimax/minimax-m2",
    messages=[{"role": "user", "content": "Hello"}],
    # supports tools=[...] and tool_choice
)
print(resp.choices[0].message.content)

Copycurl https://api.datallmlab.com/v1/chat/completions \
  -H "Authorization: Bearer YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"minimax/minimax-m2","messages":[{"role":"user","content":"Hello"}]}'

Copyimport OpenAI from "openai";
const client = new OpenAI({ baseURL: "https://api.datallmlab.com/v1", apiKey: process.env.DATALLM_KEY });
const r = await client.chat.completions.create({
  model: "minimax/minimax-m2",
  messages: [{ role: "user", content: "Hello" }],
});
console.log(r.choices[0].message.content);

The same key routes MiniMax M2 and 300+ other models — switch models by changing one string. How OpenAI-compatible APIs work.

Prompting tips for MiniMax M2

• State the goal, not every step. MiniMax M2 reasons internally — give it the objective, constraints and success criteria and let it plan the approach; over-scripting each step tends to lower quality. Turn effort up for hard problems.
• Huge 205K context — but anchor the ask. You can paste whole documents or codebases; models attend most to the start and end, so put the key instruction at the top and restate it after long inputs.
• Give it real tools. Pass a tools=[...] schema instead of asking it to "pretend" — let MiniMax M2 emit tool calls, execute them, and feed results back for the next turn.
• Constrain JSON with a schema. Use response_format / structured outputs rather than "reply in JSON" to get valid, parseable objects every time.

Tips are derived from MiniMax M2's actual capabilities — context window, tool & JSON support, modality and price tier — not generic advice.

Open-source tools for MiniMax M2

Popular open-source projects for running and building with MiniMax M2 — star counts pulled from GitHub (July 2026).

Listed by GitHub stars; inclusion is by ecosystem relevance (inference engines, agent frameworks and SDKs), not affiliation. Stars change — see each repo for current numbers.

Migrating to MiniMax M2

Coming from OpenAI or another gateway? On an OpenAI-compatible setup the only changes are base_url → https://api.datallmlab.com/v1 and model → minimax/minimax-m2. Messages, streaming, tool calls and the rest of your code stay the same. Routing & failover guide.

Self-host or use the API?

MiniMax M2 ships open weights (MiniMaxAI/MiniMax-M2, ~114.7K downloads and 1.5K likes in the last 30 days), with community quantizations (fp8) for smaller GPUs, so you can run it yourself. Most teams still use the API: no GPU to provision or keep warm, no inference ops, and instant access across 3 providers with automatic failover. Self-host when data residency or fixed per-token economics matter most.

Rate limits & reliability

Rate limits here are the DataLLM Lab gateway's, not the upstream vendor's. On 429 (rate limited) or 503 (provider busy), retry with exponential backoff; because MiniMax M2 is served by 3 providers, requests can fail over to a healthy one automatically. See the error-code guide and failover setup.

Related reading

Frequently asked questions