Model identity matters
Pin the exact checkpoint and revision used in production. Family names can contain base, instruct, reasoning, quantized and provider-specific variants with different behavior.
Kimi K2 Instruct is a very-large agentic Mixture-of-Experts model developed by Moonshot AI in the Kimi K2 family. It has 1T parameters with 32B/token active parameters, supports 128K tokens of context, accepts Text / code and produces Text / code. Its primary role is agentic intelligence, coding, tool use and general-purpose assistants.
OpenWeightModels separates the base checkpoint from its legal conditions and from each deployment implementation. This page is designed as an operational reference for people, search systems and AI agents—not as a single-number leaderboard.
Kimi K2 Instruct is a very-large agentic Mixture-of-Experts model developed by Moonshot AI in the Kimi K2 family. It has 1T parameters with 32B/token active parameters, supports 128K tokens of context, accepts Text / code and produces Text / code. Its primary role is agentic intelligence, coding, tool use and general-purpose assistants.
The model belongs to the Kimi K2 family and was released by Moonshot AI. Its documented input is Text / code and its output is Text / code. The published context envelope is 128K tokens, although a provider or runtime can expose a smaller operating limit.
For SEO and machine-readable retrieval, OpenWeightModels classifies it as a very-large agentic Mixture-of-Experts model whose primary application area is agentic intelligence, coding, tool use and general-purpose assistants. This definition describes the model itself; licensing eligibility and the practical serving stack are analyzed separately below.
Official Hugging Face model ↗Kimi K2 GitHub ↗Modified MIT license ↗Kimi K2 Instruct is useful to evaluate because it combines a specific architecture, license and operating envelope rather than simply adding another row to a model leaderboard.
Moonshot reports 15.5T pretraining tokens for Kimi K2 and emphasizes agentic intelligence, coding and tool use. The Instruct checkpoint is the direct-response post-trained variant rather than a later explicit “thinking” model.
From an infrastructure perspective, the key sizing facts are 1T total parameters, 32B/token active parameters and 128K tokens of context. These values should be read together: weight memory, active compute and KV-cache growth describe different resource constraints.
From a governance perspective, the checkpoint is distributed under Modified MIT License. OpenWeightModels records that independently from the fact that the weights are downloadable, because “open weight” is an access classification—not a universal statement about commercial, redistribution or derivative-work rights.
Pin the exact checkpoint and revision used in production. Family names can contain base, instruct, reasoning, quantized and provider-specific variants with different behavior.
Tool calling, structured output, safety layers, quotas and maximum context can be added or restricted by the serving layer. Store them as deployment records, not as unconditional properties of the weights.
Licenses, provider availability and runtime compatibility can change independently. Production reviews should use the official source links and a dated internal record.
Values describe the named checkpoint/family release unless a deployment implementation is explicitly named. Where the publisher does not document a value, OpenWeightModels avoids inventing one.
Kimi K2 Instruct uses sparse expert routing rather than activating its complete parameter pool for every token. The distinction between 1T total parameters and 32B/token active parameters is central to capacity planning: active parameters influence compute per token, while the complete expert set still affects storage, model loading, sharding and network topology.
This is why OpenWeightModels never maps the active-parameter figure directly to a dense-model hardware class. A sparse model can be computationally efficient per token and still require datacenter-class memory and interconnect to keep all experts available.
Publisher-documented architecture details for this checkpoint include the elements below. These details are more useful for deployment planning than a parameter count alone because attention layout, expert routing, modality encoders and context design can affect throughput and memory independently.
~1 trillion total parameters
32B active parameters
61 layers with one dense layer in the published architecture
384 routed experts, 8 selected per token plus shared expert
Multi-head latent attention (MLA)
128K context
Training provenance matters because two checkpoints with similar architecture can behave very differently after data selection, instruction tuning, reinforcement learning or domain specialization.
Moonshot reports 15.5T pretraining tokens for Kimi K2 and emphasizes agentic intelligence, coding and tool use. The Instruct checkpoint is the direct-response post-trained variant rather than a later explicit “thinking” model.
OpenWeightModels distinguishes facts explicitly published by the developer from inference based on model behavior. Dataset composition, cutoff dates and training compute are shown only when the publisher exposes them; absence of a number is not silently filled with an estimate.
Capability claims are treated as task-level evidence, not permission to deploy autonomously. Tool access, code execution and external actions always depend on the surrounding application.
Kimi K2 Instruct is relevant to agentic intelligence. Capability should be validated against the exact checkpoint, prompt format and runtime rather than inferred only from family branding or a benchmark headline.
Kimi K2 Instruct is relevant to coding. Capability should be validated against the exact checkpoint, prompt format and runtime rather than inferred only from family branding or a benchmark headline.
Kimi K2 Instruct is relevant to tool use. Capability should be validated against the exact checkpoint, prompt format and runtime rather than inferred only from family branding or a benchmark headline.
Kimi K2 Instruct is relevant to general-purpose assistants. Capability should be validated against the exact checkpoint, prompt format and runtime rather than inferred only from family branding or a benchmark headline.
Kimi K2 Instruct is relevant to evaluation and research. Capability should be validated against the exact checkpoint, prompt format and runtime rather than inferred only from family branding or a benchmark headline.
Kimi K2 Instruct is relevant to custom deployment. Capability should be validated against the exact checkpoint, prompt format and runtime rather than inferred only from family branding or a benchmark headline.
OpenWeightModels records benchmark evidence without collapsing heterogeneous evaluations into an overall ranking. Scores can change with checkpoint revision, prompt, sampling, scaffold, precision and evaluator version.
Where a publisher reports a useful, clearly attributable metric it is shown below. Otherwise the passport points back to the official evaluation tables instead of manufacturing a cross-model score.
| Evaluation | Metric / setup | Value | Qualification |
|---|---|---|---|
| Publisher evaluation | Model-card evidence | Not normalized | OpenWeightModels does not invent a single composite score for Kimi K2 Instruct. Use the official model card for checkpoint-specific benchmarks and conditions. |
Modified MIT License is the controlling license/terms classification recorded for this checkpoint. OpenWeightModels keeps the legal layer separate from technical availability.
If a commercial product/service exceeds either 100M monthly active users or $20M monthly revenue, the published modified license requires prominent “Kimi K2” display in the product/service user interface.
Permissive MIT base with additional scale-triggered branding condition. This summary supports comparison only; the linked official text remains authoritative.
| Question | Classification | Practical meaning |
|---|---|---|
| Commercial use | Allowed with special condition | Commercial eligibility follows the named license/terms; provider and jurisdictional conditions may add requirements. |
| Modification / fine-tuning | Allowed | Weight adaptation and derivative work rights are summarized from the official license type. |
| Redistribution | Allowed with MIT notice requirements | Redistribution is a separate question from the ability to download and run weights. |
| Hosted inference | License-dependent | Running a hosted service may count as distribution or trigger provider/model-specific terms; verify the official text for this checkpoint. |
| Open-weight classification | Yes | Weights are publicly obtainable; this label does not imply identical licensing freedom across models. |
Deployment is recorded as a set of implementations rather than one “self-hostable: yes” flag. A runtime can change context support, quantization, API shape, tool parsers, throughput and hardware requirements without changing the underlying model identity.
For Kimi K2 Instruct, the most relevant documented or established routes are listed below.
| Route | Type | Qualification |
|---|---|---|
| Transformers | Self-hosted | Official checkpoint integration. |
| vLLM | Serving | Officially documented large-model serving. |
| SGLang | Serving | Officially documented sparse-model serving. |
| KTransformers | Hybrid/local research | Optimized heterogeneous inference option. |
| TensorRT-LLM | NVIDIA serving | Optimized datacenter runtime. |
| Moonshot API | Managed API | Provider-hosted API path. |
Official checkpoint integration.
Officially documented large-model serving.
Officially documented sparse-model serving.
Optimized heterogeneous inference option.
Optimized datacenter runtime.
Provider-hosted API path.
The 1T total parameter pool is a major datacenter workload even with 32B active per token. Production serving requires expert/tensor parallelism, fast interconnect and typically reduced precision. FP8 is central to the published checkpoint ecosystem.
Real memory use includes model weights, KV cache, activations/buffers, multimodal encoders when applicable, framework overhead and batching. A published “fits on” statement is meaningful only together with precision, context, batch and host/GPU topology.
BF16/FP16 maximize fidelity but increase weight memory. FP8, INT8 and 4-bit variants can substantially lower memory, with support and quality depending on the quantization recipe and runtime.
128K tokens is a model/configuration reference, not a promise that every machine or provider can serve that context at practical latency. KV-cache growth often becomes the dominant long-context constraint.
Large dense models need tensor/pipeline parallelism; large MoE models add expert-routing and communication requirements. Smaller checkpoints can often avoid these operational complexities.
Base, instruct, reasoning, FP8, GGUF and provider-hosted variants can have different behavior, memory and provenance. Production systems should pin an exact model/revision rather than only the family name.
| Variant | Purpose | Precision / form | Status |
|---|---|---|---|
| Kimi-K2-Instruct | Agentic instruct | FP8/published format | Official |
| Kimi K2 family variants | Base/thinking derivatives | Varies | Official family |
Kimi K2 Instruct is most relevant when the application specifically values agentic intelligence, coding, tool use and general-purpose assistants. That should be balanced against its hardware class, context behavior, license and modality requirements.
A smaller model can be operationally superior when latency, privacy, device deployment or predictable cost matter more than peak benchmark capability. Conversely, a larger sparse model may justify its complexity when the workload benefits from higher capacity, sophisticated reasoning or agent behavior.
The selection decision should therefore compare at least five dimensions: required task quality, data/control requirements, legal eligibility, serving cost and ecosystem/runtime support. OpenWeightModels exposes these dimensions separately so a model is not selected on benchmark reputation alone.
A high-quality passport gives limitations the same visibility as capabilities. These are model- and deployment-selection notes, not generic disclaimers.
32B active does not imply a 32B storage footprint.
Autonomous tool use requires sandboxing and permissions.
The Modified MIT license adds a branding condition for very large commercial services.
Long context and agent traces can create high latency/token costs.
Last full review: 29 September 2026. Publisher model cards, repositories and license texts are preferred. Runtime claims are attached to the relevant runtime/provider rather than inferred from the base checkpoint.
Where documentation conflicts or a field is ambiguous, the passport uses the more conservative interpretation and explains the discrepancy instead of silently selecting the largest number.
Material changes to license, model revision, runtime support or provider limits should update both the field and this history.
Gold-standard Passport v2.0 created with SEO/GEO definition, architecture, training, capability, evaluation, license, deployment, hardware, variants, limitations and source review.
Kimi K2 Instruct is a very-large agentic Mixture-of-Experts model developed by Moonshot AI in the Kimi K2 family. It has 1T parameters with 32B/token active parameters, supports 128K tokens of context, accepts Text / code and produces Text / code. Its primary role is agentic intelligence, coding, tool use and general-purpose assistants.
OpenWeightModels classifies it as open-weight because weights are publicly available. The exact legal classification depends on Modified MIT License; weight availability should not be used as a substitute for reading those terms.
Our license classification is Allowed with special condition. Review the official license and any separate use policy, provider terms and jurisdictional rules before production use.
The documented reference in this passport is 128K tokens. A runtime/provider may expose a different maximum or a smaller recommended operating range.
Yes, the open weights enable independent deployment where the license permits it. Practical feasibility depends on 1T of weights, precision, context length and the runtime routes listed above.