Skip to main content

1. Model Introduction

Kimi-K2.6 is an open-source, native multimodal agentic model by Moonshot AI, delivering industry-leading coding, long-horizon execution, and agent swarm capabilities. It matches or surpasses GPT-5.4, Claude Opus 4.6, and Gemini 3.1 Pro across key benchmarks. Key Features:
  • Long-Horizon Coding: Excels at complex, end-to-end coding tasks with 13+ hours of continuous execution and 4,000+ lines of code modification, generalizing across languages (Rust, Go, Python) and tasks (frontend, devops, performance optimization).
  • Coding-Driven Design: Transforms prompts and visual inputs into production-ready interfaces with motion-rich elements including WebGL shaders, GSAP + Framer Motion, and Three.js 3D.
  • Agent Swarms Elevated: Scales to 300 parallel sub-agents executing 4,000 coordinated steps per run. One prompt, 100+ files.
  • Proactive Agents: Powers OpenClaw, Hermes Agent, and other autonomous frameworks for 5-day continuous operation.
  • Native Multimodality: Pre-trained on vision–language tokens with MoonViT (400M parameters) for visual understanding, cross-modal reasoning, and agentic tool use grounded in visual inputs.
Benchmarks (Open-Source SOTA):
BenchmarkScore
HLE w/ tools54.0
SWE-Bench Pro58.6
SWE-bench Multilingual76.7
BrowseComp83.2
Toolathlon50.0
AIME 202696.4
GPQA-Diamond90.5
LiveCodeBench89.6
Recommended Generation Parameters:
  • Thinking Mode: temperature=1.0, top_p=0.95
  • Instant Mode: temperature=0.6, top_p=0.95
Available Models: License: Modified MIT for the native checkpoint. The NVIDIA NVFP4 checkpoint is governed by the NVIDIA Open Model License. For details, see official documentation and tech blog.

2. SGLang Installation

Refer to the official SGLang installation guide.

3. Model Deployment

3.1 Basic Configuration

Interactive Command Generator: Use the configuration selector below to automatically generate the appropriate deployment command for your hardware platform, deployment strategy, and capabilities.

3.2 Configuration Tips

  • Memory: Requires GPUs with ≥140GB each. The native INT4 checkpoint supports H200 (8×, TP=8), B300 (8×, TP=8), GB300 (4×, TP=4), MI300X/MI325X (4×, TP=4), and MI350X/MI355X (4×, TP=4). Use --context-length 128000 to conserve memory.
  • NVFP4: Use nvidia/Kimi-K2.6-NVFP4 with --quantization modelopt_fp4 on NVIDIA Blackwell. Use tp=8 on B300 and tp=4 on GB300.
  • AMD GPU TP Constraint: On AMD GPUs, TP must be ≤ 4 (not 8). Kimi-K2.6 has 64 attention heads; the AITER MLA kernel requires heads_per_gpu % 16 == 0. With TP=4, each GPU gets 16 heads (valid). With TP=8, each GPU gets 8 heads (invalid).
  • AMD Docker Image: Use lmsysorg/sglang:v0.5.9-rocm700-mi35x for MI350X/MI355X and lmsysorg/sglang:v0.5.9-rocm700-mi30x for MI300X/MI325X.
  • DP Attention: Enable with --dp <N> --enable-dp-attention for production throughput. A common choice is to set --dp equal to --tp, but this is not required.
  • Reasoning Parser: Add --reasoning-parser kimi_k2 to separate thinking and content in model outputs.
  • Tool Call Parser: Add --tool-call-parser kimi_k2 for structured tool calls.
  • AMD FP8 KV Cache: On AMD platforms the generator adds --kv-cache-dtype fp8_e4m3 by default and sets --mem-fraction-static 0.8 to fit the INT4 weights plus KV cache. FP8 KV cache trades a small amount of accuracy for memory; omit the flag if you observe accuracy regressions on your workload.

4. Model Invocation

4.1 Basic Usage

See Basic API Usage.

4.2 Advanced Usage

4.2.1 Multimodal (Vision + Text) Input

Kimi-K2.6 supports native multimodal input with images:
Example
Output Example:
Output

4.2.2 Reasoning Output

Kimi-K2.6 supports both thinking mode (default) and instant mode. Thinking Mode (default) — reasoning content is automatically separated:
Example
Instant Mode (thinking off) — disable thinking for faster responses:
Example
Output Example:
Output

4.2.3 Tool Calling

Kimi-K2.6 supports tool calling capabilities for agentic tasks:
Example
Output Example:
Output
Handling Tool Call Results:
Example
Output Example:
Output

4.2.4 Multimodal + Tool Calling (Agentic Vision)

Combine vision understanding with tool calling for advanced agentic tasks:
Example
Output Example:
Output

4.2.5 Speculative Decoding

NVIDIA Deploy Kimi-K2.6 with the following command (H200/B300, all features enabled):
Command
Deploy Kimi-K2.6-NVFP4 with the following command (B300, all features enabled):
Command
For GB300, use --tp 4.

5. Benchmark

5.1 Accuracy Benchmark

Test Environment:
  • Hardware: 8× NVIDIA H200
  • Model: moonshotai/Kimi-K2.6 (INT4)
  • Tensor Parallelism: 8
  • SGLang version: 0.5.9
  • Reasoning Parser: kimi_k2
  • Tool Call Parser: kimi_k2

