Code Cushman 002 vs Qwen2.5-72B
Code Cushman 002 (2021) and Qwen2.5-72B (2025) compare a coding-specialized model against a standalone API model. Code Cushman 002 ships a not-yet-sourced context window, while Qwen2.5-72B ships a 128k-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 Qwen2.5-72B 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 | Qwen2.5-72B |
|---|---|---|
| Product type | Coding-specialized model | Standalone API model |
| Best for | custom coding agents and code generation | tool-calling agents |
| Decision fit | Coding | RAG, Agents, and Long context |
| Context window | — | 128k |
| Cheapest output | - | - |
| Provider routes | 0 tracked | 0 tracked |
| Shared benchmarks | 0 rows | 0 rows |
Decision tradeoffs
- Local decision data tags Code Cushman 002 for Coding.
- Qwen2.5-72B has the larger context window for long prompts, retrieval packs, or transcript analysis.
- Qwen2.5-72B uniquely exposes Function calling and Tool use in local model data.
- Local decision data tags Qwen2.5-72B for RAG, Agents, and Long context.
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
Qwen2.5-72B
Unavailable
No complete token price in local provider data
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 Qwen2.5-72B; plan for SDK, billing, or endpoint changes.
- Qwen2.5-72B adds Function calling and Tool use in local capability data.
- No overlapping tracked provider route is sourced for Qwen2.5-72B and Code Cushman 002; plan for SDK, billing, or endpoint changes.
- Check replacement coverage for Function calling and Tool use before moving production traffic.
Specs
| Specification | ||
|---|---|---|
| Released | 2021-11-15 | 2025-10-10 |
| Context window | — | 128k |
| Parameters | — | 72B |
| Architecture | decoder only | - |
| License | Proprietary | Apache 2.0(OSI) |
| Openness | Proprietary | Open source |
| Commercial use | Commercial use with conditions | Commercial use allowed |
| Knowledge cutoff | - | 2024-09 |
Pricing and availability
| Pricing attribute | Code Cushman 002 | Qwen2.5-72B |
|---|---|---|
| Input price | - | - |
| Output price | - | - |
| Providers | - | - |
Pricing not yet sourced for either model.
Capabilities
| Capability | Code Cushman 002 | Qwen2.5-72B |
|---|---|---|
| Vision | No | No |
| Multimodal | No | No |
| Reasoning | No | No |
| Function calling | No | Yes |
| Tool use | No | Yes |
| Structured outputs | No | No |
| 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 function calling: Qwen2.5-72B and tool use: Qwen2.5-72B. 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 Qwen2.5-72B has no token price sourced yet. Provider availability is 0 tracked routes versus 0. 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 Qwen2.5-72B when provider fit 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 002 or Qwen2.5-72B open source?
Code Cushman 002 is listed under Proprietary. Qwen2.5-72B is listed under Apache 2.0. 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 function calling, Code Cushman 002 or Qwen2.5-72B?
Qwen2.5-72B 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.
Which is better for tool use, Code Cushman 002 or Qwen2.5-72B?
Qwen2.5-72B has the clearer documented tool use signal in this comparison. If tool use is mission-critical, validate it against the provider endpoint because model-level support and API-level exposure can differ.
When should I pick Code Cushman 002 over Qwen2.5-72B?
Treat this as a product-type comparison: Code Cushman 002 is coding-specialized model, while Qwen2.5-72B 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 002; if it depends on provider fit, run the same evaluation with Qwen2.5-72B.
Continue comparing
Last reviewed: 2026-05-10. Data sourced from public model cards and provider documentation.