MiniMax M3.1 Flash

5 hours ago (minimax.io)

This model seems to be pretty benchmaxed. In actual use, it doesn't survive the comparison to models in the benchmark.

This model was released as a "stealth model" in OpenCode Go for a while as "Space Bunny" (they mention this in the blog). So people have been using without knowing what the model was exactly, but it failed to impress anyone as far as I can tell. This is despite the model being served for free (with some asterisks). GLM 5.3 Flash and DeepSeek V4.1 Flash, even before last week's update, seemed to be much preferred. Stealth releases happen often with OpenCode subscriptions, and GLM 5.3 Flash (stealth name "Ox Alpha") impressed a lot for example.

The perverse incentives around benchmarks are now so bad that benchmark scores are effectively meaningless. Models can score highly and still be crap to use. It doesn't matter whether it's Minimax or Google, or anyone really.

  • I used Space Bunny from some providers that offered it for free and it was a very much a "you get what you pay for" experience. If the release is comparable, I'll be sticking with Deepseek v4 for sure.

    • I’m one of the unimpressed. I tested SpaceBunny intensely on a research project for a week.

      The model wasn’t horrible at coding, it just made a ton of initial mistakes—but then would catch most of them later on. It can get work done if coaxed, but its peers are just cheaper and/or easier to work with.

      1 reply →

  • > The perverse incentives around benchmarks

    I am not sure. The people who actually care enough to look at benchmarks will run evals, and find out quickly. If you post silly benchmark scores too often, you will simply be ignored. You are paying with your reputation.

    • All the benchmarks are silly but people still want a quick way to put a new release in context

  • This is my experience with all MiniMax models: They're good on paper but fail to live up to expectations in practice. IMO, at no point has any MiniMax model been the superior choice over others, all things considered.

