NVIDIA Nemotron 3.5 Lightning 30B A3B vs Sonar
At a Glance
| Compare | SonarPerplexity | |
|---|---|---|
| Pricing and Limits | ||
| Input priceFrom · USD / 1M tokens | Not reported | $1.00Openrouter ↗ · Sep 22, 2026 |
| Output priceFrom · USD / 1M tokens | Not reported | $1.00Openrouter ↗ · Sep 22, 2026 |
| Context windowMaximum documented tokens | 1,049K | 128K |
| Model facts checked | Sep 3, 2026View model evidence → | Aug 29, 2026View model evidence → |
Token prices are the lowest available sourced USD rates; input and output may use different providers. Cost ranking estimates output spend on LiveBench, not a full request bill. Ranking methodology →
Available Benchmarks
Side-by-Side Facts
| Field | NVIDIA Nemotron 3.5 Lightning 30B-A3B | Sonar |
|---|---|---|
| Developer | NVIDIA | Perplexity |
| Family | Nvidia Nemotron 3 5 Lightning | Sonar |
| Model | NVIDIA Nemotron 3.5 Lightning 30B-A3B | Sonar |
| Version | NVIDIA Nemotron 3.5 Lightning 30B-A3B | Sonar |
| Lifecycle | active | active |
| Released | 2026-08-11 | Unknown |
| Knowledge cutoff | Unknown | Unknown |
| Input modalities | Text | Text |
| Output modalities | Text | Text |
| Context window | 1,049K | 128K |
| Total parameters | 30B | Unknown |
| Active parameters | 3B | Unknown |
| License | openmdw-1.1 | Unknown |
| Open weights | Yes | No |
| API available | Yes | Yes |
| Self-hostable | Yes | No |
| Provider access | Fireworks Ai (Standard) | Openrouter (Standard), Perplexity (Standard) |
| Capabilities | agents, chat, generation, reasoning, tools | chat, citations, search |
NVIDIA Nemotron 3.5 Lightning 30B A3B Capabilities
Sonar Capabilities
Primary Evidence
Sources and Freshness
Questions
NVIDIA Nemotron 3.5 Lightning 30B A3B vs Sonar FAQs
Is NVIDIA Nemotron 3.5 Lightning 30B A3B or Sonar better for coding?+
This comparison does not currently contain a protocol-matched coding benchmark for both NVIDIA Nemotron 3.5 Lightning 30B A3B and Sonar, so Model Markets cannot name a coding leader from pricing, context size, or capability labels alone.
Which is cheaper, NVIDIA Nemotron 3.5 Lightning 30B A3B or Sonar?+
Only Sonar has a directly sourced input price: $1.00 per million tokens. Only Sonar has a directly sourced output price: $1.00 per million tokens.
Which has a larger context window, NVIDIA Nemotron 3.5 Lightning 30B A3B or Sonar?+
NVIDIA Nemotron 3.5 Lightning 30B A3B has the larger sourced context window. NVIDIA Nemotron 3.5 Lightning 30B A3B supports 1,049K and Sonar supports 128K.
Which performs better in benchmarks, NVIDIA Nemotron 3.5 Lightning 30B A3B or Sonar?+
There is no overall benchmark winner: At least two independently verified, protocol-matched benchmarks are required for an overall winner.
Can NVIDIA Nemotron 3.5 Lightning 30B A3B or Sonar be self-hosted?+
NVIDIA Nemotron 3.5 Lightning 30B A3B is the only model in this pair currently marked as self-hostable. NVIDIA Nemotron 3.5 Lightning 30B A3B is open weight; Sonar is not marked open weight.
Can NVIDIA Nemotron 3.5 Lightning 30B A3B and Sonar understand images?+
NVIDIA Nemotron 3.5 Lightning 30B A3B is not documented with image input; Sonar is not documented with image input. This reflects supported input modalities, not vision quality.
Which can generate longer answers, NVIDIA Nemotron 3.5 Lightning 30B A3B or Sonar?+
Neither has a larger sourced maximum output. NVIDIA Nemotron 3.5 Lightning 30B A3B is — and Sonar is —.
Do NVIDIA Nemotron 3.5 Lightning 30B A3B and Sonar support reasoning and tool use?+
NVIDIA Nemotron 3.5 Lightning 30B A3B: reasoning and tool calling. Sonar: none of these features are definitively sourced. Feature support does not establish relative quality.
Which is available from more inference providers, NVIDIA Nemotron 3.5 Lightning 30B A3B or Sonar?+
NVIDIA Nemotron 3.5 Lightning 30B A3B has 1 sourced provider route; Sonar has 2, so Sonar has broader tracked availability.
Which offers better value, NVIDIA Nemotron 3.5 Lightning 30B A3B or Sonar?+
There is no universal value winner. Compare the input and output prices above with the matched benchmark result for your workload: cheaper tokens can be offset by different quality, token usage, latency, or provider availability.