
Nemotron 3.5 Super VL: NVIDIA's 120B open visiemodel wordt uitgebracht, en voor de 5x-claim is er nog geen scorebord
- OrcaNIEUWOrca: OrcaCyber Zero 1.52026-10-10$3.00 / $7.50 per 1 mln tokens · 72 tok/s
- openaiOpenAI: GPT-6.1 Sol2026-09-2952Intelligentie
- anthropicAnthropic: Claude Sonnet 5.52026-09-2856Intelligentie
- typesafeTypeSafe: Jev 1.132026-09-24$0.04 / $0.00 per 1 mln tokens · 733 tok/s
- OpenAIOpenAI: GPT-6 Luna2026-09-2238Intelligentie
- OpenAIOpenAI: GPT-6 Sol2026-09-2248Intelligentie
- AnthropicAnthropic: Claude Opus 5.52026-09-2258Intelligentie
- xAIGrok 4.72026-09-2146Intelligentie
- OrcaOrca: OrcaCyber Zero 1.02026-09-17$3.00 / $7.50 per 1 mln tokens · 35 tok/s
- OrcaOrca: OrcaVerify Text 1.02026-09-16$2.00 / $0.00 per 1 mln tokens · 821 tok/s
- DeepSeekDeepSeek: DeepSeek V4.1 Flash2026-09-1040Intelligentie
- OpenAIOpenAI: GPT-6 Astra2026-09-0453Intelligentie77Coderen
- GoogleGoogle: Gemini 3.8 Flash2026-09-0241Intelligentie76Coderen
- AlibabaQwen: Qwen3.8 Max (0902)2026-09-0245Intelligentie76Coderen
- AnthropicAnthropic: Claude Fable 5.12026-09-0153Intelligentie82Coderen
- TencentTencent: Hy4 preview2026-08-28$0.83 / $2.50 per 1 mln tokens · 52 tok/s
- AlibabaQwen: Qwen3.8 Flash2026-08-26$0.15 / $0.47 per 1 mln tokens · 107 tok/s
- z-aiZ.ai: GLM 5.3 Flash2026-08-2642Intelligentie72Coderen
- DeepSeekDeepSeek: DeepSeek V4 Flash Vision (Exp)2026-08-21$0.22 / $0.66 per 1 mln tokens · 185 tok/s
- z-aiZ.ai: GLM 5.32026-08-1845Intelligentie75Coderen
NVIDIA Nemotron 3.5 Super VL shipped on October 15, 2026 — an open 120-billion-parameter vision-language model with open weights, open datasets and training recipes, and a claim attached to it that nobody can check yet. The company's launch post calls it "the fastest open agentic model in its class — 5x faster than the next best," and attributes the number to the Artificial Analysis Intelligence Index leaderboard. As of this writing, Artificial Analysis does not list Super VL at all; its Nemotron 3.5 entries stop at Nemotron 3.5 Lightning. That does not make the claim false. It makes it vendor-reported, and it should be read that way until a third party runs the checkpoint.
The other thing worth knowing up front is a three-day gap. The weights went up on Hugging Face at 2026-10-12T15:32Z — the BF16 post-trained build, the base model and the NVFP4 build all within a minute of each other — and the announcement post did not appear until October 15 at 15:00Z, with the model card's own release-date field still reading 10/15/2026. NVIDIA uploaded first and announced later. That is now the normal shape of an open-weights release: the repository is the primary source, and the blog post is the commentary.
Wat er daadwerkelijk is uitgebracht, en wat niet
Drie Super VL-checkpoints, nu allemaal live:
• NVIDIA-Nemotron-3.5-Super-VL-120B-A12B-BF16 — the full-precision post-trained model, the reference build and the one to fine-tune from.
• NVIDIA-Nemotron-3.5-Super-VL-120B-A12B-NVFP4 — the quantized deployment build, produced with NVIDIA Model Optimizer and quantization-aware distillation from the BF16 model.
• NVIDIA-Nemotron-3.5-Super-VL-120B-A12B-Base-BF16 — the pre-post-training base, for anyone who wants to run their own post-training rather than adapt NVIDIA's.
There is a fourth repository, NVIDIA-Nemotron-3.5-Super-VL-120B-A12B-NVFP4-LiLiCorr, which is not a model you prompt. It is a speculative-decoding draft checkpoint: load it alongside the NVFP4 target and it proposes tokens ahead of the main model. Its own card dates it 10/15/2026 and describes it as intended for LiLiCorr deployments tuned for DGX Spark and low-concurrency data-center work.
Two things did not ship, and each matters. There is no price. NVIDIA's announcement states the model is available as an NVIDIA NIM microservice — a production microservice the company says is refreshed every two weeks with security patches and performance work — but publishes no per-token figure anywhere, for NIM or for the third-party platforms carrying it. And there is no independently measured speed number, for the reason above. Everything in the next two sections is NVIDIA's own reporting.
De architectuur in één alinea, omdat die het deploymentverhaal uitlegt.
Super VL is een hybride mixture of experts van Mamba-2 en Transformer: elkaar afwisselende Mamba-2-, MoE- en attentionlagen, 512 routed experts per MoE-laag, plus een C-RADIO vision-encoder en een vision-language connector die op de taal-backbone is vastgebouwd. 120B parameters in totaal, 12B actief per token. De context loopt op tot 1M tokens, en Multi-Token Prediction is native ingebouwd, wat het LiLiCorr draft-checkpoint benut. Inputs zijn tekst, afbeeldingen en video — video als MP4 van maximaal twee minuten, gesampled als frames — en documenten kunnen worden aangeleverd als pagina-afbeeldingen met bijbehorende tekst. Output is alleen tekst.
That shape is why the deployment table is the most useful part of the documentation. NVIDIA's BF16 build wants 4× H100 or 2× GB200. The NVFP4 build wants 1× DGX Spark, 1× H200, 2× H100, or 1× GB200. The gap between those two lines is the whole reason the quantized checkpoint exists, and it is the difference between "a 120B model you rent" and "a 120B model on the desk."
The benchmarks NVIDIA published, and the two problems with them
Label all of this vendor-reported. NVIDIA evaluated Super VL through NeMo Gym and published the recipes, containers, prompts and scoring settings — which is more than most labs do — but NVIDIA trained the model, chose the baselines and ran the harnesses. Nothing here has been reproduced outside the company.

