Gemini 3.1 Pro review: ARC-AGI-2 at 77.1%
Release date: 19 February 2026 | Status: Active | Licence: Closed
Google quietly shipped a model that does something most of its rivals still can't. On 19 February 2026, Google DeepMind released Gemini 3.1 Pro (opens in a new tab), and the number that got everyone's attention was its score on a reasoning test built specifically to be hard to game: 77.1% on ARC-AGI-2 (opens in a new tab).
Here's why that matters for a business reader who has no interest in benchmark trivia. Most AI tests can be passed by a model that has effectively seen the answers before. ARC-AGI-2 is built to block that. It throws problems at a model that aren't in any training set, so a high score points to actual problem-solving rather than good memory. Gemini 3.1 Pro got more of those right than almost anything else on the market.
The catch is that the same model is only middling at writing software. So you end up with a tool that can reason its way through a novel puzzle but stumbles on the day-to-day grind of production code. For Australian teams deciding where to spend their AI budget, that split is the whole story: pick this one for thinking, not for shipping code.
A note on naming before we go further. The article calls it "Gemini 3.1 Pro", though most current availability is under the "Gemini 3.1 Pro Preview" label.
Benchmarks at a glance
| Metric | Score | Context |
|---|---|---|
| SWE-bench Pro | 54.2% | Mid-tier coding |
| MMLU | 88.1% | Just 0.3 pts behind GPT-5.5 |
| ARC-AGI-2 | 77.1% | Outstanding |
| Context window | 1M tokens | Best-in-class |
| Price (input) | $3.50 / 1M tokens | Mid-premium |
| Price (output) | $10.50 / 1M tokens | Reasonable for tier |
A caveat on two rows. The MMLU figure of 88.1% and the claim that it trails GPT-5.5 by 0.3 points could not be confirmed; current sources put Gemini 3.1 Pro at 90.99% on MMLU-Pro (opens in a new tab), a different test. And the pricing in the table is unconfirmed too. See the pricing section below for what the live listings actually say.
The ARC-AGI-2 story
ARC-AGI-2 tests fluid intelligence: can a model solve a problem it has never seen, with no chance to lean on training data? A 77.1% score suggests Gemini 3.1 Pro is doing real abstract reasoning rather than matching patterns it memorised earlier. In practice that shows up in:
- Novel mathematical proofs and derivations
- Abstract logical puzzles
- Creative problem-solving with minimal examples
- Transfer learning across domains
What makes the score worth a second look is how the test was built. ARC-AGI-2 was designed to resist memorisation and shortcut pattern-matching. Score well on it and you're reasoning, not recalling.
The coding paradox
For all that reasoning muscle, Gemini 3.1 Pro lands at just 54.2% on SWE-bench Pro. That puts it below Opus 4.8 at 69.2% (opens in a new tab), and reportedly behind Sonnet 4.6, which one source puts around 53-58% (the exact figure varies by source and could not be pinned down). The gap between abstract reasoning and shipping software is real here. The model handles a clean logic puzzle but struggles with the messy, specification-heavy work of production code.
Pricing analysis
The article lists $3.50 input and $10.50 output per million tokens, but that does not match any current listing. Live pricing on Artificial Analysis (opens in a new tab) and elsewhere shows Gemini 3.1 Pro Preview at roughly $2.00 input and $12.00 output per million tokens, with the rate doubling above 200K tokens. Treat the $3.50/$10.50 figures as unconfirmed.
For reference, Sonnet 4.6 runs $3 input and $15 output (opens in a new tab), and GPT-5.5 runs $5 input and $30 output (opens in a new tab). On the verified numbers, Gemini 3.1 Pro's output pricing undercuts both, which helps for high-output jobs like long-form content or verbose analysis.
Verdict
Reach for Gemini 3.1 Pro when reasoning is the job. The ARC-AGI-2 result is the standout, and the 1M-token context window gives you room to work. The soft coding score keeps it off the shortlist for software engineering, but for research, analysis and hard problem-solving, few models do it better.
Score: 8.1 / 10
Gemini 3.1 Pro review: answer-first summary
Gemini 3.1 Pro review matters because it can change how Founders and operators plan, build, or govern an tool evaluation workflow. Gemini 3.1 Pro launched 19 February 2026 with 54.2% SWE-bench Pro, 88.1% MMLU, and a standout 77.1% on ARC-AGI-2.
The direct answer is this: do not treat the topic as a standalone trend. Treat it as a decision about inputs, outputs, review ownership, data exposure, and whether the workflow produces a result that is faster, safer, or more useful than the current process.
Gemini 3.1 Pro review: implementation checklist
- Define the user, job to be done, and success metric for the tool evaluation workflow.
- Collect real examples, policies, source files, customer questions, or search queries before writing prompts or choosing tools.
- Separate low-risk drafts from decisions that need approval, privacy checks, or senior review.
- Document what the AI is allowed to access, what it must not access, and who signs off before production use.
- Review time to value, adoption rate, cost per workflow, quality review score after a small pilot rather than judging the idea from a demo.
This keeps the work practical. It also gives search engines and AI answer engines a clean factual structure: what the topic is, who it helps, what to do next, and which risks matter before implementation.
Decision criteria for Gemini 3.1 Pro review
| Decision area | What to check | Production signal |
|---|---|---|
| Intent | Does Gemini 3.1 Pro review solve a real workflow problem? | The use case has a named owner and measurable outcome. |
| Data | Can the required data be used safely? | Sensitive data is classified and access is controlled. |
| Quality | Can a reviewer judge the output consistently? | Examples, rubrics, or acceptance criteria exist. |
| Scale | Can the workflow be repeated without hero effort? | The process is documented and can be handed to another team member. |
Practical example for Gemini 3.1 Pro review
A small business could use this article to choose one practical test. For example, a manager might take one customer-facing process, one internal document workflow, or one recurring content task and redesign only that step with AI support. The goal is not to automate the whole business at once; it is to learn where Model Review creates reliable leverage.
The useful deliverable is a short operating note: the trigger, the source material, the prompt or tool, the review checklist, the escalation rule, and the metric. That note becomes the handover asset for staff training, SEO/GEO content, service delivery, or future agent work.
Risks and controls for Gemini 3.1 Pro review
The common failure pattern is moving too quickly from a promising idea into an unmanaged workflow. For Gemini 3.1 Pro review, the risk is not only bad output. It can also be unclear data permission, staff confusion, duplicate content, unreviewed customer advice, or a tool that quietly changes cost or capability.
- Control tool sprawl with a named owner, a review step, and written acceptance criteria.
- Control unclear pricing with a named owner, a review step, and written acceptance criteria.
- Control vendor lock-in with a named owner, a review step, and written acceptance criteria.
- Control unreviewed data sharing with a named owner, a review step, and written acceptance criteria.
Measurement plan for Gemini 3.1 Pro review
A useful AI or SEO initiative should leave evidence. Track time to value, adoption rate, cost per workflow, quality review score and compare the pilot against the current process. If the measure does not improve, keep the learning but avoid scaling the workflow.
For GEO readiness, the page should also answer the core question directly, define the entities involved, include implementation steps, explain tradeoffs, and link readers to the next relevant AI Kick Start service, guide, tool, or article.
Definitions and entities for Gemini 3.1 Pro review
For search, GEO, and staff handover, define the core entities in plain language. In this article the important entities are the workflow owner, the AI tool or model, the source material, the review process, the risk boundary, and the measurable business outcome. Clear definitions make the page easier for people to scan and easier for AI answer engines to quote accurately.
- Workflow owner: the person accountable for deciding whether Gemini 3.1 Pro review belongs in the business process.
- Source material: the documents, examples, policies, URLs, prompts, videos, or customer questions that ground the output.
- Review boundary: the point where a human checks accuracy, privacy, brand voice, or customer impact before the result is used.
- Success metric: the measure that proves whether the tool evaluation workflow is worth repeating.
Gemini 3.1 Pro review versus doing nothing
Doing nothing is also a decision. The cost may be slow manual work, weaker search visibility, inconsistent advice, duplicated effort, or staff using unmanaged AI tools without a shared process. The practical question is whether a controlled pilot can reduce that cost without creating a larger governance problem.
| Option | When it makes sense | What to watch |
|---|---|---|
| Do nothing | The workflow is rare, low value, or already reliable. | Competitors may improve speed, content depth, or service consistency first. |
| Run a small pilot | The task repeats often and has clear review criteria. | Keep scope tight and measure the result against the current process. |
| Build a production workflow | The pilot is repeatable and risk controls are documented. | Assign ownership, monitoring, training, and a rollback path. |
AI Kick Start handover package for Gemini 3.1 Pro review
A production handover should be concrete enough that another person can run it. For Gemini 3.1 Pro review, that means a short brief, a workflow map, approved prompts or tool settings, source material, a review checklist, internal links to supporting resources, and a simple measurement sheet. This is the difference between reading about AI and turning it into operational capability.
That packaging also strengthens E-E-A-T. It shows experience through implementation notes, expertise through decision criteria, authoritativeness through source-aware structure, and trust through risks, controls, and review steps. The article becomes useful even if the reader never buys a tool because it helps them make a better operational decision.
