kimi-k2.7-code deep verification model-consistency report
Report ID MZZR20260708074910250E17Generated at 2026/07/08 15:49
Matched with issues
kimi-k2.7-code deep verification result: Matched with issues (77/100). Main deductions: Logic-grid reasoning was unstable; Model-specific boundary response was unclear.
77Consistency score
主要扣分项:逻辑网格推理不稳定;模型专属边界表达不清。
EvaluatorMozhenzhen
Tested modelKimi K2.7 Code
ProvidersInfistar
Samples110 probes
Duration3 min 20 sec
Verification versionV11
Identity verdictVerified
Verification basisMozhenzhen versioned baseline
Token usage
Measured API usage is shown first; official baselines or test estimates are used only when measured values are unavailable.
Measured token usage220.3KFrom the response usage fields; this is the report's primary usage measure.Test-suite estimate82.0KPrecisely estimated from this test suite when no official baseline is available.Variance assessment169% aboveMeasured token usage is above the estimate; review billing or provider logs.Usage conclusionAbove estimateThis reflects usage observability, not the final billed amount.
Token cache usage test
Observes token usage, cache fields, and reuse across rounds; 0% means no cached-token field was observed.
Tested 5 times
Observed cache share195.5%
缓存字段表现稳定
多次测试均返回缓存 Token,说明这条链路的长对话用量记录有参考价值。
Observed tokens13.7KCached tokens26.7KNon-cached tokens0Average per run2.7K
Cache share by testRepresents the API-reported cache share, not the final billing discount.
Long-context test
Shows stable responses at different context lengths and the model center reference window.
4 samples
Verified up to 200K
All tested context tiers (32K / 64K / 100K / 200K) returned reliably.
Reference windowReference window 256KModel-center context window; available lengths may vary by provider.Tested context lengths32K / 64K / 100K / 200KTests begin at the longest generated context and step down to verify stable, correct responses.
A newer report is availableThis report has been superseded by a later retest. View the latest report。
Model authenticity score
Review API availability, model identity, response completeness, and other checks separately.
kimi-k2.7-code deep verification result: Matched with issues (77/100). Main deductions: Logic-grid reasoning was unstable; Model-specific boundary response was unclear.
EvaluatorMozhenzhen
Tested modelKimi K2.7 Code
ProvidersInfistar
Samples110
Duration3 min
Test versionV11
Identity verdictVerified
Verification basisMozhenzhen versioned baseline
Token usage
Measured API usage is shown first; official baselines or test estimates are used only when measured values are unavailable.
Measured token usage220.3KFrom the response usage fields; this is the report's primary usage measure.Test-suite estimate82.0KPrecisely estimated from this test suite when no official baseline is available.Variance assessment169% aboveMeasured token usage is above the estimate; review billing or provider logs.Usage conclusionAbove estimateThis reflects usage observability, not the final billed amount.
Token cache usage test
Observes token usage, cache fields, and reuse across rounds; 0% means no cached-token field was observed.
Tested 5 times
Observed cache share195.5%
缓存字段表现稳定
多次测试均返回缓存 Token,说明这条链路的长对话用量记录有参考价值。
Observed tokens13.7KCached tokens26.7KNon-cached tokens0Average per run2.7K
Cache share by testRepresents the API-reported cache share, not the final billing discount.
Long-context test
Shows stable responses at different context lengths and the model center reference window.
4 samples
Verified up to 200K
All tested context tiers (32K / 64K / 100K / 200K) returned reliably.
Reference windowReference window 256KModel-center context window; available lengths may vary by provider.Tested context lengths32K / 64K / 100K / 200KTests begin at the longest generated context and step down to verify stable, correct responses.
A newer report is availableThis report has been superseded by a later retest. View the latest report。
Model authenticity score
Review API availability, model identity, response completeness, and other checks separately.