LLM Reference

Code Cushman 002 vs Together AI Qwen2-72B-Instruct

Code Cushman 002 (2021) and Together AI Qwen2-72B-Instruct (2024) compare a coding-specialized model against a standalone API model. Code Cushman 002 ships a not-yet-sourced context window, while Together AI Qwen2-72B-Instruct ships a 33k-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 Together AI Qwen2-72B-Instruct is standalone API model. Choose based on workflow fit before reading any benchmark or price row as decisive.

Decision scorecard

Local evidence first
SignalCode Cushman 002Together AI Qwen2-72B-Instruct
Product typeCoding-specialized modelStandalone API model
Best forcustom coding agents and code generationgeneral production evaluation
Decision fitCodingClassification and JSON / Tool use
Context window33k
Cheapest output-$0.70/1M tokens
Provider routes0 tracked1 tracked
Shared benchmarks0 rows0 rows

Decision tradeoffs

Choose Code Cushman 002 when...
  • Local decision data tags Code Cushman 002 for Coding.
Choose Together AI Qwen2-72B-Instruct when...
  • Together AI Qwen2-72B-Instruct has the larger context window for long prompts, retrieval packs, or transcript analysis.
  • Together AI Qwen2-72B-Instruct has broader tracked provider coverage for fallback and procurement flexibility.
  • Together AI Qwen2-72B-Instruct uniquely exposes Structured outputs in local model data.
  • Local decision data tags Together AI Qwen2-72B-Instruct 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 002

Unavailable

No complete token price in local provider data

Together AI Qwen2-72B-Instruct

$735

Cheapest tracked route/tier: Together AI

Cost delta unavailable until both models have sourced input and output token prices.

Switch friction

Code Cushman 002 -> Together AI Qwen2-72B-Instruct
  • No overlapping tracked provider route is sourced for Code Cushman 002 and Together AI Qwen2-72B-Instruct; plan for SDK, billing, or endpoint changes.
  • Together AI Qwen2-72B-Instruct adds Structured outputs in local capability data.
Together AI Qwen2-72B-Instruct -> Code Cushman 002
  • No overlapping tracked provider route is sourced for Together AI Qwen2-72B-Instruct and Code Cushman 002; plan for SDK, billing, or endpoint changes.
  • Check replacement coverage for Structured outputs before moving production traffic.

Specs

Specification
Released2021-11-152024-06-07
Context window33k
Parameters72B
Architecturedecoder onlydecoder only
LicenseProprietaryApache 2.0(OSI)
OpennessProprietaryOpen source
Commercial useCommercial use with conditionsCommercial use allowed
Knowledge cutoff--

Pricing and availability

Pricing attributeCode Cushman 002Together AI Qwen2-72B-Instruct
Input price-$0.70/1M tokens
Output price-$0.70/1M tokens
Providers-

Capabilities

CapabilityCode Cushman 002Together AI Qwen2-72B-Instruct
VisionNoNo
MultimodalNoNo
ReasoningNoNo
Function callingNoNo
Tool useNoNo
Structured outputsNoYes
Code executionNoNo
IDE integrationNoNo
Computer useNoNo
Parallel agentsNoNo

Benchmarks

No shared benchmark rows are currently sourced for this pair.

Deep dive

The capability footprint differs most on structured outputs: Together AI Qwen2-72B-Instruct. 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 Together AI Qwen2-72B-Instruct has $0.70/1M input tokens. Provider availability is 0 tracked routes versus 1. 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 Together AI Qwen2-72B-Instruct 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 002 or Together AI Qwen2-72B-Instruct open source?

Code Cushman 002 is listed under Proprietary. Together AI Qwen2-72B-Instruct 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 structured outputs, Code Cushman 002 or Together AI Qwen2-72B-Instruct?

Together AI Qwen2-72B-Instruct 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 002 and Together AI Qwen2-72B-Instruct?

Code Cushman 002 is available on the tracked providers still being sourced. Together AI Qwen2-72B-Instruct is available on Together AI. Provider coverage can affect latency, region availability, compliance posture, and fallback options.

When should I pick Code Cushman 002 over Together AI Qwen2-72B-Instruct?

Treat this as a product-type comparison: Code Cushman 002 is coding-specialized model, while Together AI Qwen2-72B-Instruct 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 Together AI Qwen2-72B-Instruct.

Continue comparing

Last reviewed: 2026-05-19. Data sourced from public model cards and provider documentation.