Requesty
Sign in

identity

open weights
MiniMax logo

minimax-m3.1-flashMiniMax

from /1M in$0.15minimax
context1.0M1.0M out
best ttft1.46sminimax
price spread2.0x2 endpoints
endpoints
2
regions
2
best tok/s
164
api
chat
released
October 2026
eu routing
available

capabilities 5/8

visionreasoningtoolscachingweb searchjson schemacomputer useimage gen

The same weights cost 2.0x more on tensorx than on minimax. That is what the endpoints table is for.

endpoints

2 / 2 regions
Providers serving minimax-m3.1-flash, with pricing and measured performance. Best value in each column is coloured.
#flags
1MiniMaxGlobal1M$0.15$0.60$0.011.46s164.0-zdr
2TensorXEU1.0M$0.30$1.20$0.071.88s161.0zdr
provider price, no markupper 1M tokensblank where no qualifying sample

measured

through Nov 2
median
856ms1.75s2.64s08-3109-2811-021.40s1.26s
hover the plot for weekly values
time to first token per provider: current value, window low and high, and change across the window
providernowlowhighchange
MiniMax1.46s1.24s2.49s-31%
TensorX1.88s1.00s1.48s+24%

median wait before the first token lands. this is the number a user feels, and it moves with provider load through the day.

Lines are steps: each sample is one week of traffic held flat, not a slide from the week before. Click a name in the key to drop it from the plot. Measured through Nov 2.

benchmarks

artificial analysis
Benchmark scores, each normalised to 100
evalScore as a share of 100/100
SciCode53.4
Humanity's Last Exam48.0
Intelligence Index28.9
3 evalsmean43.4

Scores from Artificial Analysis and public leaderboards, normalised to 100. Bar colour is the band, not the rank: green 80 and up, blue 55 and up, amber 30 and up. Benchmarks measure narrow skills, so test on your own workload before committing. Released 2026-10-19.

call it

model=
minimax-m3.1-flash

requesty routes this id across every provider serving minimax-m3.1-flash, picking on price and health and failing over automatically. the id stays valid when a provider changes underneath it

Base url is https://router.requesty.ai/v1 for every id here. One key reaches the whole catalog.

quickstart

openai compatible
main.py
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-m3.1-flash",    messages=[        {"role": "user", "content": "Explain quantum computing in one paragraph."},    ],) print(response.choices[0].message.content)

Change the base url, use your Requesty key, set the model to any id in the call pane. Existing OpenAI SDK code needs no other edit, and the same key reaches every other model in the catalog, so switching later is a one-parameter change. Browse all models

notes

reference

MiniMax M3.1 Flash is a fast multimodal model in the MiniMax M3 family, built for agentic cowork automation, coding and visual tasks. It scores 72.5% on AutomationBench AA (best among open models), 73.67% on DeepSWE, 91.0 on BabyVision with tools, 82.5 on CharXiv RQ, 56% on AA Omniscience and 48% on HLE. Supports image input, tool calling, structured JSON output, reasoning and prompt caching. Ideal for multi step workflows, coding agents, frontend and presentation generation, and professional analysis at low cost.

questions 7

Which providers serve minimax-m3.1-flash?
minimax-m3.1-flash is available from 2 providers through Requesty: MiniMax, TensorX. All endpoints share one OpenAI-compatible API and one key, and Requesty fails over between them automatically.
How much does minimax-m3.1-flash cost?
Pricing starts at $0.15 per million input tokens and $0.60 per million output tokens on the cheapest provider. Prices vary by provider and region; the table above shows every endpoint. Requesty charges exactly what the upstream provider charges, with no markup.
Is minimax-m3.1-flash open weights?
Yes. minimax-m3.1-flash 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-m3.1-flash?
minimax-m3.1-flash supports up to 1.0M tokens of context, with up to 1.0M output tokens per response. Some providers expose a smaller window; check the per-endpoint context column above.
Which provider is fastest for minimax-m3.1-flash?
In recent production traffic through Requesty, MiniMax had the lowest median time to first token (1.46s) for minimax-m3.1-flash. Latency shifts over time, so Requesty's latency-based routing picks the fastest healthy provider per request automatically.
How do I use minimax-m3.1-flash 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-m3.1-flash" or any endpoint id from the table above. The quickstart section shows Python, JavaScript and cURL snippets.
Should I call minimax-m3.1-flash by its managed id or a provider id?
Use the managed id, "minimax-m3.1-flash". 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. There is also an EU-only id, "minimax-m3.1-flash@eu", which routes the same way but only through EU-hosted providers. Send a provider id like "minimaxi/minimax-m3.1-flash" only when you need one specific deployment and want no failover.

more from minimax 6

Other MiniMax models
modelcontextfrom /Mproviders
minimax-m31.0M$0.304
minimax-m2.7-highspeed205K$0.602
minimax-m2.7200K$0.302
minimax-m2.5200K$0.284
minimax-m2.5-highspeed200K$0.601
minimax-m2200K$0.301

route minimax-m3.1-flash through one endpoint

One key for 2 providers on this model and 600+ others. No markup on provider prices, automatic failover, caching built in. Weekly aggregates in the measured pane come from production traffic routed through Requesty, one line per provider on a shared axis. Methodology

minimax-m3.1-flash2 providers2 endpointsfrom $0.15 /1M inctx 1.0Mttft 1.46sspread 2.0xupdated Nov 2