Code Cushman 002 vs Step 3.7 Flash
Code Cushman 002 (2021) and Step 3.7 Flash (2026) compare a coding-specialized model against a standalone API model. Code Cushman 002 ships a not-yet-sourced context window, while Step 3.7 Flash ships a 256k-token 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 002 is coding-specialized model, while Step 3.7 Flash 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 002 | Step 3.7 Flash |
|---|---|---|
| Product type | Coding-specialized model | Standalone API model |
| Best for | custom coding agents and code generation | reasoning-heavy apps, multimodal apps, and tool-calling agents |
| Decision fit | Coding | Coding, RAG, and Agents |
| Context window | — | 256k |
| Cheapest output | - | $1.15/1M tokens |
| Provider routes | 0 tracked | 3 tracked |
| Shared benchmarks | 0 rows | 0 rows |
Decision tradeoffs
- Local decision data tags Code Cushman 002 for Coding.
- Step 3.7 Flash has the larger context window for long prompts, retrieval packs, or transcript analysis.
- Step 3.7 Flash has broader tracked provider coverage for fallback and procurement flexibility.
- Step 3.7 Flash uniquely exposes Vision, Multimodal, and Reasoning in local model data.
- Local decision data tags Step 3.7 Flash for Coding, RAG, and Agents.
Monthly cost at traffic
Estimate token spend from the cheapest tracked input and output route or tier on this page.
Code Cushman 002
Unavailable
No complete token price in local provider data
Step 3.7 Flash
$448
Cheapest tracked route/tier: StepFun
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 002 and Step 3.7 Flash; plan for SDK, billing, or endpoint changes.
- Step 3.7 Flash adds Vision, Multimodal, and Reasoning in local capability data.
- No overlapping tracked provider route is sourced for Step 3.7 Flash and Code Cushman 002; plan for SDK, billing, or endpoint changes.
- Check replacement coverage for Vision, Multimodal, and Reasoning before moving production traffic.
Specs
| Specification | ||
|---|---|---|
| Released | 2021-11-15 | 2026-05-29 |
| Context window | — | 256k |
| Parameters | — | 198B (11B active) |
| Architecture | decoder only | mixture of experts |
| License | Proprietary | Proprietary |
| Openness | Proprietary | Proprietary |
| Commercial use | Commercial use with conditions | Commercial use with conditions |
| Knowledge cutoff | - | - |
Pricing and availability
| Pricing attribute | Code Cushman 002 | Step 3.7 Flash |
|---|---|---|
| Input price | - | $0.20/1M tokens |
| Output price | - | $1.15/1M tokens |
| Providers | - |
Capabilities
| Capability | Code Cushman 002 | Step 3.7 Flash |
|---|---|---|
| Vision | No | Yes |
| Multimodal | No | Yes |
| Reasoning | No | Yes |
| Function calling | No | Yes |
| Tool use | No | Yes |
| 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 vision: Step 3.7 Flash, multimodal input: Step 3.7 Flash, reasoning mode: Step 3.7 Flash, function calling: Step 3.7 Flash, tool use: Step 3.7 Flash, and structured outputs: Step 3.7 Flash. 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 002 has no token price sourced yet and Step 3.7 Flash has $0.20/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 002 when coding workflow support are central to the workload. Choose Step 3.7 Flash when reasoning depth 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.
FAQ
Is Code Cushman 002 or Step 3.7 Flash open source?
Code Cushman 002 is listed under Proprietary. Step 3.7 Flash is listed under Proprietary. 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 vision, Code Cushman 002 or Step 3.7 Flash?
Step 3.7 Flash has the clearer documented vision signal in this comparison. If vision is mission-critical, validate it against the provider endpoint because model-level support and API-level exposure can differ.
Which is better for multimodal input, Code Cushman 002 or Step 3.7 Flash?
Step 3.7 Flash has the clearer documented multimodal input signal in this comparison. If multimodal input is mission-critical, validate it against the provider endpoint because model-level support and API-level exposure can differ.
Which is better for reasoning mode, Code Cushman 002 or Step 3.7 Flash?
Step 3.7 Flash has the clearer documented reasoning mode signal in this comparison. If reasoning mode is mission-critical, validate it against the provider endpoint because model-level support and API-level exposure can differ.
Which is better for function calling, Code Cushman 002 or Step 3.7 Flash?
Step 3.7 Flash has the clearer documented function calling signal in this comparison. If function calling 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 002 and Step 3.7 Flash?
Code Cushman 002 is available on the tracked providers still being sourced. Step 3.7 Flash is available on StepFun, OpenRouter, and NVIDIA NIM. Provider coverage can affect latency, region availability, compliance posture, and fallback options.
Continue comparing
Last reviewed: 2026-05-29. Data sourced from public model cards and provider documentation.