The agentic numbers are the ones the launch leans on. SWE-bench Verified 71.10, SWE-bench Multilingual 67.72, SWE-bench Pro 51.78, tau2-bench retail 69.24, airline 76.50, telecom 73.19, BrowseComp 78.91, and GraphWalks 89.71 at the over-1M-token setting. On reasoning, GPQA-Diamond 89.52 and HLE without tools 31.79, rising to 46.01 with tools — that last figure, NVIDIA notes, comes from a separate internal harness rather than the standard path.
On vision, which is the new capability relative to the text-only Nemotron 3.5 Lightning from August: CharXiv-RQ 80.82, MathVision 78.16, V* 85.60, OCR-Reasoning 65.08, OCRBench-v2 at 68.12 English and 59.15 Chinese, MMLongBench-Doc 62.82, OSWorld 52.14, and Video-MME-v2 32.85.
Nu de twee problemen.
First, the Terminal-Bench 2.1 figure is stated twice and does not agree with itself. The model card reports 66.70. The technical report's summary table reports 60.67. Everything else in those two documents lines up, so this is not two different models — it is one number carrying two values in NVIDIA's own paperwork, and until the recipes are re-run it is not safe to quote either. That is the sort of thing a single independent replication settles in an afternoon, which is exactly why the absence of one matters this week.
Second, the headline efficiency claim and the headline intelligence claim pull in opposite directions, and only one of them is checkable. NVIDIA says Super VL reaches accuracy on multimodal agentic tasks "comparable with NVIDIA's largest reasoning model at roughly one-fifth the parameter count" — Nemotron 3 Ultra 550B A55B has 55B active parameters against Super VL's 12B, a ratio of 4.6×, and the report says Super VL's 51.78 on SWE-bench Pro does surpass Ultra. Fine.
But look at the columns where Super VL is genuinely behind. MMLU-ProX 76.91, against Qwen3.5-122B-A10B at 83.2 and Qwen3.8-Flash-Next at 83.0. AA-Omniscience accuracy 26.20, which is close to the floor of that benchmark and sits below DeepSeek-V4-Flash-0731's 45.0. Video-MME-v2 32.85 against Qwen3.8-Flash-Next at 45.1. BabyVision 29.60 against 46.8. Agentic-terminal at 60.67 or 66.70 against 85.80. Super VL is not the accuracy leader in this weight class on most rows; it is a 12B-active model that NVIDIA is selling on speed and on the breadth of what it ingests in one call, not on beating everything at everything.

