mimo-v2.5 deep verification model-consistency report
Report ID MZZR20260709040653A2B56BGenerated at 2026/07/09 12:06
Doubtful
mimo-v2.5 deep verification result: Doubtful (65/100). Main deductions: Logic-grid reasoning was unstable; Hidden-prompt boundary was unclear; Usage fields were not observable.
65Consistency score
主要扣分项:逻辑网格推理不稳定;隐藏提示词边界不清;usage 用量字段不可观测。
EvaluatorMozhenzhen
Tested modelMiMo-V2.5
ProvidersInfistar
Samples107 probes
Duration1 min 47 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 usage46.4KFrom 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 share75.1%
Low cache share
Cached tokens were observed, but the share is low. Review API parameters, context reuse, and billing methodology.
Observed tokens15.6KCached tokens11.7KNon-cached tokens3.9KAverage per run3.1K
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 (65/100). Main deductions: Logic-grid reasoning was unstable; Hidden-prompt boundary was unclear; Usage fields were not observable.
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 usage46.4KFrom 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 share75.1%
Low cache share
Cached tokens were observed, but the share is low. Review API parameters, context reuse, and billing methodology.
Observed tokens15.6KCached tokens11.7KNon-cached tokens3.9KAverage per run3.1K
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.