mimo-v2.5 deep verification model-consistency report
Report ID MZZR202608260259487CA346Generated at 2026/08/26 10:59
Doubtful
mimo-v2.5 deep verification result: Doubtful (74/100). Main deductions: Logic-grid reasoning was unstable; Usage fields were not observable; Brand-boundary response was unclear.
74Consistency score
主要扣分项：逻辑网格推理不稳定；usage 用量字段不可观测；品牌边界表达不清。
EvaluatorMozhenzhen
Tested modelMiMo-V2.5
Providersinfistar.cc
Samples130 probes
Duration4 min 37 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 usage676.0KFrom 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 assessment60% 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 share74.8%
Low cache share
Cached tokens were observed, but the share is low. Review API parameters, context reuse, and billing methodology.
Observed tokens15.7KCached 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 1M
All tested context tiers (1M) returned reliably.
Reference windowReference window 1MModel-center context window; available lengths may vary by provider.Tested context lengths1MTests 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.
Scoring breakdown
Doubtful74/100
主要扣分项：逻辑网格推理不稳定；usage 用量字段不可观测；品牌边界表达不清。
Callability and model visibility10 / 10
No deductions
Protocol and response structure9 / 12
usage 用量字段不可观测（标准题：usage 返回可观测性） -3
Identity and model match14 / 18
品牌边界表达不清（标准题：品牌边界） -4
Core capabilities and model-specific tests15 / 25
逻辑网格推理不稳定（深度题：逻辑网格推理） -10
Usage and billing consistency5 / 10
usage 用量字段不可观测（标准题：usage 返回可观测性） -5
Reliability and availability21 / 25
逻辑网格推理不稳定（深度题：逻辑网格推理） -4
Test details
Expand each check to view the redacted evidence notes.
18 checks
Model list visibility
mimo-v2.5 is visible in the API model list.
Passed
Test evidence
Check: Model list visibility
Status: Passed
Samples: 108
API path: /models
Visible models: 108
Basic call probe
The basic API call succeeded and returned a recognizable response.
mimo-v2.5 deep verification result: Doubtful (74/100). Main deductions: Logic-grid reasoning was unstable; Usage fields were not observable; Brand-boundary response was unclear.
EvaluatorMozhenzhen
Tested modelMiMo-V2.5
Providersinfistar.cc
Samples130
Duration5 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 usage676.0KFrom 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 assessment60% 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 share74.8%
Low cache share
Cached tokens were observed, but the share is low. Review API parameters, context reuse, and billing methodology.
Observed tokens15.7KCached 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 1M
All tested context tiers (1M) returned reliably.
Reference windowReference window 1MModel-center context window; available lengths may vary by provider.Tested context lengths1MTests 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.
Scoring breakdown
Doubtful74/100
主要扣分项：逻辑网格推理不稳定；usage 用量字段不可观测；品牌边界表达不清。
Callability and model visibility10 / 10
No deductions
Protocol and response structure9 / 12
usage 用量字段不可观测（标准题：usage 返回可观测性） -3
Identity and model match14 / 18
品牌边界表达不清（标准题：品牌边界） -4
Core capabilities and model-specific tests15 / 25
逻辑网格推理不稳定（深度题：逻辑网格推理） -10
Usage and billing consistency5 / 10
usage 用量字段不可观测（标准题：usage 返回可观测性） -5
Reliability and availability21 / 25
逻辑网格推理不稳定（深度题：逻辑网格推理） -4
Test details
Expand each check to view the redacted evidence notes.
18 checks
Model list visibility
mimo-v2.5 is visible in the API model list.
Passed
Test evidence
Check: Model list visibility
Status: Passed
Samples: 108
API path: /models
Visible models: 108
Basic call probe
The basic API call succeeded and returned a recognizable response.