De efficiëntiecijfers, die eigenlijk de interessante zijn.
Haal de intelligentievergelijkingen eruit, en de engineeringcijfers zijn concreet:
• Speculative decoding — NVIDIA's post-training MTP boosting lifts average acceptance length from 4.287 to 4.718 tokens under greedy decoding and 3.787 to 4.612 under probabilistic draft sampling.
• Quantization — the released NVFP4 checkpoint recovers 99.62% of BF16 accuracy as a median across 36 benchmarks, so the deployment build is close to lossless by NVIDIA's own measure.
• Doorvoer — tot 4.856 uitvoertokens/s/GPU op één enkele GB200 bij een agentische proxyworkload van 20 beurten, terwijl er ten minste 50 tokens/s/gebruiker worden volgehouden; NVFP4 behaalt 2,43× de BF16-doorvoer onder dezelfde omstandigheden.
• Relatieve doorvoer — 2,34× Qwen3.5-122B-A10B en 1,90× Qwen3.8-Flash-Next bij die workload.
• Serving stack — on NVIDIA Dynamo, NVIDIA claims up to 8× more concurrent users at 85% lower latency.
Elk daarvan is een leverancierscijfer. Het cijfer dat voor iedereen het gemakkelijkst te vervalsen is, is dat van 4.856 tokens/s/GPU, omdat het een eigenschap is van een specifieke GPU en een specifieke workload, niet van een benchmarkrun achter een scoringsharnas.
Het serveren ervan, en wat de twee builds je aan hardware kosten
Both vLLM and SGLang are named as supported runtimes, and NVIDIA ships working launch configurations: four-way tensor parallelism with three MTP draft tokens on 4× H100 for BF16, two-way with five draft tokens on 2× GB200. Hardware coverage is Hopper and Blackwell, Linux only, and NVIDIA lists DGX Spark, DGX Station, RTX PRO, RTX and Jetson on the client side — the same silicon spread the model is positioned against.
De praktische beslissing voor een team dat dit op de dag van de lancering leest, is welke checkpoint je moet ophalen. Als je aan fine-tuning doet, is de BF16-build het enige verstandige startpunt, omdat de NVFP4-build al kwantisatiebewuste distillatie heeft ondergaan en verdere training daar niet goed mee te combineren valt. Als je aan serving doet, is de NVFP4-build degene die op één H200 of een DGX Spark past, en een mediane recovery van 99,62% maakt hem de standaard, tenzij je een specifieke regressie hebt gemeten. Het ophalen van het basismodel is alleen zinvol als je van plan bent je eigen post-trainingpipeline te schrijven, wat een ander project is.
Waar Super VL eigenlijk voor is
Read NVIDIA's own framing and the target is narrow and specific: always-on enterprise agents that digest visual documents. The announcement's example is a web page — extract the text, read the charts, return findings — and the same claim is extended to PDFs, tables and structured documents. The argument for one model instead of a text model plus a separate vision pipeline is context continuity: the document, the data and the decision stay in the same window rather than being handed between systems.
Dat argument is geloofwaardig op het specificatieblad omdat het contextvenster 1M tokens is en de vision-encoder gezamenlijk is getraind, niet er achteraf aan vastgeschroefd. Of het standhoudt bij contact met echte documenten bij 1M tokens is precies de vraag waarop de cijfers van GraphWalks en MMLongBench-Doc zijn gericht, en beide zijn door de leverancier gerapporteerd.
NVIDIA also lists a long adoption roster in the launch post — Scale AI building agents for Skydance and EY, AfterQuery for Hebbia's credit-agreement analysis, AI21 and Alice on cybersecurity, Mercor on coding agents, plus Atlassian, CrowdStrike, Dassault Systèmes, Perplexity, Salesforce and Synopsys among integrators. Those are partnerships named in a press release, which is a statement of intent rather than evidence of production traffic. Treat the roster as a signal about which verticals NVIDIA is targeting, not as a reliability claim.
Hoe je het kunt uitproberen zonder een productiepad op het spel te zetten
Het eerlijke standpunt deze week is dat Super VL een interessant, goed gedocumenteerd, volledig ongeverifieerd open model is, en de juiste manier om een ongeverifieerd open model te evalueren is niet om er op dag één productieverkeer naartoe te routeren.
Locally, the NVFP4 build on a single H200 or a DGX Spark is the cheap test: pull the checkpoint, run your own document set through it, and compare against whatever vision model you use today. That costs you GPU time and nothing else, and it is the only way to get a number that is not NVIDIA's. NVIDIA's own documentation gives you one free head start: the model card and the technical report both specify temperature 1.0 and top_p 0.95 for text, and temperature 0.6 with top_p 0.95 for vision — a starting point you would otherwise spend a day rediscovering.
If you would rather test it behind an API, the availability line matters: Super VL is on Hugging Face, as NVIDIA's own NIM microservice, and through several third-party platforms. NVIDIA has published no price for any of those paths, so any per-token figure you see this week is set by the platform, not by the vendor. On the OrcaRouter side, Nemotron 3.5 Super VL is not on our catalogue — we do not serve it today, so there is nothing here to try it through yet, and we would rather say that than imply otherwise. Everything we do serve sits behind one key across 200-plus models at provider list price with 0% markup, and where a model is available from more than one provider, automatic failover across providers gives you a way to route to a new model on a fraction of traffic and let it fall back to the incumbent when it stumbles. That is the mechanism this kind of launch wants; it is not an offer to serve this particular checkpoint.

