Compare AI models
| Specifications | ||
ParametersThe learned values that shape how a model responds. B means billion and T means trillion. For mixture-of-experts models, the total count is larger than the number active for each token. Parameter count alone does not measure quality. | 30B | — |
Context windowHow much information the model can work with in one request, measured in tokens — pieces of words or other data. This includes your question, attachments, conversation and reply. Limits can vary by model variant and provider. | 1M | 256k |
| API pricingUSD per 1M tokens · lower wins | ||
Cheapest inputLowest input rate across every provider on OpenRouter, the lab included. The cheapest endpoint may run a quantised build or a shorter context — see "Available from" on the model page. | $0.06Nebius | — |
Cheapest outputLowest output rate across every provider on OpenRouter, the lab included. May come from a different provider than the cheapest input. | $0.24Nebius | — |
| $24.00Nebius · fp8 | — | |
| These models have no shared benchmark scores. | ||
BullshitBench v2Nonsense detection — Given a confidently-worded but nonsensical prompt, does the AI spot that it makes no sense and push back — instead of playing along and inventing an answer? The score is how often it clearly called out the nonsense. Higher is better. | 28% | — |
SWE-Bench VerifiedCoding — Real coding tasks pulled from open-source projects — the AI has to find and fix actual bugs. A human-checked version of the original SWE-Bench. Higher is better. | 38.8% | — |
SWE-Bench MultilingualMultilingual coding — Like SWE-Bench, but the coding problems span many programming languages, not just one. Tests how broadly the AI can code. Higher is better. | 14.07% | — |
NL2Repo-BenchRepo-level code generation — Tests whether the AI can turn a natural-language requirement into working code across an entire repository, not just produce a single function or patch. Higher is better. | — | 42.9% |
LiveCodeBenchCompetitive coding — Coding problems published so recently the AI can't have seen them in training — a contamination-free test of raw programming skill. Higher is better. | 68.25% | — |
Terminal-Bench 2.1Agentic terminal coding — Can the AI work in a command-line terminal — running commands and finishing technical setup tasks the way a developer would? Higher is better. | 8.29% | — |
Terminal-Bench 2.0Agentic terminal coding — Can the AI work in a command-line terminal — running commands and finishing technical setup tasks the way a developer would? (Version 2.0 of the test.) Higher is better. | — | 65.4% |
τ²-bench · retailAgentic tasks — task success in the retail domain of the second-generation customer-service evaluation | 56.91% | — |
τ²-bench · airlineAgentic tasks — task success in the airline domain of the second-generation customer-service evaluation | 48% | — |
τ²-bench · telecomAgentic tasks — task success in the telecom domain of the second-generation customer-service evaluation | 42.21% | — |
BrowseCompWeb browsing — Can the AI browse the web and track down hard-to-find answers? Higher is better. | 13.74% | — |
Humanity's Last Exam · text only, no toolsMultidisciplinary reasoning — accuracy on the 2,158 text-only questions without tools | 10.89% | — |
Humanity's Last Exam · text only, with toolsMultidisciplinary reasoning — The text-only questions from Humanity's Last Exam, answered with access to tools such as search or code execution. The score is the percentage answered correctly. | 15.48% | — |
AIME 2025Reasoning — single-answer accuracy on the 2025 invitational mathematics exam without tools | 89.06% | — |
GPQA DiamondScience — Graduate-level science questions in biology, physics, and chemistry — hard enough that subject-matter PhDs score around 65%. Higher is better. | 73.04% | — |
MMLU-ProKnowledge — accuracy on the ten-option MMLU-Pro benchmark | 78.3% | — |
| Overview | ||
| Company | NVIDIA | Qwen |
| Release date | Dec 15 2025 | Apr 14 2026 |
| Access | Open Weight | Closed |
| Model details | View model | View model |
Other comparisons
Nemotron 3 NanovsClaude Fable 5.2Qwen3.6-Max-PreviewvsClaude Fable 5.2Nemotron 3 NanovsGPT-6.2 AstraQwen3.6-Max-PreviewvsGPT-6.2 AstraNemotron 3 NanovsGemini 4 NeonQwen3.6-Max-PreviewvsGemini 4 NeonNemotron 3 NanovsMuse EmberQwen3.6-Max-PreviewvsMuse EmberNemotron 3 NanovsGrok 4.7Qwen3.6-Max-PreviewvsGrok 4.7Nemotron 3 NanovsDeepSeek-V4.1-Flash-1017Qwen3.6-Max-PreviewvsDeepSeek-V4.1-Flash-1017Frequently asked questions
Nemotron 3 Nano and Qwen3.6-Max-Preview don't publish scores on any of the same benchmarks, so there's no direct head-to-head comparison. Nemotron 3 Nano shipped 120 days before Qwen3.6-Max-Preview, so benchmark comparisons should account for the intervening progress.
Context windows are 1M (Nemotron 3 Nano) vs 256k (Qwen3.6-Max-Preview). Nemotron 3 Nano is open weight, while Qwen3.6-Max-Preview is closed.
Direct benchmark comparisons are unavailable — Nemotron 3 Nano and Qwen3.6-Max-Preview don't publish scores on any of the same benchmarks.