Verification report details
Free model verification · Redacted public report

mimo-v2.5-pro quick verification model-consistency report

Report ID MZZR20260708102915E94179Generated at 2026/07/08 18:29

Highly matched

mimo-v2.5-pro quick verification result: Highly matched (100/100). All primary checks passed in this run.

100Consistency score

All primary checks passed in this run.

EvaluatorMozhenzhen
Tested modelMiMo-V2.5-Pro
ProvidersInfistar
Samples93 probes
Duration1 min 19 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 usage38.1KFrom 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 assessment98% 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 share90.8%
未观察到缓存字段

接口返回了实际 Token,但本次响应没有可识别的缓存 Token 字段;可能是渠道不返回、请求未命中或字段未被解析。

Observed tokens15.9KCached tokens14.4KNon-cached tokens1.5KAverage per run3.2K
Token usage recordReturnedCache fieldObservedResultNeeds review
Cache share by testRepresents the API-reported cache share, not the final billing discount.
100%75%50%25%01次:缓存 Token 占比 87.3%,缓存 Token 2.9K,观测 Token 3.3K87.3%1times2次:缓存 Token 占比 85.6%,缓存 Token 2.9K,观测 Token 3.4K85.6%2times3次:缓存 Token 占比 94.0%,缓存 Token 2.9K,观测 Token 3.1K94.0%3times4次:缓存 Token 占比 95.3%,缓存 Token 2.9K,观测 Token 3.0K95.3%4times5次:缓存 Token 占比 92.7%,缓存 Token 2.9K,观测 Token 3.1K92.7%5times
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.

Scoring breakdown

Highly matched100/100

All primary checks passed in this run.

接口与模型可见30 / 30
No deductions
基础调用与协议25 / 25
No deductions
模型身份红旗25 / 25
No deductions
基础稳定性20 / 20
No deductions

Test details

Expand each check to view the redacted evidence notes.

5 checks
Model list visibility

mimo-v2.5-pro is visible in the API model list.

Passed
Test evidence
Check: Model list visibility
Status: Passed
Samples: 85
API path: /v1/models
Visible models: 85
Basic call probe

The basic API call succeeded and returned a recognizable response.

Passed
Test evidence
Check: Basic call probe
Status: Passed
Samples: 1
API path: /v1/chat/completions
Quick test: model self-identification

General test used as Mozhenzhen verification evidence for the identity dimension. All samples passed.

Passed
Test evidence
Check: Quick test: model self-identification
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 464
Cached tokens: 192
Specialty test: token cache usage over 5 rounds

执行 专项题,用于形成模真真验真证据。 存在样本未完全Passed。

Needs review
Test evidence
Check: Specialty test: token cache usage over 5 rounds
Status: Needs review
Samples: 5
Test type: Text test
Specialty: Token cache usage test (may affect real billing)
Needs review原因:缓存用量字段不可观测
Results: Passed 4 / Needs review 1 / Failed 0
Observed tokens: 15.9K
Cached tokens: 14.4K
Specialty test: 32K context capability

32K context sample returned reliably and is included as evidence for this run.

Passed
Test evidence
Check: Specialty test: 32K context capability
Status: Passed
Samples: 1
Test type: Text test
Specialty: Context test
Context tier: 32K
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 21.5K
Cached tokens: 20.7K

Report comments

No public reviews

Be the first to leave a review.

Post an anonymous comment

Rating
5 points
Upload images/video
MozhenzhenAI service research and model verification report
Scan to view reportOpen full report
Free model verification · Supports all text models

mimo-v2.5-pro quick verification model-consistency report

Report ID:MZZR20260708102915E94179Generated at2026/07/08 18:29
Model consistency score

Highly matched

mimo-v2.5-pro quick verification result: Highly matched (100/100). All primary checks passed in this run.

EvaluatorMozhenzhen
Tested modelMiMo-V2.5-Pro
ProvidersInfistar
Samples93
Duration1 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 usage38.1KFrom 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 assessment98% 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 share90.8%
未观察到缓存字段

接口返回了实际 Token,但本次响应没有可识别的缓存 Token 字段;可能是渠道不返回、请求未命中或字段未被解析。

Observed tokens15.9KCached tokens14.4KNon-cached tokens1.5KAverage per run3.2K
Token usage recordReturnedCache fieldObservedResultNeeds review
Cache share by testRepresents the API-reported cache share, not the final billing discount.
100%75%50%25%01次:缓存 Token 占比 87.3%,缓存 Token 2.9K,观测 Token 3.3K87.3%1times2次:缓存 Token 占比 85.6%,缓存 Token 2.9K,观测 Token 3.4K85.6%2times3次:缓存 Token 占比 94.0%,缓存 Token 2.9K,观测 Token 3.1K94.0%3times4次:缓存 Token 占比 95.3%,缓存 Token 2.9K,观测 Token 3.0K95.3%4times5次:缓存 Token 占比 92.7%,缓存 Token 2.9K,观测 Token 3.1K92.7%5times
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.

Scoring breakdown

Highly matched100/100

All primary checks passed in this run.

接口与模型可见30 / 30
No deductions
基础调用与协议25 / 25
No deductions
模型身份红旗25 / 25
No deductions
基础稳定性20 / 20
No deductions

Test details

Expand each check to view the redacted evidence notes.

5 checks
Model list visibility

mimo-v2.5-pro is visible in the API model list.

Passed
Test evidence
Check: Model list visibility
Status: Passed
Samples: 85
API path: /v1/models
Visible models: 85
Basic call probe

The basic API call succeeded and returned a recognizable response.

Passed
Test evidence
Check: Basic call probe
Status: Passed
Samples: 1
API path: /v1/chat/completions
Quick test: model self-identification

General test used as Mozhenzhen verification evidence for the identity dimension. All samples passed.

Passed
Test evidence
Check: Quick test: model self-identification
Status: Passed
Samples: 1
Test type: Text test
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 464
Cached tokens: 192
Specialty test: token cache usage over 5 rounds

执行 专项题,用于形成模真真验真证据。 存在样本未完全Passed。

Needs review
Test evidence
Check: Specialty test: token cache usage over 5 rounds
Status: Needs review
Samples: 5
Test type: Text test
Specialty: Token cache usage test (may affect real billing)
Needs review原因:缓存用量字段不可观测
Results: Passed 4 / Needs review 1 / Failed 0
Observed tokens: 15.9K
Cached tokens: 14.4K
Specialty test: 32K context capability

32K context sample returned reliably and is included as evidence for this run.

Passed
Test evidence
Check: Specialty test: 32K context capability
Status: Passed
Samples: 1
Test type: Text test
Specialty: Context test
Context tier: 32K
Results: Passed 1 / Needs review 0 / Failed 0
Observed tokens: 21.5K
Cached tokens: 20.7K

Latest user reviews

No public reviews

Be the first to leave a review.

Comments and feedback on this report

Rating
5 points
Upload images/video