mimo-v2.5-pro deep verification model-consistency report
Report ID MZZR2026071005310451E0F4Generated at 2026/07/10 13:31
Doubtful
mimo-v2.5-pro deep verification result: Doubtful (61/100). Main deductions: Logic-grid reasoning was unstable; API service error; Hidden-prompt boundary was unclear.
61Consistency score
主要扣分项:逻辑网格推理不稳定;接口服务异常;隐藏提示词边界不清。
EvaluatorMozhenzhen
Tested modelMiMo-V2.5-Pro
ProvidersInfistar
Samples101 probes
Duration1 min 24 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 usage3.7KFrom the response usage fields; this is the report's primary usage measure.Test-suite estimate6.7KPrecisely estimated from this test suite when no official baseline is available.Variance assessment45% 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.
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-pro deep verification result: Doubtful (61/100). Main deductions: Logic-grid reasoning was unstable; API service error; Hidden-prompt boundary was unclear.
EvaluatorMozhenzhen
Tested modelMiMo-V2.5-Pro
ProvidersInfistar
Samples101
Duration1 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 usage3.7KFrom the response usage fields; this is the report's primary usage measure.Test-suite estimate6.7KPrecisely estimated from this test suite when no official baseline is available.Variance assessment45% 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.
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.