The cost vs performance is insane for all these new models. I’ve been using Deepseek Flash 1017 and it does whole projects and asks for $0.10 on US provider with ZDR on Openrouter. I convinced a few friends to drop their Claude $20 subscription because DS Flash 1017 brings so much better value. They can still use Opus 5.5 for planning though each call will cost north of $2. Excited to try this model out too once there are US providers.

  • Opus 5.5 is according to AA cost per task, 23x more expensive than Deepseek with max effort (which is dumb, you shouldn't use) and 13x more expensive on xhigh.

    Claude sub has a 60x subsidy, so a $20 sub gives you $1200 in API.

    Based on this math, Claude sub is a much better deal than Deepseek. And it's a stronger model of course.

    • > Claude sub has a 60x subsidy, so a $20 sub gives you $1200 in API.

      This is only true if you max out the plan, which requires working around awkward 5-hour and weekly limits. For side projects, sure, you can use a Ralph loop or whatever and just continue when the window resets. For work, I can't afford to simply stop working when I hit my limit. And using Claude at API prices is prohibitively expensive.

      Personally, I have a $20/month OpenAI subscription that I supplement with DeepSeek V4.1 Flash (currently using CoralBricks as the provider since it's fast and I'm grandfathered into their $0 cache read pricing). It's working out rather well so far. Even when I use DS all day as my primary model, I only pay about $1/day, which is roughly equivalent to what I pay for the sub anyway (but with no limits).

      2 replies →

    • I pay API rates via OpenRouter / Fireworks, and I find it challenging to hit the $20 mark.

      If I was to do anywhere near that kind of work on Anthropic, I'd find myself running out of tokens, waiting days to continue working, and leaning on their el-crap models to try to avoid running out again. This happens all the time.

      This way I get to leverage DS for nearly all my work, benefit from its far superior latencies, and I still get to lean on OpenAPI / Anthropic or whatever SOTA models I want when I need them.

      The only time that really falls down is if I'm doing huge amounts of real novel work, which hasn't been the case for a while.

      1 reply →

    • I don't like the feeling of being watched, which unfortunately rules out the AI subscriptions for me.

      For some reason it just creeps me out knowing that someone is recording me and reading my conversations.

      2 replies →

    • Just because anthropic charges absurd consumer API prices, doesn't mean their subscription is a 'subsidy' lmao.

      I'm a heavy Claude/anthropic user, I max out my 20x max plan in 1-2 days at this point. The OpenCode Go $40 plan with DeepSeek flash is like 2x the value of the Claude max 20x plan for how much I actually get out of it, for 1/5 the price.

      DeepSeek literally like 10x better value than Claude/Anthropic.

      4 replies →

  • I suspect that we may soon be seeing a modern version of VHS vs Betamax. Betamax was better quality, but VHS beat it in virtually every other metric that mattered to most consumers.

    (yes, I'm aware the analogy isn't perfect for many reasons)

I go off of marketing obviously, but how is every new announcement of any vendor always on top of all others and then cheaper, while next day the next best and even cheaper model pops up? Is there anyone who independently verifies this? Its kind of pointless to comment on this announcement, much like how its pointless to comment on all the other announcements...

  • There are hundreds of benchmarks (all noisy), dozens of model families, and dozens of modes and variants within each. Announcements are crafted by publicity teams and involve cherry picking a chart that looks compelling.

    As a prospective user, none of of the benchmarks details will matter to you, but the family of models and settings they peg themselves against can give you a hint of where you might want to evaluate them within your own workflows.

    As an enthusiast or lay researcher, the more interesting thing is to look at their techniques and any innovations they're exploring in training, inference, etc. Those are usually going to be details tucked below the fold and won't be summarized in a benchmark chart.

    As anybody else, why do you even care about this in the first place?

    This doesn't just apply to AI. You should know better than to take marketing announcements at face value, nor trust that most "influencers" or "journalists" or "commenter" repeating and discussing those announcements are doing a lot of work as they buzz over what's said.

    Don't be a victim to PR spin, but also don't discount potentially interesting work just because it got channeled through a marketing team. Just look for the information you need amidst the noise or move on if there's none there.

    • > Announcements are crafted by publicity teams and involve cherry picking a chart that looks compelling.

      *crafted by LLMs with a list of PR guidelines in a markdown file

  • Because they selectively choose which benchmarks to highlight and which competing models to compare against; they don't always compare against the SOTA or the Pareto frontier of performance/price, a lot of times you'll see them compare against the last generation of competing models, or the like, so that they look better if you don't carefully consider what they're comparing against.

    For example, here you see they are comparing against Opus 5 and GPT-5.6 Sol, when Opus 5.5, Sonnet 5.5, GPT-6 Astra, and GPT-6.1 Sol would be the latest SOTA models from those labs to compare against.

    Also because a lab's own benchmarks tend to run about 6.4% better than third party runs of the same benchmark. Source: https://whatmodel.sh/claims This can happen due to a number of factors, and doesn't necessarily indicate anything nefarious. It could just be that they run multiple times while fixing issues that aren't related to the model, and have a selection bias towards stopping when the score is on the higher side. But since you see that sometimes their own scores are lower than the independent runs, some of the variation is explained just by variance in the model solving problems, since LLMs are nondeterministic there can be variation from run to run and you don't see labs always cheating, just potentially a bit of selection bias about when they stop tweaking their benchmark setup and publish the results.

    And yes, there are independent third party runs of benchmarks for just this reason. The most popular with broad coverage of a range of benchmarks is https://artificialanalysis.ai/ but there are a number of others as well.

    • > LLMs are nondeterministic

      Being pedantic - LLMs are deterministic software, that is chaotic and typically deployed with a PRNG seed. An LLM ran using the same seed will produce the same output consistently (theoretically - in practice this isn’t always the case because of changing factors wrt the execution environment given how sensitive/chaotic models are).

      2 replies →

  • You have to read between the lines (or wait for someone on HN to do it for you).

    It's never "cheaper and faster and more intelligent", it's pick 2. Sometimes (as was the case this month), it was "cheaper per token, but reasons five times as much", so your costs go up.

    • the nice thing about local models is you can limit reasoning and keep things even all the time.

  • I run a benchmark and independently check all new models. They are very spiky.

    If you are doing coding only then official benchmarks are mostly right, but as many people are starting to do for instance marketing work with LLMs now there’s very little correlation between coding and creativity for instance.

  • This seems worse across the board compared to latest DeepSeek Flash, except on some automation bench.

    So, I can quickly judge that this is an interesting option only if cheaper or faster than DeepSeek.

    Based on Terminal Bench 4.0, I'd also guesstimate behind GPT 5.6 Sol, so of course behind the SOTA as expected.

  • I have this idea that the big labs internally have much more capable models which are prohibitively expensive to run though, and the competition is mainly around getting the price down by releasing models that are quantized/otherwise made more efficient at the cost of a lot of performance.

  • I've got a corollary question, which is "how big is the market for these never ending model announcements?" ... I guess its mostly people coding with agents. Most general AI users are just asking ChatGpt to word an email for them or whatever. How many AI users are on here looking for the next model announcement and working out if the price per token is better? Are we talking like 50,000 developers? More? Less?

    • Openrouter does >600 trillion tokens a month and the top models shift on a daily basis. A lot of people are paying attention to new releases and even pre-releases (which tend to be free)

  • It's always cheaper (*than the next more expensive model) and better (*than the next worse model).

    And often they also don't mention how verbose it is, that the same text splits into more tokens than in competing models, how slow it is, that the pricing is temporary, that the cost per task actually isn't that good despite being both cheap and capable.

    • Can't you control verbosity? Of course defaults are going to be optimized for revenue. Isn't Deepseek second in cost_per_task:intelligence?

      Edit: You removed model names ig

> For agentic tasks, the model’s overall usage cost is 70% lower than its predecessor.

For this release, the cost is $0.15 input MToK/$0.60 output MTok/$0.015 cache read MTok, In this case the predecessor is MiniMax M3 (not Flash), which was $0.30 input MToK/$1.20 output MTok/$0.06 cache read MTok. So a 50% cut to input costs and a 50% proportional cut to cache read costs (20% of input -> 10% of input) makes the ~70% cost reduction plausible.

A 70% cost reduction is very funny in light of reports saying LLMs are becoming too expensive. That is likely due to the need to compete with DeepSeek V4.1 ($0.15 input MToK/$0.60 output MTok/$0.003 cache read MTok), which this new model still does not beat because DeepSeek's cache costs are still confusingly low, but it's pretty close.

  • If anything I am confused by how high cache costs still are across many models

    The really expensive part of inference - the compute and memory traffic required to perform prompt processing and decode - is paid for roughly once per token in a multi-turn session when prompt caching is working properly.

    The difference to the provider's costs between:

    - Submitting 100 back-to-back requests, each adding 1k tokens to the context

    - Submitting 1 100k token context request

    Is negligible. Yet the consumer is going to pay a lot more in the former case for all those repeatedly submitted input tokens that you get charged the cached rate for (but which required no additional compute on the provider side).

    DeepSeek V4.1 has an insanely optimized KV-cache that takes around 900MB per million tokens, making it feasible to move to disk between requests. Makes sense they're cheap

    • The amazing part of DeepSeek's caching is that the TTL is (although not guaranteed) like 8-24 hours. Makes a big difference to how much time I can spend reviewing code, when most everyone else offers maybe 1 hour (for subscribers - often minutes for API users).

  • Not sure why ds cache costs are confusing? Their kv cache is absurdly compressed compared to almost everyone else.

    • It is confusing because they are the only ones doing so whereas everyone has an incentive to apply similar techniques.

  • That still isn't the whole story. Compare DS 4.1 Flash [1] to GLM 5.3 Flash [2], and consider the effective price. DS's price is lower than GLM on input tokens, but higher than GLM on output tokens. Output price is an order of magnitude higher than input price. So for output-heavy workloads and long reasoning, DS costs more than GLM.[1] https://openrouter.ai/deepseek/deepseek-v4.1-flash#pricing [2] https://openrouter.ai/z-ai/glm-5.3-flash#pricing

    Yes the official DS provider has a low cache cost, for now (it's just distributed KV). But people are still concerned about ZDR, sovereign AI, getting more model choice in their subscription price, etc. They want more bang for their buck. So when a new model comes out, the bigger impact is really its performance across providers, not the price at a single provider.

    And in about 5 years (or less), API prices will stop being a thing. We all used to pay per-minute for phone calls, texts, data. Nobody does anymore. Virtually every mobile provider is now a flat prepaid or contract fee. Carriers improved their technology (going from analog to digital), and it turned out consumers will spend more money on a packaged subscription than on pay-per-use. That's why everything in the world is a subscription now.

    Your modern $70 big wireless plan isn't giving you $70 of value. Similarly, your $20 AI subscription that's a great deal right now, will be less valuable in 5 years, when hardware & models are more efficient. You'll still be able to buy a local AI rig, but it will still be very expensive, due to AI models continuing to be large, and NVidia keeping new hardware expensive, as these things together reinforce their dominance and profits, and our reliance on them.

    This also follows another pre-existing trend. Why do people keep having to buy a new iPhone or laptop every other year? Because each year companies make software & data less efficient/more bloated, so people need a more powerful machine to run it, which enables them to make even more bloated software. Almost everything people do with a computer today is what they did 15-20 years ago; it's just a higher bit-rate. Despite this, people keep re-buying the same machine, so companies can keep extracting more wealth.

    AI works the same way. Rather than cost to consumers going down over time, it will likely go up. Not because it can't get cheaper/more efficient - but because it increases companies' profit. This isn't just a theory, btw; the US economy's growth is now almost entirely reliant on this happening.

    • > Rather than cost to consumers going down over time, it will likely go up. Not because it can't get cheaper/more efficient - but because it increases companies' profit.

      As shown in the OpenRouter links you provided, there are over 30 distinct providers of these open-weights models, the majority of them supporting ZDR. They can't raise prices because it's a near-perfect marketplace and if they do, someone will just lower them to compete as long as marginal revenue >= marginal cost. There's no moat or other economic factors (e.g. collusion; hard to do with 30 actors) to allow for price control.

The weights have yet to be released. The previous MiniMax M3 had (I think) ~428B parameters. Since this one is called Flash and they advertise it as inference being 3 times faster, there's the possibility that this will be a ~150B size model which would (quantized) run on DGX Spark or 128GB Macs or the new AMD AI systems.

  • The FAQ on their website says Minimax 3.1 flash is 428B total, 23B active

    Which is roughly similar to deepseek 4.1 flash.

    I find it interesting that we’re calling these “flash” models now, even though they aren’t “small or light” and in many cases aren’t particularly that fast.

    I suppose it’s more so that the standard for “regular models” is becoming 1T+

    https://agent.minimax.io/tools/m3-1-flash-preview

    • Flash probably means single expert fits into some cost efficient GPU memory, and non flash models require more complex and cost expensive architectures.

  • I think flash usually means MoE, not dense

    • Every frontier model is MoE these days! Flash or otherwise. Sparsity just gets you more bang for your buck.

    • Not really. “Flash” generally means fast or cost-efficient, not specifically MoE (Mixture of Experts).

      - DeepSeek V4 Flash: 284B / 13B active MoE

      - DeepSeek V4 Pro: 1.6T / 49B active MoE

      - DeepSeek V4.1 Flash: 552B / 8B input, 16B output MoE

Minimax has been a strong player in our tests, if they managed to solve the inference speed issue(be scared, be very scared). A decent speed is at least 13 tps in consumer hardware. Let see if it passes Hugston bench this time, we really hope so.

  • 13 TPS is painfully slow?

    20 t/s is about the speed you can read at, so slower than that and it always feels like it's buffering. 35 t/s is where it starts feeling decent and 50 t/s feels nice.

    • I know, it is never enough, more, more, give me more. But the fact is that no one has broken though yet to offer a frontier like open weight over 13 tps in consumer hardware. It would be usable at 13tps for me, especially considering the benefits and advantages of privacy, infinite tokens, availability and no refusals/restrictions. To this day Minimax and GLM are very strong coders but have the same issue, inference speed. We need a real break through, one that thinks out of the box (Tesla turbines style perhaps).

    • If all you're going to do is chat with an AI, you don't need a 400B parameter MoE model.

      13 TPS is unusable for agentic coding, because if decode is that slow, then prefill is absolutely abysmal, and agentic work live and die by prefill speeds.

      6 replies →

    • It feels even slower when you consider thinking traces and tool calls which are skimmable at best.

Odd choice to have a mix of opus 5 and 5.5 in different graphics.

  • I went to check and Opus 5.5 wasn't benchmarked on DeepSWE1.1, I can't keep track of which are in vogue at the moment but maybe it's thought to be saturated at this point, as they only have older GPT models as well

  • The recent DeepSeek release used Opus 5 as a reference point as well. I don't understand it. It's not like they're referencing superseded releases of other open models.

    • I think it clearly points to where they expect themselves to be, Opus 5.5 and Astra or Sol 6.1 are models that shouldn't exist at those prices without the price competition.

      And no new releases from Chinese labs likely means their models that they could compare against those models are still baking largely because they lack compute so severely they need to train models for far longer, or figure out training on Chinese hardware.

      Either way it's clear open models a lagging by ~1-2 months compare to frontier, depending on what frontier means to a person. Honestly most new models are just not that much better than at edge cases, they still fail a lot for the kind of stuff I do, but those edge cases matter a lot for un-interrupted long horizon work.

      I personally am starting to see a wall here in llm development but that might just be me, given that people are being forced to scale models up considerably for frontier performance.

      It's scary thinking that modern models will likely be at best 2-3% better in benchmarks or only useful in 1-2 unique edge cases compared to base models for 100x cost increase in compute required, it's getting absurd.

      I can't imagine how Fable models can retain any value once you have to go 100x larger, while 27-32B models start to catch up to the current frontier for coding or other narrow/focused tasks in a year or so.

      5 replies →

I used it as Space Bunny, was very good at documentation, structuring and organizing the things, but was not as concise and direct as DeepSeek 4.1 Flash in coding, we could not focus on code part as a human and AI team from how many approves are needed for each step discussion.

Is there a single use case where you would not be better served using MiMo 2.6 Pro?

https://artificialanalysis.ai/models/comparisons/mimo-v2-6-p...

  • On Openrouter at least, all Mino models are painfully slow. TTFT is many seconds and the models spend a lot of time on its CoT, making effective output per second many times slower than DS Flash. On Flash 4.1, I constantly get ~180 tok/s and the real work got done fast, too. So even when the Mimo 2.6 are smart models, I use them much less recently. Not to mention their costs are also higher than DS.

    For me, the DeepSeek 4.1 models are currently the ultimate cost-effective model the rest have to match with, especially if you are not on a subscription plan with heavy discount.

    GPT Sol 6.1 is however, for me the most efficient model, both in terms of time to finish and token usage.

Another day where the Pareto frontier is moved up and to the left!

I haven't tried this model yet but Deepseek and the GLM 5.3 series do feel like "enough" for a lot of tasks, it's pretty amazing to see that we're still getting better and cheaper models all the time.

I only wished they would focus more on wall clock time. For a hobby project I do not mind that a cheaper model takes twice as long but at work it's hard to justify using a "cheaper" model if the time per task is so much higher than the frontier models.

The amount of time that it took to complete a benchmark is almost never shown in these kind of releases.

  • Would place DS 4.1 1017 roughly equivalent to GLM 5.3 which means it's targeted to price rather than direct capability. Probably why they listed DS adjacent in the comparison table when according to their results more expensive models are beaten by it.

  • You do realize that there exist multiple Pareto frontiers, at least for every arbitrary combination of parameters for a given benchmark?

    Obviously your marketing team is going to use the Pareto frontier where your model has improved the most and compares favorably against competitors.

Curious if anyone has put it up against DeepSeek Flash yet, see if the price/performance benchmarks hold up?

  • Some reddit comments say it's not as good as DS 4.1 Flash. But I didn't test myself and I don't trust benchmarks.

The deepswe and terminalbench4.0 scores don't seem to jive with what many opencode users' experience has been of this model while it was being tested as "space bunny". I saw a lot of anecdotes of people trying it and going back to qwen 3.8-flash-next or deepseek v4 flash because "space bunny" made some rather egregious errors.

  • > [Space Bunny] was an early version of MiniMax M3.1 Flash.

    They mention that space bunny was an earlier checkpoints, so it may have improved (or may it could be benchmaxxed)

    I find it interesting that so many models seem to be at almost exactly 74% specifically which makes me suspicious of the benchmark. I want to say 5.6-sol, Astra, deepseek flash 4.1, opus 5 (and 5.5?), Gemini 3.8-flash and a few others all ended up there?

    • > so many models seem to be at almost exactly 74%

      There was talk of deepswe tests being flawed. I have yet to find a better gauge of useful work for my case though, so I still keep referencing it and sampling it. On the lookout for improved benchmarks.

      "We found issues in at least 23 out of 113 tasks (over 20.3%), leading us to designate the benchmark as Flawed." - https://epoch.ai/benchmarks/deepswe/review

      1 reply →

MiniMax models have been pretty disappointing. M2.5 was good, M2.7 was meh and came with a terrible license, 3 meh. Maybe this will be better, but I have my doubts. When I say good vs meh vs bad, this is all relative of course. If M3.1 came out a few months ago it would be groundbreaking. Things just move too quick.

H3, on the other hand, is phenomenal

The comparisons with models like GPT-5.6 or Opus are pointless because they vary substantially. They are often nerfed shortly after release and then performance is not consistent. One day model will be doing relatively fine, another it will be dumb as markov generator. In that regard self hosted models are better, because you know what is running your requests.

Not as strong as DeepSeek V4.1 Flash 1017 on deepswe so it's already dead to me.

Unless they come in at half the price (which I think will be impossible) on inference ... they have wasted their training compute imho.

Dupe, dupe, dupe, dupe, and dupe:

https://news.ycombinator.com/item?id=50153725