NVIDIA NVFP4 Accuracy Reference

NVIDIA reports the following accuracy results for nvidia/Kimi-K2.6-NVFP4 compared with the native INT4 baseline, using temperature=1.0, top_p=0.95, and max tokens 128,000:
PrecisionGPQA DiamondSciCodeτ²-Bench TelecomMMMU ProAA-LCRIFBench
Baseline (INT4)90.952.698.275.671.073.9
NVFP490.454.498.076.571.873.9

5.1.1 K2-Vendor-Verifier (Tool Calling)

  • Dataset: K2-Vendor-Verifier tool-calls dataset (2,000 requests)
  • Evaluation Tool: K2-Vendor-Verifier tool_calls_eval.py
  • Settings: temperature=1.0, max_tokens=64,000, concurrency=256
Evaluation Command:
Command
Results:
MetricValue
Success Rate99.95% (1999/2000)
Tool Call Triggered970
Tool Call Valid89.6% (869/970)
Tool Call Invalid (schema error)10.4% (101/970)

5.1.2 AIME 2025

  • Dataset: AIME 2025 (30 problems)
  • Evaluation Tool: NVIDIA NeMo-Skills
  • Prompt: eval/matharena/aime (MathArena format with \boxed{} answers)
  • Settings: temperature=1.0, top_p=0.95, max_tokens=131,072, 32 seeds
Evaluation Command:
Command
Results:
Evaluation ModeAccuracy
pass@1 (avg-of-32)98.9% (29.7/30)
majority@32100.0% (30/30)
pass@32100.0%
22 out of 32 seeds achieved a perfect score of 30/30. The remaining 10 seeds each missed exactly 1 problem (29/30).

5.1.3 GPQA Diamond

  • Dataset: GPQA Diamond (198 questions, 4-choice multiple choice)
  • Evaluation Tool: Inspect AI with inspect_evals/gpqa_diamond
  • Settings: temperature=1.0, top_p=0.95, max_tokens=131,072, 4 epochs, cot=True
Evaluation Command:
Command
Results (partial — 553/792 samples across 4 epochs):
Evaluation ModeAccuracy
pass@1 (avg across epochs)96.9%
EpochAccuracy
196.4% (160/166)
296.9% (156/161)
396.9% (155/160)
498.5% (65/66)

5.1.4 OCRBench

  • Dataset: OCRBench (1,000 questions with images)
  • Evaluation Tool: Kimi-Vendor-Verifier (inspect-ai based)
  • Settings: max_tokens=4,096, thinking mode enabled (opensource)
Evaluation Command:
Command
Results:
Evaluation ModeAccuracy
pass@190.8%

5.1.5 MMMU Pro Vision

  • Dataset: MMMU Pro standard 10-option subset (1,730 questions with images)
  • Evaluation Tool: Kimi-Vendor-Verifier (inspect-ai based)
  • Settings: max_tokens=32,768, thinking mode (default), max_connections=256
Important: Kimi-K2.6 is a reasoning model. Setting max_tokens too low (e.g., 4096) causes the thinking process to consume the entire token budget, leaving no tokens for the final answer. Use max_tokens=32768 or higher.
Evaluation Command:
Command
Results (1,481/1,730 samples completed):
Evaluation ModeAccuracy
pass@182.2%

5.2 Speed Benchmark

Test Environment:
  • Hardware: NVIDIA H200 GPU (8x)
  • Model: Kimi-K2.6
  • Tensor Parallelism: 8
  • SGLang Version: 0.5.9
Kimi-K2.6 shares the same architecture as K2.5. Speed benchmarks are expected to be equivalent. The results below are measured with K2.5 and serve as a reference.
We use SGLang’s built-in benchmarking tool with the random dataset for standardized performance evaluation.

5.2.1 Latency Benchmark

  • Model Deployment:
Command
Scenario 1: Chat (1K/1K)
  • Low Concurrency
Command
Output
  • Medium Concurrency (Balanced)
Command
Output
  • High Concurrency (Throughput-Optimized)
Command
Output
Scenario 2: Reasoning (1K/8K)
  • Low Concurrency
Command
Output
  • Medium Concurrency
Command
Output
Scenario 3: Summarization (8K/1K)
  • Low Concurrency
Command
Output
  • Medium Concurrency
Command
Output
  • High Concurrency
Command
Output

5.3 Speed Benchmark (AMD MI350X)

Test Environment:
  • Hardware: AMD Instinct MI350X GPU (4x)
  • Model: Kimi-K2.6 (INT4)
  • Tensor Parallelism: 4
  • SGLang Version: 0.5.9
  • Docker Image: lmsysorg/sglang:v0.5.9-rocm700-mi35x
  • ROCm: 7.0
We use SGLang’s built-in benchmarking tool with the random dataset for standardized performance evaluation.
AMD GPU TP Constraint: Kimi-K2.6 requires TP ≤ 4 on AMD GPUs. The model has 64 attention heads, and the AITER MLA kernel requires heads_per_gpu % 16 == 0. With TP=4, each GPU gets 16 heads (valid). With TP=8, each GPU gets 8 heads (invalid).

5.3.1 Latency Benchmark

  • Model Deployment:
Command
  • Benchmark Command:
Command
  • Results:
Output
  • Medium Concurrency (Balanced)
Command
Output