Cached at:
04/21/26, 04:48 AM
# Kimi Vendor Verifier
Source: [https://www.kimi.com/blog/kimi-vendor-verifier](https://www.kimi.com/blog/kimi-vendor-verifier)
[Research](https://www.kimi.com/blog/)## Rebuilding the "Chain of Trust": Kimi Vendor Verifier[](https://github.com/MoonshotAI/Kimi-Vendor-Verifier)[](https://www.kimi.com/blog/kimi-vendor-verifier#rebuilding-the-chain-of-trust-kimi-vendor-verifier)
Alongside the release of the Kimi K2\.6 model, we are open\-sourcing the Kimi Vendor Verifier \(KVV\) project, designed to help users of open\-source models verify the accuracy of their inference implementations\.
Not as an afterthought, but because we learned the hard way that open\-sourcing a model is only half the battle\. The other half is ensuring it runs correctly everywhere else\.
## Official Evaluation Results[](https://www.kimi.com/blog/kimi-vendor-verifier#official-evaluation-results)
You can[click here](https://statics.moonshot.cn/k2vv/kimi-k2.6_t0.6_m8192_nothink.zip)to access the Kimi API K2VV evaluation results for calculating the F1 score\.
## Why We Built KVV[](https://www.kimi.com/blog/kimi-vendor-verifier#why-we-built-kvv)
**From Isolated Incidents to Systemic Issues**
Since the release of K2 Thinking, we have received frequent feedback from the community regarding anomalies in benchmark scores\. Our investigation confirmed that a significant portion of these cases stemmed from the misuse of Decoding parameters\. To mitigate this immediately, we built our first line of defense at the API level: enforcing Temperature=1\.0 and TopP=0\.95 in Thinking mode, with mandatory validation that thinking content is correctly passed back\.
However, more subtle anomalies soon triggered our alarm\. In a specific evaluation on[LiveBenchmark](https://www.reddit.com/r/LocalLLaMA/comments/1osglws/kimi_k2_thinking_scores_lower_than_gemini_25/?rdt=41412), we observed a stark contrast between third\-party API and official API\. After extensive testing of various infrastructure providers, we found this difference is widespread\.
This exposed a deeper problem in the open\-source model ecosystem: The more open the weights are, and the more diverse the deployment channels become, the less controllable the quality becomes\.
If users cannot distinguish between "model capability defects" and "engineering implementation deviations," trust in the open\-source ecosystem will inevitably collapse\.
## Our Solution[](https://www.kimi.com/blog/kimi-vendor-verifier#our-solution)
**Six Critical Benchmarks**\(selected to expose specific infra failures\):
1. [Pre\-Verification](https://github.com/MoonshotAI/Kimi-Vendor-Verifier?tab=readme-ov-file#3-pre-flight-check): Validates that API parameter constraints \(temperature, top\_p, etc\.\) are correctly enforced\. All tests must pass before proceeding to benchmark evaluation\.
2. [OCRBench](https://github.com/MoonshotAI/Kimi-Vendor-Verifier?tab=readme-ov-file#ocrbench-quick-validation): 5 minutes smoke test for multimodal pipelines\.
3. [MMMU Pro](https://github.com/MoonshotAI/Kimi-Vendor-Verifier?tab=readme-ov-file#mmmu-pro-vision): Verify Vision input preprocessing by testing diverse visual inputs\.
4. [AIME2025](https://github.com/MoonshotAI/Kimi-Vendor-Verifier?tab=readme-ov-file#aime-2025): Long\-output stress test\. Catches KV cache bugs and quantization degradation that short benchmarks hide\.
5. [K2VV ToolCall](https://github.com/MoonshotAI/K2-Vendor-Verifier): Measures trigger consistency \(F1\) and JSON Schema accuracy\. Tool errors compound in agents; we catch them early\.
6. SWE\-Bench: Full agentic coding test\. \(Not open sourced due to dependency of sandbox\)
**Upstream Fix**: We embed with vLLM/SGLang/KTransformers communities to fix root causes, not just detect symptoms\.
**Pre\-Release Validation**: Rather than waiting for post\-deployment complaints, we provide early access to test models\. This lets infrastructure providers validate their stacks before users encounter issues\.
**Continuous Benchmarking**: We will maintain a public leaderboard of vendor results\. This transparency encourages vendors to prioritize accuracy\.
## Testing Cost Estimation[](https://www.kimi.com/blog/kimi-vendor-verifier#testing-cost-estimation)
We completed full evaluation workflow validation on Two NVIDIA H20 8\-GPU servers, with sequential execution taking approximately 15 hours\. To improve evaluation efficiency, scripts have been optimized for long\-running inference scenarios, including streaming inference, automatic retry, and checkpoint resumption mechanisms\.
## An Open Invitation[](https://www.kimi.com/blog/kimi-vendor-verifier#an-open-invitation)
**Weights are open\. The knowledge to run them correctly must be too\.**
We are expanding vendor coverage and seeking lighter agentic tests\.**Contact Us:[contact\-kvv@kimi\.com](mailto:
[email protected])**