LLM ReferenceLLM Reference

K-EXAONE 236B-A23B vs Kimi K2.6

K-EXAONE 236B-A23B (2025) and Kimi K2.6 (2026) are agentic coding models from LG Research and Moonshot AI. K-EXAONE 236B-A23B ships a 256k-token context window, while Kimi K2.6 ships a 262K-token context window. On Google-Proof Q&A, Kimi K2.6 leads by 12.2 pts. This comparison covers specs, pricing, capabilities, benchmarks, provider availability, and production fit. It focuses on practical selection signals rather than broad model-family marketing.

Kimi K2.6 is safer overall; choose K-EXAONE 236B-A23B when provider fit matters.

Decision scorecard

Local evidence first
SignalK-EXAONE 236B-A23BKimi K2.6
Decision fitLong contextCoding, RAG, and Agents
Context window256k262K
Cheapest output-$3.5/1M tokens
Provider routes0 tracked5 tracked
Shared benchmarks1 rowsGoogle-Proof Q&A leader

Decision tradeoffs

Choose K-EXAONE 236B-A23B when...
  • Local decision data tags K-EXAONE 236B-A23B for Long context.
Choose Kimi K2.6 when...
  • Kimi K2.6 leads the largest shared benchmark signal on Google-Proof Q&A by 12.2 points.
  • Kimi K2.6 has the larger context window for long prompts, retrieval packs, or transcript analysis.
  • Kimi K2.6 has broader tracked provider coverage for fallback and procurement flexibility.
  • Kimi K2.6 uniquely exposes Vision, Multimodal, and Reasoning in local model data.
  • Local decision data tags Kimi K2.6 for Coding, RAG, and Agents.

Monthly cost at traffic

Estimate token spend from the cheapest tracked input and output prices on this page.

K-EXAONE 236B-A23B

Unavailable

No complete token price in local provider data

Kimi K2.6

$1,475

Cheapest tracked route: OpenRouter

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

Switch friction

K-EXAONE 236B-A23B -> Kimi K2.6
  • No overlapping tracked provider route is sourced for K-EXAONE 236B-A23B and Kimi K2.6; plan for SDK, billing, or endpoint changes.
  • Kimi K2.6 adds Vision, Multimodal, and Reasoning in local capability data.
Kimi K2.6 -> K-EXAONE 236B-A23B
  • No overlapping tracked provider route is sourced for Kimi K2.6 and K-EXAONE 236B-A23B; plan for SDK, billing, or endpoint changes.
  • Check replacement coverage for Vision, Multimodal, and Reasoning before moving production traffic.

Specs

Specification
Released2025-12-312026-04-20
Context window256k262K
Parameters236B1T
ArchitectureMoEMixture of Experts (MoE)
LicenseOpen SourceOpen Source
Knowledge cutoff--

Pricing and availability

Pricing attributeK-EXAONE 236B-A23BKimi K2.6
Input price-$0.75/1M tokens
Output price-$3.5/1M tokens
Providers-

Capabilities

CapabilityK-EXAONE 236B-A23BKimi K2.6
VisionNoYes
MultimodalNoYes
ReasoningNoYes
Function callingNoYes
Tool useNoYes
Structured outputsNoNo
Code executionNoNo

Benchmarks

BenchmarkK-EXAONE 236B-A23BKimi K2.6
Google-Proof Q&A78.390.5

Deep dive

On shared benchmark coverage, Google-Proof Q&A has K-EXAONE 236B-A23B at 78.3 and Kimi K2.6 at 90.5, with Kimi K2.6 ahead by 12.2 points. The largest visible gap is 12.2 points on Google-Proof Q&A, which matters most when that benchmark mirrors your workload. Treat isolated benchmark wins as directional, because provider routing, prompt style, and tool access can move real application results.

The capability footprint differs most on vision: Kimi K2.6, multimodal input: Kimi K2.6, reasoning mode: Kimi K2.6, function calling: Kimi K2.6, and tool use: Kimi K2.6. 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: K-EXAONE 236B-A23B has no token price sourced yet and Kimi K2.6 has $0.75/1M input tokens. Provider availability is 0 tracked routes versus 5. Treat unknown pricing as an integration gap, then verify the route you will actually call before estimating production spend.

Choose K-EXAONE 236B-A23B when provider fit are central to the workload. Choose Kimi K2.6 when coding workflow support, larger context windows, 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.

FAQ

Which has a larger context window, K-EXAONE 236B-A23B or Kimi K2.6?

Kimi K2.6 supports 262K tokens, while K-EXAONE 236B-A23B supports 256k tokens. That gap matters most for long documents, large codebases, retrieval-heavy agents, and conversations where earlier context must remain visible.

Is K-EXAONE 236B-A23B or Kimi K2.6 open source?

K-EXAONE 236B-A23B is listed under Open Source. Kimi K2.6 is listed under Open Source. 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 vision, K-EXAONE 236B-A23B or Kimi K2.6?

Kimi K2.6 has the clearer documented vision signal in this comparison. If vision is mission-critical, validate it against the provider endpoint because model-level support and API-level exposure can differ. Use this as a quick comparison signal, then confirm the provider-specific limits before committing to production.

Which is better for multimodal input, K-EXAONE 236B-A23B or Kimi K2.6?

Kimi K2.6 has the clearer documented multimodal input signal in this comparison. If multimodal input is mission-critical, validate it against the provider endpoint because model-level support and API-level exposure can differ.

Which is better for reasoning mode, K-EXAONE 236B-A23B or Kimi K2.6?

Kimi K2.6 has the clearer documented reasoning mode signal in this comparison. If reasoning mode is mission-critical, validate it against the provider endpoint because model-level support and API-level exposure can differ.

Where can I run K-EXAONE 236B-A23B and Kimi K2.6?

K-EXAONE 236B-A23B is available on the tracked providers still being sourced. Kimi K2.6 is available on NVIDIA NIM, Moonshot AI Kimi, Fireworks AI, OpenRouter, and Microsoft Foundry. Provider coverage can affect latency, region availability, compliance posture, and fallback options.

Continue comparing

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