nemotron-3.5-lightning-30b-a3b
NVIDIA/Open weights/1 provider
NVIDIA Nemotron 3.5 Lightning 30B-A3B is a hybrid Mamba-2 + MoE + Attention model with 30B total and 3B active parameters, pre-trained on over 20T tokens with an NVFP4 recipe and Multi-Token Prediction for fast generation. Up to 1M token context for long-running autonomous agents, sub-agent workhorse deployments, and agentic workflows. Supports reasoning and tool calling. English and coding languages plus Spanish, French, German, Italian, and Japanese. Open weights under the OpenMDW License Agreement v1.1. Part of the NVIDIA Nemotron family.MoreLess
Which id to call
nemotron-3.5-lightning-30b-a3bRequesty routes this id across every provider serving nemotron-3.5-lightning-30b-a3b, picking on price and health and failing over automatically. The id stays valid when a provider changes underneath it.
From /1M input
free
NVIDIA
Context
1.0M
66K output
Endpoints
1
1 region
Regions
1
chat
Capabilities 2/8
1 endpoint / 1 region
Providers serving nemotron-3.5-lightning-30b-a3b
Provider prices, per 1M tokens. Pay as you go adds 5%, or 0% on your own keys.
| Rank | Privacy | ||||||
|---|---|---|---|---|---|---|---|
| 1 | NVIDIA | Global | 1.0M | free | free | free | - |
A column is blank where no qualifying sample exists, and every row links to that provider's endpoint page.
model=
Which id to call
One base url, https://router.requesty.ai/v1, and one key for every id here.
nemotron-3.5-lightning-30b-a3bRequesty routes this id across every provider serving nemotron-3.5-lightning-30b-a3b, picking on price and health and failing over automatically. The id stays valid when a provider changes underneath it.
OpenAI compatible
Call it in three lines
Change the base url, use your Requesty key, set the model to any id on the left. Existing OpenAI SDK code needs no other edit.
123456789101112131415from openai import OpenAI client = OpenAI( api_key="YOUR_REQUESTY_API_KEY", base_url="https://router.requesty.ai/v1", ) response = client.chat.completions.create( model="nemotron-3.5-lightning-30b-a3b", messages=[ {"role": "user", "content": "Explain quantum computing in one paragraph."}, ], ) print(response.choices[0].message.content)
6
More from NVIDIA
nemotron-lightning-3.5-30b-a3b
262K ctx/from $0.05/1 provider
nvidia-nemotron-3-ultra
262K ctx/from $0.37/1 provider
nemotron-3.5-content-safety
131K ctx/from free/1 provider
nemotron-3-ultra-nvfp4
262K ctx/from $0.60/1 provider
nemotron-3-nano-omni-30b-a3b-reasoning
131K ctx/from free/1 provider
nemotron-3-ultra-550b-a55b
1.0M ctx/from free/2 providers
Reference
nemotron-3.5-lightning-30b-a3b questions
Which providers serve nemotron-3.5-lightning-30b-a3b?
nemotron-3.5-lightning-30b-a3b is available from 1 provider through Requesty: NVIDIA. All endpoints share one OpenAI-compatible API and one key, and Requesty fails over between them automatically.
How much does nemotron-3.5-lightning-30b-a3b cost?
Pricing starts at free per million input tokens and free per million output tokens on NVIDIA, the cheapest endpoint. Prices vary by provider and region; the table above shows every endpoint. Those are the upstream provider rates: pay as you go adds 5% on top, or 0% if you bring your own provider keys.
Is nemotron-3.5-lightning-30b-a3b open weights?
Yes. nemotron-3.5-lightning-30b-a3b is an open-weights model from NVIDIA, which is why multiple inference providers can host it. Provider choice affects price, latency, and data-privacy terms, all compared above.
What is the context window of nemotron-3.5-lightning-30b-a3b?
nemotron-3.5-lightning-30b-a3b supports up to 1.0M tokens of context, with up to 66K output tokens per response. Some providers expose a smaller window; check the per-endpoint context column above.
How do I use nemotron-3.5-lightning-30b-a3b with the OpenAI SDK?
Install the OpenAI SDK, set base_url to "https://router.requesty.ai/v1", set your API key to your Requesty key, and set the model to "nemotron-3.5-lightning-30b-a3b" or any endpoint id from the table above. The quickstart section shows Python, JavaScript and cURL snippets.
Should I call nemotron-3.5-lightning-30b-a3b by its managed id or a provider id?
Use the managed id, "nemotron-3.5-lightning-30b-a3b". Requesty picks which of the 1 provider serves each request based on price and health, and fails over when one degrades, so the id keeps working while the routing changes underneath it. Send a provider id like "nvidia/nemotron-3.5-lightning-30b-a3b" only when you need one specific deployment and want no failover.
Route nemotron-3.5-lightning-30b-a3b through one endpoint
One key for 1 provider on this model and 600+ others. No markup on provider prices, automatic failover, caching built in.