Code Cushman 001 vs Nemotron-Nano-9B-v2
Code Cushman 001 (2021) and Nemotron-Nano-9B-v2 (2025) compare a coding-specialized model against a standalone API model. Code Cushman 001 ships a not-yet-sourced context window, while Nemotron-Nano-9B-v2 ships a not-yet-sourced context window. This page treats the result as workflow and deployment fit, not a universal model winner.
Treat this as a product-type comparison: Code Cushman 001 is coding-specialized model, while Nemotron-Nano-9B-v2 is standalone API model. Choose based on workflow fit before reading any benchmark or price row as decisive.
Decision scorecard
Local evidence first| Signal | Code Cushman 001 | Nemotron-Nano-9B-v2 |
|---|---|---|
| Product type | Coding-specialized model | Standalone API model |
| Best for | custom coding agents and code generation | provider-routed production |
| Decision fit | Coding | Classification and JSON / Tool use |
| Context window | — | — |
| Cheapest output | - | $0.16/1M tokens |
| Provider routes | 0 tracked | 3 tracked |
| Shared benchmarks | 0 rows | 0 rows |
Decision tradeoffs
- Local decision data tags Code Cushman 001 for Coding.
- Nemotron-Nano-9B-v2 has broader tracked provider coverage for fallback and procurement flexibility.
- Nemotron-Nano-9B-v2 uniquely exposes Structured outputs in local model data.
- Local decision data tags Nemotron-Nano-9B-v2 for Classification and JSON / Tool use.
Monthly cost at traffic
Estimate token spend from the cheapest tracked input and output route or tier on this page.
Code Cushman 001
Unavailable
No complete token price in local provider data
Nemotron-Nano-9B-v2
$72.00
Cheapest tracked route/tier: OpenRouter
Cost delta unavailable until both models have sourced input and output token prices.
Switch friction
- No overlapping tracked provider route is sourced for Code Cushman 001 and Nemotron-Nano-9B-v2; plan for SDK, billing, or endpoint changes.
- Nemotron-Nano-9B-v2 adds Structured outputs in local capability data.
- No overlapping tracked provider route is sourced for Nemotron-Nano-9B-v2 and Code Cushman 001; plan for SDK, billing, or endpoint changes.
- Check replacement coverage for Structured outputs before moving production traffic.
Specs
| Specification | ||
|---|---|---|
| Released | 2021-11-03 | 2025-08-18 |
| Context window | — | — |
| Parameters | — | 9B |
| Architecture | decoder only | decoder only |
| License | Proprietary | Llama 3 Community |
| Openness | Proprietary | Open weights |
| Commercial use | Commercial use with conditions | Commercial use with conditions |
| Knowledge cutoff | - | 2025-03 |
Pricing and availability
| Pricing attribute | Code Cushman 001 | Nemotron-Nano-9B-v2 |
|---|---|---|
| Input price | - | $0.04/1M tokens |
| Output price | - | $0.16/1M tokens |
| Providers | - |
Capabilities
| Capability | Code Cushman 001 | Nemotron-Nano-9B-v2 |
|---|---|---|
| Vision | No | No |
| Multimodal | No | No |
| Reasoning | No | No |
| Function calling | No | No |
| Tool use | No | No |
| Structured outputs | No | Yes |
| Code execution | No | No |
| IDE integration | No | No |
| Computer use | No | No |
| Parallel agents | No | No |
Benchmarks
No shared benchmark rows are currently sourced for this pair.
Deep dive
The capability footprint differs most on structured outputs: Nemotron-Nano-9B-v2. Both models share the core language-model surface, so the practical split is not just feature count. Use those differences to decide whether the page is about raw model quality, agentic coding support, multimodal ingestion, or predictable structured API behavior.
Pricing coverage is uneven: Code Cushman 001 has no token price sourced yet and Nemotron-Nano-9B-v2 has $0.04/1M input tokens. Provider availability is 0 tracked routes versus 3. Treat unknown pricing as an integration gap, then verify the route you will actually call before estimating production spend.
Choose Code Cushman 001 when coding workflow support are central to the workload. Choose Nemotron-Nano-9B-v2 when provider fit and broader provider choice are more important. For production, rerun your own prompts through the exact provider, region, and tool stack you plan to ship. This keeps the decision grounded in measurable tradeoffs instead of brand-level assumptions. It also helps separate model capability from provider packaging, which can change cost and latency. For teams standardizing a stack, that distinction is often the difference between a benchmark win and a reliable deployment.
FAQ
Is Code Cushman 001 or Nemotron-Nano-9B-v2 open source?
Code Cushman 001 is listed under Proprietary. Nemotron-Nano-9B-v2 is listed under Llama 3 Community. License labels affect whether you can self-host, redistribute weights, or rely only on hosted APIs, so confirm the upstream license before deployment.
Which is better for structured outputs, Code Cushman 001 or Nemotron-Nano-9B-v2?
Nemotron-Nano-9B-v2 has the clearer documented structured outputs signal in this comparison. If structured outputs is mission-critical, validate it against the provider endpoint because model-level support and API-level exposure can differ.
Where can I run Code Cushman 001 and Nemotron-Nano-9B-v2?
Code Cushman 001 is available on the tracked providers still being sourced. Nemotron-Nano-9B-v2 is available on NVIDIA NIM, OpenRouter, and Vercel AI Gateway. Provider coverage can affect latency, region availability, compliance posture, and fallback options.
When should I pick Code Cushman 001 over Nemotron-Nano-9B-v2?
Treat this as a product-type comparison: Code Cushman 001 is coding-specialized model, while Nemotron-Nano-9B-v2 is standalone API model. Choose based on workflow fit before reading any benchmark or price row as decisive. If your workload also depends on coding workflow support, start with Code Cushman 001; if it depends on provider fit, run the same evaluation with Nemotron-Nano-9B-v2.
Continue comparing
Last reviewed: 2026-05-22. Data sourced from public model cards and provider documentation.