# Atlas with Qwen2.5 72B Instruct: The Flagship Dense Qwen in 2026 > Qwen2.5 72B Instruct runs Atlas at $1.40 per Mtok input and $5.60 per Mtok output with a 128K token (131,072) context window. Qwen2.5 72B Instruct is the flagship dense model of the Qwen2.5 line at 72B parameters, and inside Atlas it is the strongest non-MoE, non-reasoning Qwen you can point the agent at. It gives Atlas 128K tokens (131,072) of context at $1.40 per Mtok input and $5.60 per Mtok output, and because the 72B dense weights are openly published, the hosted DashScope endpoint and your own vLLM deployment are the same model. Reach for it when you want frontier-adjacent quality with weights you can actually download, and pin a cheaper tier in small_model so routine traffic never touches the $5.60 output rate. ## Key takeaways - Qwen2.5 72B Instruct costs $1.40 per Mtok input and $5.60 per Mtok output, with 128K tokens (131,072) of context. - The $5.60 per Mtok output rate is 8x the 7B tier and is not worth it for routine file edits. - 72B dense weights are openly published, so the hosted DashScope endpoint and your own vLLM deployment are the same model. - Best instruction-following in the Qwen2.5 line for Atlas's strict tool-call JSON schemas. - Superseded on reasoning-heavy work by Qwen3 235B-A22B, which costs less per token. ## What is Qwen2.5 72B Instruct best at inside Atlas? Qwen2.5 72B Instruct has the best instruction-following in the Qwen2.5 line for Atlas's strict tool-call JSON schemas. At 72B dense parameters it is the strongest non-MoE, non-reasoning Qwen available in 2026, and it holds 128K tokens (131,072) of context per Atlas session. Tool calling is where a coding agent quietly falls apart. Atlas hands the model a strict JSON schema for every tool, and a model that drops a required argument or emits a stray field burns a turn. Qwen2.5 72B Instruct is the Qwen2.5 tier that gets those schemas right most consistently, which is worth more in an agent loop than a benchmark point. The 128K context (131,072 tokens) also pairs well with Atlas's reciprocal-rank-fusion code search, which tends to return large but relevant hunks: Atlas searches code with hybrid semantic and keyword retrieval fused by reciprocal rank fusion, so what lands in the window is big, and the model needs the room to hold it. Atlas connects to Model Context Protocol servers and exposes their tools to the agent as well, and every one of those tools arrives as another schema Qwen2.5 72B Instruct has to fill correctly. ## How much does Qwen2.5 72B Instruct cost in an Atlas session? Qwen2.5 72B Instruct is $1.40 per Mtok input and $5.60 per Mtok output in 2026. The $5.60 per Mtok output rate is 8x the 7B tier, and it is not worth paying for routine file edits, which is the single most important cost fact on this page. The honest framing of Qwen2.5 72B Instruct pricing is that the output side is the problem. Paying $5.60 per Mtok output for a model to rename a variable or add a null check is a waste, because a 7B tier does that work at one eighth the output rate. The right Atlas configuration therefore splits traffic: pin `"model": "alibaba/qwen2-5-72b-instruct"` in atlas.json for the work that needs it, and pin `"small_model": "alibaba/qwen2-5-7b-instruct"` so cheap traffic does not hit the 72B price. Atlas routes titles, summaries, and subagent chores through the small model slot, and that split is where most of the savings live in a long session. On the input side, $1.40 per Mtok is the price of keeping a large retrieved context in front of a dense 72B. ## Can I self-host Qwen2.5 72B Instruct instead of using DashScope? Yes. The 72B dense weights of Qwen2.5 72B Instruct are openly published, so the hosted DashScope endpoint and your own vLLM deployment are the same model. Atlas loads Alibaba through @ai-sdk/openai-compatible, so an OpenAI-compatible vLLM server drops into the same provider shape. Openly published weights change the risk calculus for a team standardizing on Qwen2.5 72B Instruct. There is no drift between what you validated against the hosted endpoint and what you serve internally, because the parameters are identical. Atlas loads Alibaba through @ai-sdk/openai-compatible, which means the provider plumbing Atlas already uses for DashScope is the same plumbing an OpenAI-compatible server speaks, so pointing Atlas at your own deployment is a configuration change rather than an integration project. That path also lets you keep source code inside your network, and Atlas can build its code index with local Ollama embeddings, keeping code off third-party servers, so both the generation and the retrieval side can be brought in-house. ## What are the tradeoffs of Qwen2.5 72B Instruct in 2026? Qwen2.5 72B Instruct is superseded on reasoning-heavy work by Qwen3 235B-A22B, which costs less per token. That is the uncomfortable fact about the Qwen2.5 flagship in 2026: the sparse successor is both stronger on hard problems and cheaper, so the dense 72B has a narrower job. Two tradeoffs define Qwen2.5 72B Instruct. First, $5.60 per Mtok output is 8x the 7B tier and is not worth it for routine file edits, so the model needs a cost discipline around it or the bill grows without a matching quality gain. Second, Qwen3 235B-A22B is stronger on reasoning-heavy work and costs less per token, which means the case for the dense 72B in 2026 is not raw capability. The case is that Qwen2.5 72B Instruct is dense, non-reasoning, openly published, and predictable: no MoE routing, no thinking trace competing for the output budget, and identical parameters whether you rent it or serve it. If none of those properties matter to your workload, the successor is the better buy. ## When should I switch away from Qwen2.5 72B Instruct mid-session? Switch away as soon as the work stops needing 72B dense quality. Atlas lets you switch the active model and provider on the fly with favorites and recents, so use /models in the TUI to favorite Qwen2.5 72B Instruct, then use model.cycle_recent to bounce between it and a cheaper tier mid-session. The mid-session swap is the practical answer to the $5.60 per Mtok output rate. A real Atlas session is not uniformly hard: there is a stretch of planning and tricky edits where Qwen2.5 72B Instruct earns its price, followed by a long tail of mechanical follow-through where it does not. Open `/models` in the TUI, favorite Qwen2.5 72B Instruct so it sits at the top of the dialog, and bind `model.cycle_recent` into your muscle memory so bouncing down to a cheap tier is one keystroke rather than a config edit. Atlas drafts a plan in a read-only plan agent and asks before switching to a build agent, which gives you a natural seam: spend the 72B on the plan, then decide whether the build actually needs it. ## How does Atlas keep a Qwen2.5 72B Instruct build loop reviewable? Atlas computes a unified diff for every file edit and surfaces it for approval before writing, and it snapshots file changes as git patches so edits can be diffed and rolled back. Both apply to a Qwen2.5 72B Instruct session in 2026 regardless of how strong the model is. Qwen2.5 72B Instruct is non-reasoning, so review is not optional even at the top of the Qwen2.5 line. Atlas computes a unified diff for every file edit and surfaces it for approval before writing, which means nothing lands on disk without you seeing the exact hunk. Every Atlas tool call is permission-gated against allow, ask, and deny rules before it runs, so the bash tool can stay on ask while reads run freely. Atlas snapshots file changes as git patches so edits can be diffed and rolled back, and Atlas reads git branches, status, and diffs, and can stage and create commits on your behalf, which makes the whole Qwen2.5 72B Instruct run a reviewable branch rather than an irreversible mutation of your working tree. ## Setup 1. Export DASHSCOPE_API_KEY in your shell profile. Atlas loads Alibaba through @ai-sdk/openai-compatible. 2. List the tier with `atlas models alibaba` to confirm `qwen2-5-72b-instruct` is present. 3. Add `"model": "alibaba/qwen2-5-72b-instruct"` to atlas.json. 4. Pin `"small_model": "alibaba/qwen2-5-7b-instruct"` so cheap traffic does not hit the 72B price. 5. Use `/models` in the TUI to favorite Qwen2.5 72B Instruct, then use `model.cycle_recent` to bounce between it and a cheaper tier mid-session. ## FAQ ### how much does qwen2.5 72b instruct cost per million tokens Qwen2.5 72B Instruct is $1.40 per Mtok input and $5.60 per Mtok output. The $5.60 output rate is 8x the 7B tier, so pin a cheaper model in Atlas's small_model slot for routine traffic. ### what is the context window of qwen2.5 72b instruct Qwen2.5 72B Instruct has 128K tokens (131,072) of context. That pairs well with Atlas's reciprocal-rank-fusion code search, which tends to return large but relevant hunks. ### can i self host qwen2.5 72b instruct with vllm Yes. The 72B dense weights are openly published, so the hosted DashScope endpoint and your own vLLM deployment are the same model. Atlas loads Alibaba through @ai-sdk/openai-compatible. ### how do i configure qwen2.5 72b instruct in atlas.json Export DASHSCOPE_API_KEY, run `atlas models alibaba` to confirm `qwen2-5-72b-instruct` is present, then add `"model": "alibaba/qwen2-5-72b-instruct"` and pin `"small_model": "alibaba/qwen2-5-7b-instruct"`. ### qwen2.5 72b instruct vs qwen3 235b a22b Qwen2.5 72B Instruct is superseded on reasoning-heavy work by Qwen3 235B-A22B, which costs less per token. Stay on the 72B when you want dense, non-reasoning, openly published behavior. ### how do i switch models mid session in atlas Atlas lets you switch the active model and provider on the fly with favorites and recents. Use `/models` in the TUI to favorite Qwen2.5 72B Instruct, then use `model.cycle_recent` to bounce between it and a cheaper tier. ### is qwen2.5 72b instruct good at tool calling Qwen2.5 72B Instruct has the best instruction-following in the Qwen2.5 line for Atlas's strict tool-call JSON schemas, which matters because Atlas also exposes Model Context Protocol server tools to the agent. --- Canonical HTML: https://runatlas.sh/resources/models/qwen2-5-72b-instruct Source of truth: aeo_pages row `/resources/models/qwen2-5-72b-instruct` (segment: Models) (this file is generated from it, never hand-edited). Licence: Atlas is proprietary with a free core. It is not open source and there is no public source repository.