NVIDIA: Nemotron 3 Super
NVIDIA Nemotron 3 Super is a 120B-parameter open hybrid MoE model, activating just 12B parameters for maximum compute efficiency and accuracy in complex multi-agent applications. Built on a hybrid Mamba-Transformer...
Anyone in the Project can @-mention NVIDIA: Nemotron 3 Super with the team's shared context - pooled credits, one chat, one memory.
Starter is free forever - 1 Project, 100 credits/month, 1 MCP. No card.
Verdict
Best for
- Budget-constrained long-context summarization
- Codebase analysis under cost pressure
- Document QA with tight token budgets
- Prototyping before committing to premium models
Strengths
The 262K context window handles entire codebases, legal documents, or multi-chapter manuscripts in a single pass. Pricing sits well below GPT-4 class models — input tokens cost one-tenth of Claude Sonnet 4, output tokens roughly one-third. NVIDIA's GPU infrastructure likely ensures low-latency inference. For teams already in the NVIDIA ecosystem, integration friction should be minimal.
Trade-offs
Absence of public benchmarks makes capability comparisons speculative. You cannot verify how it stacks up on MMLU, HumanEval, or reasoning tasks against Claude, GPT-4o, or Gemini. The output token cost climbs quickly for generation-heavy workloads — five times the input rate. Early adopters will need to run their own evals before trusting it for production.
Specifications
- Provider
- nvidia
- Category
- llm
- Context length
- 262,144 tokens
- Max output
- 235,929 tokens
- Modalities
- text
- License
- proprietary
- Released
- 2026-03-11
Pricing
- Input
- $0.08/Mtok
- Output
- $0.45/Mtok
- Model ID
nvidia/nemotron-3-super-120b-a12b
Per-token prices show what the model costs upstream. On Switchy your team draws from one shared org credit pool - one plan, one balance for everyone.
Team cost calculator
5 seats · 80 msgs/day
Switchy meters this against your org's shared credit pool - one plan, one balance for everyone.
Providers
| Provider | Context | Input | Output | P50 latency | Throughput | 30d uptime |
|---|---|---|---|---|---|---|
| nvidia | 262k | $0.08/Mtok | $0.45/Mtok | — | — | — |
Performance
Benchmarks
Works well with
Top MCPs
Compatibility data comes from first-party telemetry; once we have enough co-usage signal, top MCPs for this model will appear here.
How Switchy teams use it
Starter prompts
Codebase Architecture Summary
You are reviewing this entire codebase. Identify the core architectural patterns, list the main modules and their responsibilities, and flag any circular dependencies or design smells.
Multi-Document Contract Review
Compare these three contracts for conflicting terms, missing clauses, and liability gaps. Highlight any inconsistencies in payment schedules or termination rights.
Research Paper Synthesis
Summarize the key findings from these five research papers. Identify where results agree, where they conflict, and what methodological choices might explain the differences.
Customer Support Ticket Triage
Review this support ticket thread and the user's account history. Recommend the next troubleshooting step and flag whether escalation to engineering is warranted.
Meeting Notes to Action Items
Extract all action items from this meeting transcript. For each item, list the owner, deadline, and any dependencies mentioned in the discussion.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
Review this Python function for potential bugs and suggest improvements. Focus on edge cases and performance: ```python def find_duplicates(items): seen = [] dupes = [] for item in items: if item in seen: dupes.append(item) seen.append(item) return dupes ```
This function has a critical performance issue: using `item in seen` on a list creates O(n²) complexity. For large inputs, this becomes prohibitively slow. Edge case bug: if the input contains the same duplicate multiple times (e.g., [1,1,1,1]), it adds that duplicate to `dupes` for each occurrence after the first, which is likely unintended. Improved version: ```python def find_duplicates(items): seen = set() dupes = set() for item in items: if item in seen: dupes.add(item) else: seen.add(item) return list(dupes) ``` This runs in O(n) time and returns each duplicate once.
Nemotron 3 Super's 262K token context window enables it to analyze entire codebases in one pass, making it particularly effective for architectural reviews. This example shows its ability to identify both algorithmic inefficiencies and logical bugs. The trade-off: without public benchmarks, its code generation accuracy relative to specialized coding models remains unverified.
Summarize the key regulatory requirements from this 50-page compliance document, then draft three specific action items our legal team should prioritize this quarter. [Document text would follow...]
The model would process the full document (well within its 262K token capacity) and produce a structured summary identifying: (1) new data retention requirements taking effect in Q3, mandating 90-day deletion cycles for certain customer data categories; (2) expanded consent language requirements for EU users; (3) mandatory security audit documentation for third-party processors. Priority actions: First, audit current data retention policies against the new 90-day requirement and implement automated deletion workflows. Second, update consent forms and deploy revised versions across all EU-facing properties by end of Q2. Third, request SOC 2 reports from all active data processors and establish a quarterly review cadence.
This showcases Nemotron 3 Super's long-context strength — processing entire documents without chunking or summarization loss. The $0.08 input pricing makes large-document analysis economical compared to models charging $0.15+. However, the lack of published benchmarks means users can't compare its summarization accuracy against alternatives like Claude or GPT-4.
I'm designing a customer onboarding flow for a B2B SaaS product. Walk me through the psychological principles I should consider, then suggest a 5-step sequence that balances user education with time-to-value.
Key psychological principles: Progressive disclosure prevents cognitive overload by revealing complexity gradually. The endowed progress effect (starting users at 20% complete rather than 0%) increases completion rates. Social proof during onboarding reduces uncertainty for risk-averse B2B buyers. Suggested sequence: (1) Single-field welcome screen asking for primary use case — establishes relevance immediately. (2) Guided 2-minute product tour highlighting the one feature that maps to their stated use case. (3) Assisted creation of their first project with pre-filled templates. (4) Invitation to add one team member, leveraging commitment and social dynamics. (5) Dashboard view showing their progress (marked as 60% complete) with clear next steps. This gets users to a working state in under 10 minutes while building investment through incremental commitment.
Nemotron 3 Super handles open-ended strategic questions with structured, actionable responses. The $0.45/Mtok output pricing is competitive for this use case where response length matters. The model synthesizes multiple domains (psychology, UX, business strategy) effectively, though without benchmark data, its reasoning depth compared to o1 or Claude Opus is unclear.
Use-case deep-dives
When 262K context handles contract review without chunking overhead
A 4-person legal tech startup needs to compare clauses across 40-page vendor agreements for SaaS clients. Nemotron 3 Super's 262K context window fits entire contract sets in one prompt—no retrieval pipeline, no chunking errors where definitions span pages. At $0.08/$0.45 per Mtok, a 200K-token analysis (5 contracts, full cross-reference) costs roughly $0.11 per run. The trade-off: without public benchmarks, you're trusting NVIDIA's internal evals for accuracy on legal reasoning. If your clients demand audit trails tied to specific model scores (MMLU, LegalBench), wait for published numbers. If speed-to-answer and context density matter more than third-party validation, this is the call for document-heavy workflows under 50 requests/day.
Why 262K context beats RAG for multi-turn support transcripts
A 12-person B2B support team handles Slack threads that stretch across 30+ messages, referencing past tickets and product docs. Nemotron 3 Super loads the entire conversation history plus knowledge base excerpts (combined 180K tokens) without external vector search. Each response costs $0.09-$0.12 depending on output length—cheaper than maintaining Pinecone + a smaller-context model when your median thread is 80K tokens. The risk: no MMLU or MT-Bench scores means you're flying blind on instruction-following quality compared to Opus or GPT-4. If your support SLA tolerates 5% hallucination and you're optimizing for context retention over benchmark pedigree, this works. If customers escalate on accuracy, stick with a scored model until NVIDIA publishes evals.
When to use 262K context for manuscript-scale rewrites
A 3-person editorial agency rewrites 15K-word white papers for enterprise clients, preserving technical accuracy across sections. Nemotron 3 Super fits the full draft plus style guide (combined 60K tokens) in one context, letting the model cross-check terminology and tone without losing thread. At $0.08 input, loading a 60K-token manuscript costs $0.005; a 10K-token rewrite output costs $0.0045—total $0.0095 per job. The ceiling: without Creative Writing or GPQA benchmarks, you can't compare its rewrite quality to Claude Opus ($15/$75 per Mtok, proven on long-form). If you're under 100 jobs/month and can QA outputs manually, the 5x price advantage justifies the eval gap. Above that volume, benchmark transparency becomes the bottleneck.
Frequently asked
Is Nemotron 3 Super good for general text generation?
Yes, but with limited public validation. The 262k context window handles long documents well, making it suitable for summarization and analysis tasks. However, no public benchmarks exist yet, so you're relying on NVIDIA's internal testing. If you need proven performance metrics before committing, wait for independent evaluations or test it yourself on your specific workload.
Is Nemotron 3 Super cheaper than GPT-4o?
Yes, significantly. At $0.08 input and $0.45 output per million tokens, it costs roughly 75% less than GPT-4o for most workloads. The output pricing is competitive with Claude Sonnet 3.5. If cost is your primary constraint and you can tolerate the lack of public benchmarks, Nemotron 3 Super offers substantial savings for high-volume text processing.
Can it handle 262k tokens in practice?
The advertised context window is 262k tokens, which theoretically supports documents around 200k words. However, without public benchmark data on long-context retrieval accuracy or latency at max capacity, real-world performance remains unverified. Test your specific use case at scale before relying on the full window for production applications requiring precise information extraction.
How does Nemotron 3 Super compare to Llama 3.3 70B?
Direct comparison is impossible without shared benchmarks. Llama 3.3 70B has extensive public testing showing strong reasoning and coding performance. Nemotron 3 Super offers a larger context window (262k vs 128k) and potentially lower latency through NVIDIA's infrastructure, but lacks the community validation. Choose Llama if you need proven capabilities; choose Nemotron if context length and NVIDIA integration matter more.
Should I use this for customer support chatbots?
Possibly, but verify latency first. The pricing is attractive for high-volume chat applications, and the large context window helps maintain conversation history. However, without public latency benchmarks or quality metrics, you're taking a risk on response time and accuracy. Run a pilot with real customer queries and measure both speed and answer quality before full deployment.
Compare with
More language models
- NVIDIA: Nemotron 3 Super (free)nvidia
- NVIDIA: Nemotron 3 Ultranvidia
- NVIDIA: Nemotron 3 Ultra (free)nvidia
- NVIDIA: Switchyardnvidia
- OpenAI: GPT-3.5 Turboopenai
- OpenAI: GPT-3.5 Turbo 16kopenai
- OpenAI: GPT-3.5 Turbo (batch)openai
- OpenAI: GPT-3.5 Turbo Instructopenai
- OpenAI: GPT-3.5 Turbo (older v0613)openai
- OpenAI: GPT-4openai
- OpenAI: GPT-4.1openai
- OpenAI: GPT-4.1 (batch)openai