← Back
LLMsNEW

A Cheap Model With a 93% Hallucination Rate: How to Read That Number Before You Switch

MiniMax M3.1 Flash got more questions right than its rivals and still scored a 93% hallucination rate. What the number means, why accuracy does not cancel it out, and how to test a cheap model on your own work before you move to it.

5 min read
Updated Oct 20, 2026
QUICK ANSWER

On Artificial Analysis’s AA-Omniscience test, the hallucination rate is the share of questions a model did not get right where it gave a wrong answer instead of declining. It measures whether a model knows when to say it does not know, which is separate from how often it is right.

What happened

MiniMax released M3.1 Flash, an agentic model with a one-million-token context window at $0.15 per million input tokens and $0.60 per million output. VentureBeat's report puts it at 42 on the Artificial Analysis Intelligence Index, up from 29 for M3, with the average cost per index task falling from about $0.51 to $0.22.

The same report has two numbers from AA-Omniscience, Artificial Analysis's knowledge test, that look like they disagree. M3.1 Flash answered 56% of the questions correctly, ahead of DeepSeek V4.1 Flash at 43% and GLM-5.3 Flash at 28%. Its hallucination rate was 93%. Both are true, and the gap between them is the useful part.

What 93% does not mean

It does not mean 93% of its answers were wrong. Artificial Analysis's benchmarking methodology scores each response as correct, wrong, or an abstention, and the index "subtracts points for hallucinated responses" while it "keeps abstentions neutral". The hallucination rate looks only at the questions a model did not get right, and asks how many of those it answered wrongly rather than declining.

Put the two numbers together. M3.1 Flash got 56 of every 100 questions right, which leaves 44. At a 93% hallucination rate, about 41 of those 44 were confident wrong answers, and about 3 were "I don't know". In other words, it almost never declines. When it does not know, it guesses, and the guess reads exactly like a right answer.

Accuracy and hallucination rate are different questions

Accuracy
How often is it right? This rewards a model that knows more, and it also rewards guessing, because a guess sometimes lands.
Hallucination rate
When it is not right, does it say so? This rewards a model that knows the edge of what it knows. A low number here is what lets you trust an answer you cannot check.
The overall index
Adds points for right answers and takes them away for wrong ones, so a guess costs more than a refusal. M3.1 Flash's overall AA-Omniscience score was 16, per VentureBeat. Read it next to the other two, not instead of them.

A model can raise its accuracy just by refusing less, and its hallucination rate rises at the same time. That is why a single "accuracy" figure in a launch post tells you less than it seems to.

When a model that guesses is fine

A high hallucination rate matters in proportion to how much of the answer comes from the model's memory. It matters least when something else supplies or checks the facts:

  • The source is in the prompt. Summarising a document, extracting fields from an invoice, answering from retrieved passages. The model is reading, not recalling. See RAG done properly for how to keep it reading.
  • The output is checked by machine. Code that has to pass tests, JSON that has to match a schema, a tool call that fails loudly when it is wrong. A guess that fails a check costs you a retry, not a mistake.
  • A person reviews every output anyway. First drafts, brainstorming, rewriting your own text.

It matters most when the model answers from memory and nobody checks: facts about people and companies, legal or medical questions, citations, numbers, and any agent that acts on what it believes without looking it up. Those are the cases where "I don't know" was the right answer, and a guessing model will almost never give it.

Before you switch, test it on your own work

1. Build a small answer key
Collect around fifty real questions from your own work where you know the answer. Include some the model cannot know: an internal name, a figure from last week, a made-up product.
2. Count three outcomes, not two
Mark each answer right, wrong, or declined. The questions it cannot know are the test. A model that invents an answer to those will do the same in production.
3. Ask it to decline, then check that it does
Add an instruction to answer "not sure" when it lacks the information, and run the set again. Some models follow that instruction and some ignore it. You only find out by counting.
4. Price the checking
A model that costs less per call but needs every answer verified can cost more in total. Add the retries, the review time and the cost of a wrong answer that gets through.

Run the same set against the model you use now. The comparison you care about is not a leaderboard position. It is how many wrong answers each model would have handed you on your own questions.

What is still open

Several of the strongest claims in the launch, including the business-workflow results against Claude Opus 5 and GPT-5.6 Sol, are MiniMax's own comparisons, and VentureBeat notes the evaluation settings differ. The weights are proprietary at launch, with a release planned for October 23, and the licence terms have not been published. If you plan to self-host, wait for the licence before you plan around it.

The story is in the October 19 briefing. For how independent scores feed our picks, see the leaderboard. To compare per-token prices, read LLM pricing compared, and for a wider checklist, how to evaluate an AI tool's reliability.

FREQUENTLY ASKED QUESTIONS
What does a model’s hallucination rate actually measure?
On Artificial Analysis’s AA-Omniscience test, the hallucination rate is the share of questions a model did not get right where it gave a wrong answer instead of declining. It measures whether a model knows when to say it does not know, which is separate from how often it is right.
Does a 93% hallucination rate mean 93% of answers are wrong?
No. It is measured only over the questions the model did not get right. It says how often the model guessed wrongly instead of declining, so a model can have high accuracy and a high hallucination rate at once.
Is a model with a high hallucination rate safe to use?
It depends on where the facts come from. With the source in the prompt, or output checked by tests or a schema, guessing costs a retry. When the model answers from memory and nobody checks, prefer a model that declines when it does not know.
EXPLORE TOOLS

Ready to try AI tools? Explore our curated directory:

SHARE THIS GUIDE

On Artificial Analysis’s AA-Omniscience test, the hallucination rate is the share of questions a model did not get right where it gave a wrong answer instead of declining. It measures whether a model knows when to say it does not know, which is separate from how often it is ri...

Share on X LinkedIn Reddit Email
Copied to clipboard