Together AI (gateway) offers the broadest catalog of open-weights models under one key, from Qwen3.7 Max to DeepSeek V4 Pro to Kimi K2.7, and it is where you go when you want open models at scale without running the hardware. Context varies by model (up to 1M on Qwen3.7 Max). Pricing is Qwen3.7 Max $1.25 / $3.75; DeepSeek V4 Pro $1.74 / $3.48; Kimi K2.7 Code $0.95 / $4 per Mtok. Together AI serves open-weights only, so no Claude, no GPT-5, no Gemini.
What is Together AI best at inside Atlas?
Together AI (gateway) is best inside Atlas at running large open-weights models you could never host yourself. Together AI serves the full Qwen3-Coder line including the 480B variant, which needs 250GB to run locally, and exposes it to Atlas behind a single TOGETHER_API_KEY.
The Qwen3-Coder 480B case is the clearest argument for Together AI (gateway). Running that model locally means 250GB of memory, which is not a workstation, it is a server rack. Together AI serves it, and Atlas drives it like any other model: pin it in atlas.json with "model": "togetherai/Qwen/Qwen3-Coder-480B-A35B-Instruct-FP8" and the build agent uses it. Atlas indexes code by AST declarations using tree-sitter and searches with hybrid semantic and keyword retrieval fused by reciprocal rank fusion, so the model gets real declaration bodies to reason over, and Atlas computes a unified diff for every file edit and surfaces it for approval before writing.
How much does Together AI cost compared to first-party APIs?
Together AI (gateway) prices Qwen3.7 Max at $1.25 / $3.75 per Mtok, which is half Alibaba's first-party rate of $2.50 / $7.50 for the same model. DeepSeek V4 Pro runs $1.74 / $3.48 and Kimi K2.7 Code runs $0.95 / $4 per Mtok.
The headline number on Together AI (gateway) is Qwen3.7 Max at $1.25 / $3.75 per Mtok against $2.50 / $7.50 first-party from Alibaba, an exact halving on both sides of the meter. For an Atlas workload, where hybrid retrieval pushes a lot of code into the input and every file edit produces a unified diff on the output, both halves matter. DeepSeek V4 Pro at $1.74 / $3.48 has a notably flat ratio, only twice the input rate on output, which suits diff-heavy sessions. Kimi K2.7 Code at $0.95 / $4 is the opposite shape: cheap to feed, expensive to generate from.
Why do teams route Atlas through Together AI instead of going direct?
Teams route Atlas through Together AI (gateway) for US-hosted inference on models whose first-party APIs sit in China. DeepSeek, Qwen, Kimi, and GLM are 4 such families, and Together AI serves the same open weights on US infrastructure, at $1.74 / $3.48 per Mtok for DeepSeek V4 Pro.
This is a data-residency decision more than a price decision, although Together AI (gateway) usually wins on both. The weights for DeepSeek V4 Pro, Qwen3.7 Max, and Kimi K2.7 Code are open, so the model your Atlas session talks to is the same model regardless of who serves it. What changes is where the request lands. For a team whose code cannot leave US infrastructure, Together AI at $1.74 / $3.48 for DeepSeek V4 Pro is the only way to use that model at all. Pair it with Atlas's permission gating, where every tool call is checked against allow, ask, and deny rules before it runs.
What context window does Together AI give Atlas?
Context on Together AI (gateway) varies by model, up to 1M on Qwen3.7 Max. That 1M window is the largest Together AI exposes, and it is enough for Atlas to hold a wide hybrid search result, several source files, and an accumulating stack of unified diffs in a single turn.
Because Together AI (gateway) is a catalog rather than a single model, the window is a per-model property. Qwen3.7 Max reaches 1M at $1.25 / $3.75 per Mtok, while other entries in the catalog carry smaller windows. Run `atlas models togetherai` to see the exact model IDs and what each one exposes, because the IDs are case-sensitive, for example Qwen/Qwen3.7-Max. Getting the ID wrong is the most common Together AI setup failure inside Atlas, and it is why the documented flow is to select a model from `/models` rather than hand-typing the string.
When should you pick a different provider instead of Together AI?
Pick a different provider than Together AI (gateway) when the task needs a proprietary frontier model. Together AI is open-weights only: no Claude, no GPT-5, no Gemini. Pricing also varies by model and quantization tier, so the same model name can cost different amounts depending on the exact ID.
Two real frictions with Together AI (gateway). First, the catalog boundary: open weights only, so Claude, GPT-5, and Gemini are simply not reachable. Keep a frontier provider registered in Atlas for those turns, since Atlas lets you switch the active model and provider on the fly with favorites and recents. Second, the quantization tiers: the same model name can cost different amounts depending on the exact ID you select, which is why the FP8 suffix in togetherai/Qwen/Qwen3-Coder-480B-A35B-Instruct-FP8 is not decoration. Confirm the ID and its price with `atlas models togetherai` before pinning it in atlas.json.
Setup
- 01Export `TOGETHER_API_KEY=...`. Atlas loads it via `@ai-sdk/togetherai`.
- 02Run `atlas models togetherai` to see the exact model IDs (they are case-sensitive, for example Qwen/Qwen3.7-Max).
- 03Select a model from `/models` in the Atlas TUI.
- 04Pin it in atlas.json, for example "model": "togetherai/Qwen/Qwen3-Coder-480B-A35B-Instruct-FP8".
Frequently asked questions
- how to use together ai with atlas
- Export `TOGETHER_API_KEY=...`, which Atlas loads via `@ai-sdk/togetherai`. Run `atlas models togetherai` to see the exact case-sensitive model IDs, then select one from `/models` or pin it in atlas.json.
- how much does qwen3.7 max cost on together ai
- Qwen3.7 Max costs $1.25 / $3.75 per Mtok on Together AI, which is half Alibaba's first-party rate of $2.50 / $7.50 for the same model. Its context window reaches 1M tokens.
- can i run qwen3-coder 480b without a gpu cluster
- Yes, through Together AI. The Qwen3-Coder 480B variant needs 250GB to run locally, but Together AI serves the full Qwen3-Coder line. Pin it in Atlas as "model": "togetherai/Qwen/Qwen3-Coder-480B-A35B-Instruct-FP8".
- is together ai us-hosted
- Together AI provides US-hosted inference for models whose first-party APIs are in China, including DeepSeek, Qwen, Kimi, and GLM. That is the usual reason teams route an Atlas session through it rather than going direct.
- does together ai support claude or gpt-5
- No. Together AI is open-weights only: no Claude, no GPT-5, no Gemini. Keep a frontier provider registered in Atlas alongside it, since Atlas lets you switch the active model and provider on the fly.
- why do together ai model ids fail in my config
- Together AI model IDs are case-sensitive, for example Qwen/Qwen3.7-Max. Run `atlas models togetherai` to copy the exact ID, and prefer selecting from `/models` over hand-typing the string into atlas.json.
- how much does deepseek v4 pro cost on together ai
- DeepSeek V4 Pro costs $1.74 / $3.48 per Mtok on Together AI. The flat input-to-output ratio suits Atlas sessions that generate many unified diffs, since output tokens are only twice the input rate.
Try Atlas in your terminal
The terminal-native AI coding agent. Free core, single binary.
Install AtlasRelated guides
Atlas for Crystal: A Terminal-Native AI Coding Agent for shard.yml Projects in 2026
Atlas is a terminal-native AI coding agent for Crystal in 2026. It reads shard.yml and union types, narrows Nil unions, runs crystal spec behind a prompt, and formats the diff.
Atlas for Pandas: Terminal-Native AI Coding in 2026
Atlas is a terminal-native AI coding agent for Pandas. Vectorize df.apply, fix chained assignment under Copy-on-Write, and pin DataFrames with assert_frame_equal.
Atlas for Astro: Islands, Content Collections, and Zero JS by Default in 2026
Atlas is a terminal-native AI coding agent for Astro in 2026. It reads astro.config.mjs, src/pages, and content collection schemas, drops needless client:load directives, and runs astro check.
Atlas for Groovy: A Terminal-Native AI Coding Agent for Gradle, Spock, and Jenkins in 2026
Atlas is a terminal-native AI coding agent for Groovy in 2026. It reads build.gradle closures and Jenkinsfiles, writes Spock specs, runs ./gradlew test, and applies Spotless.
Atlas vs Base44: Terminal AI Coding Agents in 2026
Compare Atlas, the terminal-native AI coding agent, with Base44, the Wix-owned no-code app builder, for developers in 2026. Evaluate features, pricing, and workflow.
Atlas for WebAssembly: Terminal-Native AI Coding in 2026
Atlas is a terminal-native AI coding agent for WebAssembly. Audit wasm-bindgen exports, batch calls across the JS boundary, and run wasm-pack test --node in 2026.
Atlas vs OpenAI Codex CLI: Terminal AI Coding Agents in 2026
Comparing Atlas and OpenAI Codex CLI for terminal AI coding in 2026. Atlas offers a TUI, permission-gated tools, and BYO models, while OpenAI Codex CLI provides sandboxed execution and OpenAI model integration.
Atlas for Perl: A Terminal-Native AI Coding Agent for CPAN Distributions in 2026
Atlas is a terminal-native AI coding agent for Perl in 2026. It reads cpanfile deps and @EXPORT lists, writes Test2::V0 cases, runs prove -lr t/, and runs perltidy on the diff.