Key takeaways
- Nemotron 3.5 Lightning enters NVIDIA API pricing at $0.08 per 1M input tokens and $0.20 per 1M output tokens.
- Prompt caching reduces the input cost per 1M tokens by 50 percent down to $0.04.
- At $0.20 per 1M output tokens, the model runs 94.87 percent below our database median output rate of $3.90 across 35 tracked models.
- The model features a 1000k context window alongside a maximum output limit of 131k tokens.
- DeepSeek V4 Flash 0731 holds the widest context in our current dataset at 1311k tokens, charging $0.14 input and $0.28 output per 1M tokens.
Nemotron 3.5 Lightning enters the live database at 8 cents per million input tokens
Nemotron 3.5 Lightning entered our pricing feed on 2026-08-12 with standard API rates set at $0.08 per 1M input tokens and $0.20 per 1M output tokens. Evaluating nemotron 3.5 lightning pricing shows NVIDIA positioning this open weights model aggressively within the efficiency tier, offering a massive context window at unit rates far lower than historic benchmarks.
The capabilities recorded in our dataset for this release include Long context, Agents, and Open weights. For engineering teams running heavy text generation, the output cost per 1m tokens of $0.20 sits dramatically below market norms. Across 35 tracked current models in our database, the median output rate is $3.90 per 1M tokens, putting this release at roughly one twentieth of the median output expense.
Because NVIDIA provides open weights alongside API access, teams can choose between hosted infrastructure or self-managed deployments. However, for organizations seeking managed access without hardware management, the public API rates provide a clear benchmark for operational budgeting.
- Standard input rate: $0.08 per 1M tokens.
- Standard output rate: $0.20 per 1M tokens.
- Cached input rate: $0.04 per 1M tokens.
- Release date on record: 2026-08-12.
- Tracked capabilities: Long context, Agents, Open weights.
How Nemotron 3.5 Lightning pricing compares with direct alternatives
Nemotron 3.5 Lightning costs significantly less than DeepSeek V4 Flash 0731 while maintaining competitive rates against Qwen alternatives. In direct comparison, nemotron 3.5 lightning vs Qwen3.7 Flash shows Qwen undercutting NVIDIA on raw token costs, whereas NVIDIA beats DeepSeek across every token category.
Specifically, Qwen3.7 Flash from Qwen charges $0.03 for input tokens and $0.13 for output tokens per 1M tokens. This makes Qwen3.7 Flash 62.5 percent cheaper on input and 35 percent cheaper on output than Nemotron 3.5 Lightning. Conversely, DeepSeek V4 Flash 0731 from DeepSeek charges $0.14 per 1M input tokens and $0.28 per 1M output tokens, making Nemotron 3.5 Lightning 42.86 percent cheaper on input and 28.57 percent cheaper on output.
Another point of comparison in our dataset is Qwen3 32B hosted on Hugging Face, which matches NVIDIA on input cost at $0.08 per 1M tokens but charges $0.28 per 1M output tokens. For output-heavy tasks, Nemotron 3.5 Lightning saves $0.08 per million output tokens compared to Qwen3 32B on Hugging Face.
- Qwen3.7 Flash (Qwen): $0.03 input / $0.13 output per 1M tokens.
- Nemotron 3.5 Lightning (NVIDIA): $0.08 input / $0.20 output per 1M tokens.
- Qwen3 32B (Hugging Face): $0.08 input / $0.28 output per 1M tokens.
- DeepSeek V4 Flash 0731 (DeepSeek): $0.14 input / $0.28 output per 1M tokens.
| Model Name | Provider | Input Rate (per 1M) | Output Rate (per 1M) | Cached Input (per 1M) | Context Window |
|---|---|---|---|---|---|
| Nemotron 3.5 Lightning | NVIDIA | $0.08 | $0.20 | $0.04 | 1000k |
| Qwen3.7 Flash | Qwen | $0.03 | $0.13 | N/A | Tracked |
| Qwen3 32B | Hugging Face | $0.08 | $0.28 | N/A | Tracked |
| DeepSeek V4 Flash 0731 | DeepSeek | $0.14 | $0.28 | N/A | 1311k |
Prompt caching slashes unit costs by 50 percent for agentic workflows
Using cached input for Nemotron 3.5 Lightning lowers the cost to $0.04 per 1M tokens, representing exactly a 50 percent discount over standard input rates. This discount makes repetitive context injections for agents far more economical during prolonged execution cycles.
Autonomous agents frequently re-send systemic instructions, code repositories, and structural templates across multiple reasoning steps. When developers take advantage of nvidia api pricing structures for context caching, input bills drop from $0.08 down to $0.04 per million tokens. This brings the effective input price within a single cent of Qwen3.7 Flash's un-cached baseline rate of $0.03 per million tokens.
For teams operating complex agent loops where system prompts represent 80 percent or more of total input volume, context caching transforms the unit economics. Over long-running agent threads, cached inputs reduce total operational spend substantially compared to providers that do not offer caching discounts.
- Standard input price: $0.08 per 1M tokens.
- Cached input price: $0.04 per 1M tokens.
- Prompt cache discount: 50 percent reduction.
- Primary workload target: Autonomous agents and iterative prompt pipelines.
Context window trade-offs across long-context models
Nemotron 3.5 Lightning provides a 1000k token context window alongside a 131k maximum output token limit. While substantial, this context window is narrower than DeepSeek V4 Flash 0731, which offers 1311k tokens as the widest context in our current dataset.
A context window of 1000k tokens allows teams to load full document suites, code bases, or deep conversation histories into a single request. The generous 131k token maximum output limit ensures that long-form reasoning, document generation, and synthetic dataset creation do not hit premature truncation boundaries.
When deciding between models for extreme long-context tasks, developers must weigh the 311k additional context tokens offered by DeepSeek against the lower token costs of Nemotron. DeepSeek charges $0.14 input and $0.28 output per 1M tokens for its 1311k window, whereas Nemotron provides its 1000k window for $0.08 input and $0.20 output per 1M tokens.
- Nemotron 3.5 Lightning context window: 1000k tokens.
- Nemotron 3.5 Lightning maximum output: 131k tokens.
- DeepSeek V4 Flash 0731 context window: 1311k tokens (widest in tracked dataset).
- DeepSeek V4 Flash 0731 rates: $0.14 input / $0.28 output per 1M tokens.
Monthly cost benchmarks for real-world API workloads
Processing 500 million input tokens and 50 million output tokens per month costs $50.00 on Nemotron 3.5 Lightning under standard rates, dropping to $34.00 when 80 percent of input tokens are cached. Understanding how nemotron 3.5 lightning pricing scales across high volumes highlights clear financial tiers when compared to alternative options.
Consider a baseline production scenario processing 50 million input tokens and 10 million output tokens per month. On Nemotron 3.5 Lightning without caching, the math is (50 * $0.08) + (10 * $0.20), which equals $4.00 for inputs plus $2.00 for outputs, totaling $6.00 per month. If all input tokens qualify for prompt caching, the input expense drops to $2.00 (50 * $0.04), bringing the total monthly bill down to $4.00.
Running that same 50M input and 10M output workload on alternative platforms yields distinct totals. On Qwen3.7 Flash, the monthly total is $2.80 ((50 * $0.03) + (10 * $0.13)). On Hugging Face running Qwen3 32B, the bill reaches $6.80 ((50 * $0.08) + (10 * $0.28)). On DeepSeek V4 Flash 0731, the monthly cost rises to $9.80 ((50 * $0.14) + (10 * $0.28)). For a high-volume scenario of 500M inputs and 50M outputs, DeepSeek costs $84.00 compared to $50.00 for standard Nemotron 3.5 Lightning, demonstrating significant savings at scale.
- 50M input / 10M output (Nemotron standard): $6.00 per month.
- 50M input / 10M output (Nemotron 100% cached input): $4.00 per month.
- 50M input / 10M output (Qwen3.7 Flash): $2.80 per month.
- 50M input / 10M output (DeepSeek V4 Flash 0731): $9.80 per month.
- 500M input / 50M output (Nemotron standard): $50.00 per month.
- 500M input / 50M output (DeepSeek V4 Flash 0731): $84.00 per month.
Which production workloads are worth paying for and which to avoid
Nemotron 3.5 Lightning delivers exceptional value for agent execution and cached context processing, but pure low-context tasks remain cheaper on rival platforms. Verifying whether nemotron 3.5 lightning pricing fits your stack requires separating multi-turn agent pipelines from high-frequency single-turn requests.
This model is worth paying for if your workload relies heavily on long context windows up to 1000k tokens, agent framework loops, or open weights self-hosting strategies. The combination of a $0.04 cached input rate and a $0.20 output rate makes it ideal for complex workflows where large context blocks are repeatedly evaluated.
However, Nemotron 3.5 Lightning is not worth paying for if your application consists entirely of short, un-cached single-turn prompts where Qwen3.7 Flash is accessible. At $0.03 per 1M input tokens and $0.13 per 1M output tokens, Qwen3.7 Flash remains the lower cost option for basic lightweight calls. Furthermore, if your application strictly requires context beyond 1000k tokens up to 1311k tokens, DeepSeek V4 Flash 0731 is necessary despite its higher unit prices.
- Worth paying for: Long-context processing up to 1000k tokens.
- Worth paying for: Multi-step agent loops leveraging 50% prompt cache discounts.
- Worth paying for: Teams planning to migrate from managed API to self-hosted open weights.
- Not worth paying for: Simple, un-cached short prompts where Qwen3.7 Flash saves more money.
- Not worth paying for: Ultra-long contexts exceeding 1000k tokens requiring DeepSeek's 1311k limit.
Frequently asked questions
- What is the nemotron 3.5 lightning api cost for input and output tokens?
- NVIDIA charges $0.08 per 1M input tokens and $0.20 per 1M output tokens for Nemotron 3.5 Lightning. If you use prompt caching, the input rate drops to $0.04 per 1M tokens, which is a 50 percent discount compared to standard input pricing.
- How does Nemotron 3.5 Lightning compare to DeepSeek V4 Flash 0731 on price?
- Nemotron 3.5 Lightning is cheaper across all token types than DeepSeek V4 Flash 0731. DeepSeek charges $0.14 input and $0.28 output per 1M tokens, whereas Nemotron charges $0.08 input and $0.20 output. However, DeepSeek offers a wider context window of 1311k tokens compared to Nemotron's 1000k window.
- What are the context window limits for Nemotron 3.5 Lightning?
- Nemotron 3.5 Lightning supports a maximum context window of 1000k tokens. Its maximum output limit is set to 131k tokens per single request, making it suitable for long-form generation and agentic reasoning tasks.
- Is Nemotron 3.5 Lightning cheaper than Qwen3.7 Flash?
- No, Qwen3.7 Flash is cheaper than Nemotron 3.5 Lightning for standard inputs and outputs. Qwen3.7 Flash charges $0.03 input and $0.13 output per 1M tokens, compared to Nemotron's $0.08 input and $0.20 output rates.
- When was Nemotron 3.5 Lightning released to the pricing index?
- Nemotron 3.5 Lightning was added to our live database on 2026-08-12. It is listed with support for Long context, Agents, and Open weights.
About the author
AIOPLY Pricing Desk
Independent AI cost research, verified against live provider rates
How we workQuality standards
Prices were checked against provider documentation on Aug 18, 2026. Rates change without notice, so confirm current figures with the provider before committing a budget. We publish list prices only and take no payment for placement.
Report a correctionSources and further reading
More from the blog
Pricing updates
Grok API Pricing Explained: What xAI Models Actually Cost to RunA working breakdown of Grok API pricing per million tokens, including cached input, long-context billing, tool calls, and how to forecast a monthly bill.
Pricing updates
Claude Opus API Pricing: How Anthropic Bills Its Most Capable ModelA working breakdown of Claude Opus API pricing per million tokens, including cached input, batch discounts, extended thinking, and how to forecast a monthly Anthropic bill.
Comparisons
Grok vs Claude: API Pricing, Cost per Task and When Each One WinsA cost-first comparison of Grok and Claude API pricing, with worked examples, break-even token volumes, and clear guidance on which model fits which workload.
