Updated September 24, 2026. Rank says Inkling is ahead. Price, access, and your workload can each overturn that. Public scores include evidence status and uncertainty.
Both of these models will change. Get the price, version and retirement notices for the pair, each with its source. Follow model changes
Inkling has the higher public score, 54.17 versus 19.1, and the 90% score intervals do not overlap. 8 results are shared. Category rows resting on Estimated evidence or different benchmark sets are marked directional and do not name a winner.
NVIDIA
19.1/100
Estimated · Public rank #186
90% interval 9.2–29.0
Recommendations appear only when a shared evidence basis or an explicit operating constraint supports the call. Secondary and unsupported use cases stay disclosed below the initial list.
No workload recommendation clears the current evidence threshold.
Use the matched evidence, workload costs, and sourced specifications below instead of treating a point score as a universal answer.
Code generation, repair, and software-engineering tasks
Not enough matched evidence
Nemotron 3.5 Lightning 30B A3B NVFP4 is scored on Estimated evidence for coding, so the reading is directional rather than like-for-like.
Tool use, computer use, and multi-step task completion
Not enough matched evidence
Nemotron 3.5 Lightning 30B A3B NVFP4 is scored on Estimated evidence for agentic, so the reading is directional rather than like-for-like.
Prompts that approach the documented context limit
No clear pick
The documented context windows are equal.
1K fresh input + 500 output tokens
Not enough matched evidence
A complete comparable API-rate estimate is not available for both models.
200K cached + 20K fresh input + 10K output tokens
Not enough matched evidence
A complete comparable API-rate estimate is not available for both models.
50K fresh input + 3K output tokens
Not enough matched evidence
A complete comparable API-rate estimate is not available for both models.
Choose a job from the LLM Selector's task catalog to see the category row it rests on, under the same basis rules as the table below. A directional row stays directional; choosing a job never creates a winner.
The same task catalog as the LLM Selector. Each job names the evidence surface it rests on; nothing here adds a new score.
Directional only · BenchAlign v5.7
Inkling scores higher, but at least one score rests on Estimated evidence or a different benchmark set. Directional only, no winner.
Coding scores combine specific tasks and setups. Match the editor, harness, and effort to your workflow.
Shared results can support a head-to-head reading. Results present for only one model describe coverage, not superiority.
3 categories rest on Estimated evidence or different evidence sets. Those rows remain visible for coverage context but do not name a winner.
Only shared public evidence is shown. Sparse evidence stays a ruled list rather than being closed into a radar shape.
Too few matched category axes support a radar. The ruled list below shows only shared benchmark results; positions use each benchmark’s normalized display scale when available.
BrowseCompAgentic
Normalized gap 40.3SWE-bench VerifiedCoding
Normalized gap 24.8HLE w/o toolsKnowledge
Normalized gap 19.5GPQAKnowledge
Normalized gap 12.3IFBenchInstruction following
Normalized gap 6.9Each row shows the public-lane category score for both models: the BenchAlign v5.7 lane for agentic, coding, and knowledge, and the weighted public rows elsewhere, with the same rank each model page reports. A row is like-for-like only when both scores rest on Supported evidence or the same weighted set. Directional and not-comparable rows remain visible, but they never receive a winner.
| Category | Inkling | Nemotron 3.5 Lightning 30B A3B NVFP4 | Basis | Reading |
|---|---|---|---|---|
| Instruction following | 83.9#44/124 | 68.5#67/124 | Like-for-likeProvisional lane · 1 vs 1 weighted rows | Inkling leads |
| Agentic | 36.2Supported · #51/105 | 7.3Estimated · #104/105 | Directional onlyBenchAlign v5.7 lane · 4 vs 4 public rows | Directional only |
| Coding | 36.7Supported · #66/135 | 11.4Estimated · #135/135 | Directional onlyBenchAlign v5.7 lane · 6 vs 4 public rows | Directional only |
| Knowledge | 53.5Supported · #45/158 | 20.7Estimated · #154/158 | Directional onlyBenchAlign v5.7 lane · 6 vs 4 public rows | Directional only |
| Reasoning | 75.2Unranked · 2 rankable rows | 55.9Unranked · 1 rankable row | Not comparableProvisional lane · 0 vs 0 weighted rows | Not comparable |
| Multimodal | 47.6#41/50 | Not ranked | Not comparableProvisional lane · 2 vs 0 weighted rows | Not comparable |
| Multilingual | Not ranked | Not ranked | Not comparableProvisional lane · 0 vs 0 weighted rows | Not comparable |
| Math | 78.5Unranked · 1 rankable row | Not ranked | Not comparableProvisional lane · 1 vs 0 weighted rows | Not comparable |
Ranks count the models scored in each category’s lane, so the agentic, coding, and knowledge denominators (BenchAlign v5.7) differ from the provisional-lane categories. Unranked scores sit on the provisional lane’s scale but never name a winner. Like-for-like rows within 0.5 points read as a practical tie.
Three fixed token mixes turn per-token rates into comparable decisions. Each scenario states context fit and whether cached input had to fall back to the published list-input rate.
1K fresh input + 500 output tokens
Nemotron 3.5 Lightning 30B A3B NVFP4 has no comparable published API token rate.
50K fresh input + 3K output tokens
Nemotron 3.5 Lightning 30B A3B NVFP4 has no comparable published API token rate.
200K cached + 20K fresh input + 10K output tokens
Nemotron 3.5 Lightning 30B A3B NVFP4 has no comparable published API token rate.
Sourced differences are shown directly. Missing facts stay explicit instead of being inferred from a model name or family.
Maximum documented context; output-token limits may be lower.
Inkling
1M
Nemotron 3.5 Lightning 30B A3B NVFP4
Inkling
Not sourced
Nemotron 3.5 Lightning 30B A3B NVFP4
Not sourced
A missing cached-input rate falls back to the listed input rate only in the stated workload estimate.
Inkling
$0.374 per 1M cached input tokens
Nemotron 3.5 Lightning 30B A3B NVFP4
No comparable hosted API rate
NVIDIA Nemotron 3.5 Lightning model cardInkling
Not sourced
Nemotron 3.5 Lightning 30B A3B NVFP4
Not sourced
Inkling
Not sourced
Nemotron 3.5 Lightning 30B A3B NVFP4
Not sourced
Inkling
Not sourced
Nemotron 3.5 Lightning 30B A3B NVFP4
Not sourced
Inkling
Hybrid
Nemotron 3.5 Lightning 30B A3B NVFP4
Reasoning
Inkling
Open Weight
Nemotron 3.5 Lightning 30B A3B NVFP4
Open Weight
Inkling
Open Weight
Nemotron 3.5 Lightning 30B A3B NVFP4
Open Weight
Inkling
2026-07-15
Nemotron 3.5 Lightning 30B A3B NVFP4
2026-08-11
Inkling has the higher public score, 54.17 versus 19.1, and the 90% score intervals do not overlap. That is the clearest overall quality signal in the current public data.
Inkling scores higher for coding on the public lane, 36.7 to 11.4. Nemotron 3.5 Lightning 30B A3B NVFP4 is scored on Estimated evidence for coding, so the reading is directional rather than like-for-like. BenchLM does not name a winner for coding from a directional reading; read the shared benchmark rows directly and test the models on the same task set.
Inkling scores higher for agentic tasks on the public lane, 36.2 to 7.3. Nemotron 3.5 Lightning 30B A3B NVFP4 is scored on Estimated evidence for agentic tasks, so the reading is directional rather than like-for-like. BenchLM does not name a winner for agentic tasks from a directional reading; read the shared benchmark rows directly and test the models on the same task set.
Both models do not have comparable published API token rates, so this page does not name a universal price winner.
Both models list the same context window, 1M.
The full public result ledger is available for audit without forcing a wide desktop table onto a phone.
Terminal-Bench 2.1
Inkling leads this result
BrowseComp
Inkling leads this result
MCP Atlas
Not directly comparable
Terminal-Bench 2.1 (Vals)
Not directly comparable
PinchBench
Not directly comparable
τ³-bench results
Not directly comparable
SWE-bench Verified
Inkling leads this result
SWE-bench Pro
Not directly comparable
Terminal-Bench 2.1
Inkling leads this result
FrontierSWE v2
Not directly comparable
LiveCodeBench (Vals)
Not directly comparable
SWE-bench (Vals)
Not directly comparable
SWE Multilingual
Not directly comparable
SciCode
Not directly comparable
GPQA
Inkling leads this result
GPQA-D
Inkling leads this result
HLE
Not directly comparable
HLE w/o tools
Inkling leads this result
GPQA Diamond (Vals)
Not directly comparable
MMLU-Pro (Vals)
Not directly comparable
MMLU-Pro
Not directly comparable
AIME26
Not directly comparable
One weekly email when material rank, price, or benchmark evidence changes make this matchup worth revisiting.
Read a sample issueJoin 2,000+ readers.
Last updated September 24, 2026
