Compare AI models
| Specifications | ||
ParametersA rough measure of how big the model is. More parameters usually means more capable and more expensive to run, though it is a poor guide on its own — a smaller, newer model often beats a larger, older one. | 2.8T | 30B |
Context windowHow much text the model can hold in mind at once — your question, any documents you attach, the conversation so far, and its own reply. Go past it and the earliest part falls out of view. | 1M | — |
| API pricingUSD per 1M tokens · lower wins | ||
Input priceWhat you pay for everything you send the model — your question, plus any documents or earlier conversation you include with it. | $3.00 | — |
Output priceWhat you pay for the text the model writes back. It is normally the dearer half: producing an answer costs more than reading one. | $15.00 | — |
Cached input priceA reduced rate for text you send over and over. If every request starts with the same instructions or the same document, the provider keeps a copy ready and charges less to read it again. | $0.30 | — |
Cheapest inputLowest input rate across third-party providers, excluding the lab itself. The cheapest endpoint may run a quantised build or a shorter context — see "Available from" on the model page. | $0.33Wafer | $0.05Novita |
Cheapest outputLowest output rate across third-party providers, excluding the lab itself. May come from a different provider than the cheapest input. | $12.75Makora | $0.20Novita |
| Benchmarks | ||
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. | 74% | 28% |
GPQA DiamondScience — Graduate-level science questions in biology, physics, and chemistry — hard enough that subject-matter PhDs score around 65%. Higher is better. | 93.5% | 73% |
CheatBenchCheating rate — Measures how often AI agents try to cheat on difficult assignments, such as reading hidden answers, copying work or manipulating grading. The overall score gives equal weight to ten categories; the sycophancy category measures how far an agent shifts its beliefs toward a user's stated views. Scores describe each model in its tested agent setup, and task success is measured separately. Lower is better. | 70% | — |
DeepSWE 1.1Agentic coding — Artificial Analysis' independent test of deep, agentic software-engineering work — the AI has to plan and carry out substantial coding tasks end to end. (Version 1.1 of the test.) Higher is better. | 69% | — |
DeepSWE 1.0Agentic coding — Artificial Analysis' independent test of deep, agentic software-engineering work — the AI has to plan and carry out substantial coding tasks end to end. Higher is better. | 67.5% | — |
Next.js EvalsNext.js coding — Vercel's open eval of how well AI coding agents build and migrate real Next.js apps — measured as the share of tasks the agent completes successfully. Higher is better. | 84% | — |
Supabase Evals · with skillsSupabase coding — Supabase's own open benchmark: a coding agent is dropped into a real Supabase project and asked to do real work — set up a schema, fix a broken security policy, debug an Edge Function — and every run is checked against a live Supabase stack. This is the headline number, where the agent has Supabase's own skills loaded, as most people building on Supabase would. The score is the share of scenarios it got right. Higher is better. | 87% | — |
Supabase Evals · no skillsSupabase coding — The same Supabase scenarios, but with none of Supabase's skills loaded — so it measures what the model already knows about building on Supabase, rather than how well it follows Supabase's supplied instructions. Higher is better. | 84.1% | — |
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.3% |
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. | 88.3% | — |
MCP AtlasMulti-step tool use — Can the AI chain together many tools and steps to complete one bigger task, rather than doing just a single thing? Higher is better. | 84.2% | — |
JobBenchProfessional tool use — Tests the AI on professional workplace tasks that require using real work tools — the kind of multi-step jobs an office worker handles. Higher is better. | 52.9% | — |
Toolathlon-VerifiedPersonal tool use — Tests how well the AI uses everyday personal tools and apps to get things done — a human-checked version of Toolathlon. Higher is better. | 73.2% | — |
BrowseCompWeb browsing — Can the AI browse the web and track down hard-to-find answers? Higher is better. | 91.2% | — |
Humanity's Last Exam · no toolsMultidisciplinary reasoning — Humanity's Last Exam — extremely hard expert questions across many subjects, written so you can't just look up the answer. “No tools” means the AI answers on its own. Higher is better. | 43.5% | — |
Humanity's Last Exam · with toolsMultidisciplinary reasoning — Humanity's Last Exam — extremely hard expert questions across many subjects. “With tools” means the AI is allowed to search the web or run code while answering. Higher is better. | 56% | — |
ARC-AGI-2Abstract reasoning — Puzzle-style tests of abstract reasoning and pattern-finding — the kind of thing people find easy but AIs often struggle with. Higher is better. | 60.4% | — |
GDPval-AA v2Knowledge work — economically valuable knowledge work (v2, re-based Elo) | 1668 | — |
CharXiv ReasoningChart reasoning — Can the AI read and reason about complex charts and figures, not just text? Higher is better. | 84.8% | — |
MMMU-ProMultimodal reasoning — A tougher version of MMMU — college-level questions that mix images, diagrams, and text together. Higher is better. | 81.6% | — |
threejsevalCommunity preference (Three.js) — Every model gets the same prompt — "the Eiffel Tower", "a glass fishbowl", "a robot arm picking toys into a box" — and builds a 3D scene in Three.js. Real people then see two scenes side by side, names hidden, and vote for the one they prefer. The votes become a chess-style Elo rating on threejseval.com, averaged across all the prompts. It measures whether the scene looks and moves right to a human eye, not whether the code passes a test. Higher is better. | 1515 | — |
| Overview | ||
| Company | Moonshot AI | NVIDIA |
| Release date | Jul 16 2026 | Dec 15 2025 |
| Access | Open Weight | Open Source |
| Model details | View model | View model |
Other comparisons
Kimi K3vsClaude Haiku 5.5Nemotron 3 NanovsClaude Haiku 5.5Kimi K3vsGPT-6.1 SolNemotron 3 NanovsGPT-6.1 SolKimi K3vsGemini 4 ArgonNemotron 3 NanovsGemini 4 ArgonKimi K3vsMuse Spark 1.3Nemotron 3 NanovsMuse Spark 1.3Kimi K3vsGrok 4.7Nemotron 3 NanovsGrok 4.7Kimi K3vsDeepSeek-V4.1-FlashNemotron 3 NanovsDeepSeek-V4.1-FlashFrequently asked questions
Kimi K3 leads Nemotron 3 Nano on 2 of the 2 benchmarks they both report (BullshitBench v2, GPQA Diamond). Only Kimi K3 has a verified first-party API price: $3.00 per million input tokens and $15.00 per million output tokens. No pay-as-you-go API rate is tracked for Nemotron 3 Nano. Nemotron 3 Nano shipped 213 days before Kimi K3, so benchmark comparisons should account for the intervening progress.
Kimi K3 has 2.8T parameters, while Nemotron 3 Nano has 30B. Kimi K3 is open weight, while Nemotron 3 Nano is open source.
On BullshitBench v2, Kimi K3 leads at 74% vs Nemotron 3 Nano at 28%. On GPQA Diamond, Kimi K3 leads at 93.5% vs Nemotron 3 Nano at 73%.