One more piece of the release worth a look regardless of whether you want the model: NVIDIA published its post-training datasets alongside it — spans covering agentic tool use, finance, instruction following, long context, fairness and vision-language understanding — plus the RL environments in NeMo Gym. The dataset release is often more reusable than the checkpoint, and it is the part of this launch that costs NVIDIA the most to give away.
Wat te kijken
Vier dingen zouden dit artikel veranderen, ruwweg in volgorde van hoeveel ze zouden uitmaken.
Een eerste onafhankelijke benchmark, van Artificial Analysis of wie dan ook, die ofwel de Super VL-rij oplevert die de 5x-claim impliceert, ofwel weigert dat te doen. Zolang die niet bestaat, is de centrale efficiëntieclaim van de lancering een zin in een persbericht met de naam van een ranglijst eraan verbonden, en het voorbehoud hoort in één adem met het getal te worden genoemd.
A price. NVIDIA has told you the hardware, the runtimes and the licence, and withheld the one figure a buyer needs to compare this against a closed model. When NIM pricing appears, the comparison becomes arithmetic instead of positioning.
The Terminal-Bench 2.1 discrepancy — 66.70 on the model card against 60.67 in the technical report. Whichever is right, one of NVIDIA's two primary documents is wrong, and a corrected re-run would settle several other rows at the same time.
And the walk from "available now" to "actually served." Super VL's benchmark rows compare it against Qwen3.5-122B-A10B, Qwen3.8-Flash-Next, DeepSeek-V4-Flash-0731, GLM-5.3-Flash and Nemotron 3 Ultra 550B A55B — all of which are mature enough to have measured throughput, real prices and production track records. A 12B-active model that ingests video, 1M-token documents and tool calls in one pass is a genuinely useful shape. Whether it earns a routing rule is a question about latency and price stability under load, and NVIDIA has published the first of those only on its own hardware, under its own workload, in its own units.
Benchmarks verouderen en prijzen veranderen; het faalregister niet: de gedocumenteerde AI-incidenten en agentfouten achter modellen in deze klasse zijn verzameld in het OrcaRouter AI Incident Archive, waar elke vermelding haar eigen bronnen, ernstniveau, betrouwbaarheidsklasse en betwistingsmarkering bevat.
Vergeleken in dit artikel1
Herkend uit dit artikel · Benchmarks: Artificial Analysis · dagelijks bijgewerkt
