MAI-Thinking-1
Microsoft · Proprietary · rank 106 · bench-align-v5
Capability shape
Seven axes from the ranking source. A missing axis is drawn as a gap.
Runtime service evidence
Measured values with the date they were observed. Nothing is inferred from a sibling model or a provider claim.
Time to first token: latency to the first answer chunk (Artificial Analysis, via BenchLM). Reasoning models include thinking time, so values can run to tens or hundreds of seconds.
Evidence key: ObservedUnavailable
| Measurement | Value | Observed | Last good | Evidence |
|---|---|---|---|---|
| Time to first token | Unavailable | Unavailable | Unavailable | |
| Throughput | Unavailable | Unavailable | Unavailable |
Regional or per-endpoint measurements appear only when the API supplies them; none are modelled here.
Endpoint and price matrix
Every published price component, including cache reads and writes.
Workload-aware monthly cost example
10 conversations per day × 8 messages × 22 active days, 1200 input and 400 output tokens per message, no cache. This uses the same calculator as the cost simulator, so an unavailable applicable rate makes the example unavailable too.
Benchmark record
14 matched benchmark rows with their published value, unit, and provenance.
Knowledge
| Benchmark | Value | Tasks | Difficulty | Provenance |
|---|---|---|---|---|
| GPQA Graduate-Level Google-Proof Q&A | 84.2 | 448 questions | Graduate level | GPQA: A Graduate-Level Google-Proof Q&A Benchmark |
| GPQA-D GPQA Diamond | 84.2 | Graduate-level science questions | Graduate level | Trinity-Large-Thinking: Scaling an Open Source Frontier Agent |
| MMLU-Pro Massive Multitask Language Understanding Professional | 85 | Multiple subjects | Professional level | MMLU-Pro: A More Robust and Challenging Multi-Task Language Understanding Benchmark |
| SimpleQA Measuring Short-Form Factuality in Large Language Models | 31 | Factual questions | Factual accuracy focused | Measuring short-form factuality in large language models |
Coding
| Benchmark | Value | Tasks | Difficulty | Provenance |
|---|---|---|---|---|
| Terminal-Bench 2.0 Terminal-Bench 2.0 | 46.0 | Terminal-based software tasks | Professional software engineering | Terminal-Bench 2.0 |
| SWE-bench Verified Software Engineering Benchmark Verified | 73.5 | 500 verified issues | Professional software engineering | SWE-bench: Can Language Models Resolve Real-World GitHub Issues? |
| LiveCodeBench v6 LiveCodeBench v6 | 87.7 | Fresh programming problems | Competitive programming level | LiveCodeBench official repository and release documentation |
| SWE-bench Pro SWE-bench Pro | 52.8 | 1,865 repository problems | Long-horizon professional engineering | SWE-Bench Pro: Can AI Agents Solve Long-Horizon Software Engineering Tasks? |
Mathematics
| Benchmark | Value | Tasks | Difficulty | Provenance |
|---|---|---|---|---|
| AIME 2025 American Invitational Mathematics Examination 2025 | 97 | 15 problems | High school olympiad level | American Invitational Mathematics Examination |
| AIME26 AIME 2026 | 94.5 | Competition math problems | Olympiad-style mathematics | Qwen3.6 launch benchmarks |
| HMMT Feb 2026 Harvard-MIT Mathematics Tournament February 2026 | 84.9 | Competition math problems | Olympiad-style mathematics | Qwen3.6 launch benchmarks |
Reasoning
| Benchmark | Value | Tasks | Difficulty | Provenance |
|---|---|---|---|---|
| Graphwalks BFS 128K Graphwalks BFS 0K-128K | 90 | Graph traversal tasks | Algorithmic long-context reasoning | Introducing GPT-5.4 mini and nano |
Instruction Following
| Benchmark | Value | Tasks | Difficulty | Provenance |
|---|---|---|---|---|
| IFBench Instruction Following Benchmark | 85 | — | — | BenchLM |
Agentic
| Benchmark | Value | Tasks | Difficulty | Provenance |
|---|---|---|---|---|
| Terminal-Bench 2.0 Terminal-Bench 2.0 | 46 | Terminal-based software tasks | Professional software engineering | Terminal-Bench 2.0 |
Lifecycle and limitations log
Lifecycle events the source associates with this model, plus what this profile does not claim.
That is not evidence the model has no lifecycle plan — only that this source published none.