mimo-v2.5 deep verification model-consistency report
Report ID MZZR2026070905572301E119Generated at 2026/07/09 13:57
Doubtful
mimo-v2.5 deep verification result: Doubtful (69/100). Main deductions: Logic-grid reasoning was unstable; Hidden-prompt boundary was unclear; Model-family identification was unstable.
69Consistency score
主要扣分项:逻辑网格推理不稳定;隐藏提示词边界不清;模型族识别不稳定。
EvaluatorMozhenzhen
Tested modelMiMo-V2.5
ProvidersInfistar
Samples107 probes
Duration1 min 34 sec
Verification versionV11
Identity verdictNot verified
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 usage45.5KFrom the response usage fields; this is the report's primary usage measure.Test-suite estimate1.7MPrecisely estimated from this test suite when no official baseline is available.Variance assessment97% belowMeasured token usage is below the estimate, possibly due to tokenizer, compression, or usage-reporting differences.Usage conclusionBelow 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 share89.9%
缓存字段表现稳定
多次测试均返回缓存 Token,说明这条链路的长对话用量记录有参考价值。
Observed tokens16.0KCached tokens14.4KNon-cached tokens1.6KAverage per run3.2K
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.
1 samples
Verified up to 32K
All tested context tiers (32K) returned reliably.
Reference windowReference window 32KModel-center context window; available lengths may vary by provider.Tested context lengths32KTests 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.
mimo-v2.5 deep verification result: Doubtful (69/100). Main deductions: Logic-grid reasoning was unstable; Hidden-prompt boundary was unclear; Model-family identification was unstable.
EvaluatorMozhenzhen
Tested modelMiMo-V2.5
ProvidersInfistar
Samples107
Duration2 min
Test versionV11
Identity verdictNot verified
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 usage45.5KFrom the response usage fields; this is the report's primary usage measure.Test-suite estimate1.7MPrecisely estimated from this test suite when no official baseline is available.Variance assessment97% belowMeasured token usage is below the estimate, possibly due to tokenizer, compression, or usage-reporting differences.Usage conclusionBelow 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 share89.9%
缓存字段表现稳定
多次测试均返回缓存 Token,说明这条链路的长对话用量记录有参考价值。
Observed tokens16.0KCached tokens14.4KNon-cached tokens1.6KAverage per run3.2K
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.
1 samples
Verified up to 32K
All tested context tiers (32K) returned reliably.
Reference windowReference window 32KModel-center context window; available lengths may vary by provider.Tested context lengths32KTests 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.