Kimi K3.1 Pro

Kimi K3.1 Pro has 44 source-displayable benchmark rows, but it does not qualify for a public overall rank. The available rows remain visible by category without being converted into a site-wide score. Missing evidence stays blank instead of being estimated from an earlier model.

Kimi K3.1 Pro has source-displayable benchmark coverage for knowledge and understanding, but the public category table does not assign it a rank there. The individual rows remain available for inspection. A missing category position means the evidence threshold was not met; it does not convert the model's unmeasured work into a zero.

Kimi K3.1 Pro has source-displayable benchmark coverage for coding and programming, but the public category table does not assign it a rank there. The individual rows remain available for inspection. A missing category position means the evidence threshold was not met; it does not convert the model's unmeasured work into a zero.

Kimi K3.1 Pro has source-displayable benchmark coverage for agentic tool use and computer tasks, but the public category table does not assign it a rank there. The individual rows remain available for inspection. A missing category position means the evidence threshold was not met; it does not convert the model's unmeasured work into a zero.

Kimi K3.1 Pro ranks #1 out of 56 eligible models for multimodal and grounded tasks, with a public category score of 98/100. That places it in the current top ten for this category. Check the underlying rows before treating the aggregate as a workload guarantee.

No. Kimi K3.1 Pro currently has 57 source-displayable rows. The profile exposes published, non-generated evidence and leaves missing categories blank until an exact evaluation is available. Coverage describes how much was measured; it is not a penalty added to an individual benchmark result.

Kimi K3.1 Pro has a reported context window of 1.05M in the exact-model catalog record. The value stays visible, but the profile marks its source link as unavailable instead of presenting it as directly documented. Maximum output length remains separate because providers often publish a different limit.