Magistral Small 2509 vs Hunyuan Turbo S
Magistral Small 2509 (2025) and Hunyuan Turbo S (2026) are general-purpose language models from MistralAI and Tencent AI Lab. Magistral Small 2509 ships a not-yet-sourced context window, while Hunyuan Turbo S ships a 200K-token context window. This comparison covers specs, pricing, API access, capabilities, benchmarks, input and output token costs, and production fit for coding and agent workloads. It focuses on practical selection signals rather than broad model-family marketing.
Hunyuan Turbo S is safer overall; choose Magistral Small 2509 when provider fit matters.
Decision scorecard
Local evidence first| Signal | Magistral Small 2509 | Hunyuan Turbo S |
|---|---|---|
| Best for | provider-routed production | general production evaluation |
| Decision fit | General | Long context |
| Context window | — | 200K |
| Cheapest output | $1.50/1M tokens | - |
| Provider routes | 2 tracked | 0 tracked |
| Shared benchmarks | 0 shared | 0 shared |
Decision tradeoffs
- Magistral Small 2509 has broader tracked provider coverage for fallback and route flexibility.
- Hunyuan Turbo S has the larger context window for long prompts, retrieval packs, or transcript analysis.
- Local decision data tags Hunyuan Turbo S for Long context.
Monthly cost at traffic
Estimate token spend from the cheapest tracked input and output route or tier on this page.
Magistral Small 2509
$775
Cheapest tracked route/tier: AWS Bedrock
Hunyuan Turbo S
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 Magistral Small 2509 and Hunyuan Turbo S; plan for SDK, billing, or endpoint changes.
- No overlapping tracked provider route is sourced for Hunyuan Turbo S and Magistral Small 2509; plan for SDK, billing, or endpoint changes.
Specs
| Specification | ||
|---|---|---|
| Released | 2025-09-01 | 2026-01-10 |
| Context window | — | 200K |
| Parameters | 24B | — |
| Architecture | - | - |
| License | Apache 2.0OSI-approved | Tencent Hunyuan Community License |
| Openness | Open source | Open weights |
| Weights | Unknown | Unknown |
| Code | Unknown | Unknown |
| Commercial use | Permitted | Restricted |
| Knowledge cutoff | - | - |
Pricing and availability
| Pricing attribute | Magistral Small 2509 | Hunyuan Turbo S |
|---|---|---|
| Input price | $0.50/1M tokens | - |
| Output price | $1.50/1M tokens | - |
| Providers | - |
Capabilities
| Capability | Magistral Small 2509 | Hunyuan Turbo S |
|---|---|---|
| Vision | No | No |
| Multimodal | No | No |
| Reasoning | No | No |
| JSON / Tool use | No | No |
| Structured outputs | No | No |
| Code execution | No | No |
| IDE integration | No | No |
| Computer use | No | No |
| Parallel agents | No | No |
Benchmarks
No shared benchmark scores are currently available for this pair.
Deep dive
The capability footprint is close: both models cover the core production surface. That makes context budget, benchmark fit, and provider maturity more important than a simple checklist. If your application depends on one integration detail, verify it against the provider route you plan to use, not just the base model listing.
Pricing coverage is uneven: Magistral Small 2509 has $0.50/1M input tokens and Hunyuan Turbo S has no token price sourced yet. Provider availability is 2 tracked routes versus 0. Treat unknown pricing as an integration gap, then verify the route you will actually call before estimating production spend.
Choose Magistral Small 2509 when provider fit and broader provider choice are central to the workload. Choose Hunyuan Turbo S 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 Magistral Small 2509 or Hunyuan Turbo S open source?
Magistral Small 2509 is listed under Apache 2.0. Hunyuan Turbo S is listed under Tencent Hunyuan Community License. License labels affect whether you can self-host, redistribute weights, or rely only on hosted APIs, so confirm the upstream license before deployment.
Where can I run Magistral Small 2509 and Hunyuan Turbo S?
Magistral Small 2509 is available on AWS Bedrock and Vercel AI Gateway. Hunyuan Turbo S is available on the tracked providers still being sourced. Provider coverage can affect latency, region availability, compliance posture, and fallback options.
When should I pick Magistral Small 2509 over Hunyuan Turbo S?
Hunyuan Turbo S is safer overall; choose Magistral Small 2509 when provider fit matters. If your workload also depends on provider fit, start with Magistral Small 2509; if it depends on provider fit, run the same evaluation with Hunyuan Turbo S.
What is the main difference between Magistral Small 2509 and Hunyuan Turbo S?
Magistral Small 2509 and Hunyuan Turbo S differ most on context, provider coverage, capabilities, or pricing depending on the data currently sourced. Use the specs table first, then validate the model behavior with your own prompts.
Continue comparing
Popular comparisons for Magistral Small 2509
Popular comparisons for Hunyuan Turbo S
Last reviewed: 2026-10-20. Data sourced from public model cards and provider documentation.