Kimi K2.5 from Moonshot AI is the January 2026 generation that reset the Kimi price floor for reasoning: $0.60 per Mtok input and $3.00 per Mtok output, with a full 256K tokens (262,144) context and a matching 262,144 output cap. Inside Atlas it is the sensible default before you consider the K2.6 and K2.7 tiers, because it is the cheapest current-generation Kimi reasoning model and it descends from the 1T-total / 32B-active K2 MoE lineage that was purpose-trained for agentic tool calling, which is exactly Atlas's execution model.
Why is Kimi K2.5 a good default model for Atlas?
Kimi K2.5 is the cheapest current-generation Kimi reasoning model at $0.60 per Mtok input, and it descends from the 1T-total / 32B-active K2 MoE lineage that Moonshot AI purpose-trained for agentic tool calling. Agentic tool calling is exactly Atlas's execution model.
Atlas runs on tool calls. Atlas searches code with hybrid semantic and keyword retrieval fused by reciprocal rank fusion, it connects to Model Context Protocol servers and exposes their tools to the agent, and every tool call is permission-gated against allow, ask, and deny rules before it runs. A model that is weak at deciding which tool to call next will burn context flailing, regardless of how good its prose is. The K2 MoE lineage behind Kimi K2.5 was trained for that decision loop specifically, which is why it holds up in Atlas at a $0.60 per Mtok input price that would normally imply a weaker tier.
How does Kimi K2.5 pricing compare to GLM-4.7 and GLM-5.1?
Kimi K2.5 charges $0.60 per Mtok input, matching GLM-4.7's $0.60 while carrying a larger 262,144 token window against GLM-4.7's 204,800. Kimi K2.5 also lands far under GLM-5.1's $1.40 per Mtok input, which makes it a strong entry price for reasoning.
Input price is where long-context agent work gets decided, because Atlas is constantly pushing retrieved code into the prompt. On that axis Kimi K2.5 is competitive with anything in its class: $0.60 per Mtok input for a reasoning model with a 262,144 token window. Output is the softer side of the deal at $3.00 per Mtok, which is more than GLM-4.7 but well inside normal for a current-generation reasoning model. If your Atlas sessions are read-heavy, which most code exploration sessions are, Kimi K2.5 is priced where you want it.
Does Kimi K2.5 truncate large refactors?
No. Kimi K2.5 has an output cap that equals its context window at 262,144 tokens, so it will never truncate a large refactor mid-write. The 256K tokens (262,144) ceiling applies to both sides of the exchange.
Output truncation is a real cost in agentic coding, not a theoretical one. A model that stops writing halfway through a multi-file diff has burned the whole turn, and the retry costs full price again. Kimi K2.5 removes that failure mode by matching output to context at 262,144 tokens. Atlas pairs this with real safety on the write side: Atlas computes a unified diff for every file edit and surfaces it for approval before writing, and Atlas snapshots file changes as git patches so edits can be diffed and rolled back. Big diffs from Kimi K2.5 stay reviewable and reversible.
Is Kimi K2.6 worth the upgrade over Kimi K2.5?
Kimi K2.6 supersedes Kimi K2.5 on coding benchmarks for $0.35 more per Mtok input, taking you from $0.60 to $0.95. If your Atlas workload is heavy on code generation rather than exploration, that $0.35 delta is usually worth paying.
Kimi K2.5 is mainly a cost play now. That is not a criticism, it is a positioning statement: the model is current-generation, it is cheap, and it is the right pick when your budget is the binding constraint or when Atlas is doing a lot of reading relative to writing. When code quality is the binding constraint instead, K2.6 is the better buy. The honest framing for a 2026 developer choosing between them is that Kimi K2.5 sets the floor, and every step up the Kimi ladder is a deliberate purchase of coding quality at a known input-price increment.
Can you run Kimi K2.5 locally instead of calling Moonshot?
Yes. There is an `ollama pull kimi-k2.5` route if you would rather keep the weights local, and running `atlas device` first tells you whether Ollama and a GPU are detected on the machine. Local serving also sidesteps the China data-residency question entirely.
Kimi K2.5 is served from Moonshot in China, so data residency is a real consideration for regulated codebases. Some teams cannot send source to that jurisdiction at all, and no price makes that acceptable. Atlas has a genuine answer here: Atlas can build its code index with local Ollama embeddings, keeping code off third-party servers, and the same Ollama path can host Kimi K2.5 itself. Start with `atlas device` to confirm the hardware story, then `ollama pull kimi-k2.5`. If the local route is not viable, treat residency as a hard filter rather than something to negotiate on price.
Setup
- 01Export MOONSHOT_API_KEY, or run `atlas login` and select Moonshot AI.
- 02Run `atlas models moonshotai` and confirm that `kimi-k2.5` resolves from the registry.
- 03Set "model": "moonshotai/kimi-k2.5" in atlas.json.
- 04For a local route instead, run `atlas device` first to see whether Ollama and a GPU are detected on the machine.
- 05If local serving is viable, run `ollama pull kimi-k2.5` to keep the weights on your own hardware.
Frequently asked questions
- how much does kimi k2.5 cost per million tokens
- Kimi K2.5 costs $0.60 per Mtok input and $3.00 per Mtok output, which makes it the cheapest current-generation Kimi reasoning model.
- what is the kimi k2.5 context window
- Kimi K2.5 has a 256K tokens (262,144) context window, and its output cap equals the window at 262,144 tokens.
- how do I use kimi k2.5 with atlas
- Export MOONSHOT_API_KEY, run `atlas models moonshotai` to confirm `kimi-k2.5` resolves, then set "model": "moonshotai/kimi-k2.5" in atlas.json.
- kimi k2.5 vs kimi k2.6 for coding
- Kimi K2.6 supersedes Kimi K2.5 on coding benchmarks for $0.35 more per Mtok input, taking you from $0.60 to $0.95. K2.5 is the cost play.
- can I run kimi k2.5 locally with ollama
- Yes. Run `atlas device` to check whether Ollama and a GPU are detected, then `ollama pull kimi-k2.5` to keep the weights on your own hardware.
- is kimi k2.5 hosted in china
- Yes. Kimi K2.5 is served from Moonshot in China, so data residency is a real consideration for regulated codebases.
- is kimi k2.5 good at agentic tool calling
- Kimi K2.5 descends from the 1T-total / 32B-active K2 MoE lineage that was purpose-trained for agentic tool calling, which matches how Atlas executes work.
Try Atlas in your terminal
The terminal-native AI coding agent. Free core, single binary.
Install AtlasRelated guides
Atlas for Clojure: A Terminal-Native AI Coding Agent for deps.edn and Kaocha in 2026
Atlas is a terminal-native AI coding agent for Clojure in 2026. It reads deps.edn aliases and namespace requires, runs clojure -M:test with Kaocha, and applies cljfmt.
Atlas for Erlang in 2026
Atlas is a terminal-native AI coding agent for Erlang/OTP in 2026. Run it in an app with a rebar.config, map supervisors and gen_server modules, review every diff.
Atlas for C in 2026
Atlas is a terminal-native AI coding agent for C in 2026. Run it in a project with a Makefile, have it find memory leaks or add Unity tests, and review the diff.
Atlas for Flutter in 2026
Discover Atlas for Flutter in 2026. This terminal-native AI coding agent helps Flutter developers build apps faster and safer, integrating with widgets, state, and the Dart toolchain.
Atlas vs. Goose: Choosing Your AI Coding Agent in 2026
Compare Atlas and Goose for 2026. Atlas offers terminal-native TUI and code-specialized features. Goose provides shareable Recipes and 70+ MCP extensions for general agentic workflows.
Atlas vs Magic.dev: Terminal AI Coding Agents in 2026
Compare Atlas, the terminal-native AI coding agent with permission-gated tools and diff review, against Magic.dev's research claims of 100 million token context models in 2026.
Migrate a Deprecated API Across Every Callsite with Atlas (2026 Workflow)
How to migrate a deprecated API across every callsite with Atlas in 2026: the lsp tool's findReferences enumerates callers, todowrite tracks them, apply_patch migrates each one.
Atlas for Node.js in 2026
Node.js developers in 2026 can adopt Atlas, the terminal-native AI coding agent, for secure, efficient development. Leverage local embeddings, AST indexing, and robust safety features.