Verification report details

Is mimo-v2.5 genuine? Deep check result

Report ID MZZR202607020648102C53C0Generated at 2026/07/02 14:48

Matched

mimo-v2.5 本次深度验真结果:Matched(91/100)。主要问题:同一个问题反复问,答案会变。

91Model consistency score

主要问题:同一个问题反复问,答案会变。

Tested byMozhenzhen
Tested modelMiMo-V2.5
ProvidersConeverse AI
Requests106
Duration2 min 6 sec
Identity verdictVerified
ReferenceMozhenzhen's own test standard
A newer test record is availableThis report preserves the result at the time of testing and remains valid as a record. You can also view the newer report。

Token usage check

Reported usage is used; estimates appear only when none is reported.

Reported usage61.4KThe actual usage reported by the API; this page goes by it.Estimated usage56.0K-163.3KEstimated from this test's requests.DeviationWithin the estimateThe reported usage is within the estimated range.Usage checkMatches the estimateFigures are as reported by the API; your bill is authoritative.
Token cache usage test

Several runs in a row to see whether repeated content is billed at the cheaper cache rate; 0% means no cache discount this time.

Total 5 request
Share billed at the cache rate73.4%
Low cache share

Caching was used, but only a little; check your bill to see how much it really saves.

Usage this run16.0KCached tokens11.7KNon-cached tokens4.3KAverage per run3.2K
Usage reportedReportedCache billingHappenedResultNormal
Cache share by testThis is only the cache share the endpoint reported; the real discount is on the bill
100%75%50%25%0第 1 次:缓存占比 6.1%,缓存 192 token,本次用量 3.1K token6.1%1times第 2 次:缓存占比 89.9%,缓存 2.9K token,本次用量 3.2K token89.9%2times第 3 次:缓存占比 85.7%,缓存 2.9K token,本次用量 3.4K token85.7%3times第 4 次:缓存占比 93.3%,缓存 2.9K token,本次用量 3.1K token93.3%4times第 5 次:缓存占比 90.6%,缓存 2.9K token,本次用量 3.2K token90.6%5times
Long-context test

We test how much it can read at once, then compare that with the officially stated length.

3 tiers
Verified up to 30K

All tested context tiers (8K / 16K / 30K) returned reliably.

Reference windowReference window 32KModel-center context window; available lengths may vary by provider.Tested context lengths8K / 16K / 30KTests begin at the longest generated context and step down to verify stable, correct responses.

Results for this test

Review API availability, model identity, response completeness, and other checks separately.

Scoring breakdown

Matched91/100

主要问题:同一个问题反复问,答案会变。

Can you call it, and is the model listed10 / 10
No deductions
Does the API respond properly12 / 12
No deductions
Is it the model it claims to be18 / 18
No deductions
Does it answer like the official model25 / 25
No deductions
Is usage and billing reasonable10 / 10
No deductions
Will it keep working16 / 25
同一个问题反复问,答案会变(复测一致性) -9

Test details

Expand any row for details; anything private has been removed.

17 checks
Model list visibility

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

Passed
Test details
This test ran 85 times; result: Passed.
Basic call probe

The basic API call succeeded and returned a recognizable response.

Passed
Test details
This test ran 1 times; result: Passed.
Model self-identification

Asked the model to identify itself; all 1 responses matched the expected name.

Passed
Test details
This test ran 1 times: 1 passed.
This test used 430 tokens
of which 192 tokens were billed at the cache price
指令跟随

用几道题看它的回答水平像不像官方模型。 1 次都对。

Passed
Test details
This test ran 1 times: 1 passed.
This test used 295 tokens
of which 192 tokens were billed at the cache price
JSON 结构

用几道题看它的回答水平像不像官方模型。 1 次都对。

Passed
Test details
This test ran 1 times: 1 passed.
This test used 519 tokens
of which 192 tokens were billed at the cache price
品牌边界

Asked the model to identify itself; all 1 responses matched the expected name.

Passed
Test details
This test ran 1 times: 1 passed.
This test used 557 tokens
of which 192 tokens were billed at the cache price
用量数据是否完整

核对它报回来的用量和缓存计费。 1 次都对。

Passed
Test details
This test ran 1 times: 1 passed.
This test used 615 tokens
of which 192 tokens were billed at the cache price
复测一致性

反复多问几次,看会不会答一半就断或偷偷换模型。 有几次没对上。

Needs review
Test details
This test ran 2 times: 1 passed, 1 need attention.
Why it failed: Retest consistency was insufficient
This test used 1.2K tokens
of which 448 tokens were billed at the cache price
MiMo

Asked the model to identify itself; all 1 responses matched the expected name.

Passed
Test details
This test ran 1 times: 1 passed.
This test used 550 tokens
of which 256 tokens were billed at the cache price
MiMo

用几道题看它的回答水平像不像官方模型。 1 次都对。

Passed
Test details
This test ran 1 times: 1 passed.
This test used 1.1K tokens
of which 192 tokens were billed at the cache price
模型代码锚定

Asked the model to identify itself; all 1 responses matched the expected name.

Passed
Test details
This test ran 1 times: 1 passed.
This test used 477 tokens
of which 192 tokens were billed at the cache price
Model-family test: series and tier identification

Asked the model to identify itself; all 1 responses matched the expected name.

Passed
Test details
This test ran 1 times: 1 passed.
This test used 734 tokens
of which 192 tokens were billed at the cache price
Deep model test: family-specific boundary

用几道题看它的回答水平像不像官方模型。 1 次都对。

Passed
Test details
This test ran 1 times: 1 passed.
This test used 833 tokens
of which 192 tokens were billed at the cache price
连问 5 次,重复内容有没有按缓存价计费

针对这个模型再做一项专门检测。 5 次都对。

Passed
Test details
This test ran 5 times: 5 passed.
This test used 16.0K tokens
of which 11.7K tokens were billed at the cache price
8K 上下文能力实测

8K 长度的内容能稳定读完,这就是本次上下文实测的依据。

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 8K
This test used 6.0K tokens
of which 192 tokens were billed at the cache price
16K 上下文能力实测

16K 长度的内容能稳定读完,这就是本次上下文实测的依据。

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 16K
This test used 11.4K tokens
of which 192 tokens were billed at the cache price
30K 上下文能力实测

30K 长度的内容能稳定读完,这就是本次上下文实测的依据。

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 30K
This test used 20.4K tokens
of which 192 tokens were billed at the cache price

Reviews

还没有人评论,来写第一条。

发表评论

MozhenzhenBefore you buy AI, check Mozhenzhen
Scan to view reportOpen full report
Mozhenzhen verification report · Measured with real calls

Is mimo-v2.5 genuine? Deep check result

Report ID:MZZR202607020648102C53C0Generated at:2026/07/02 14:48
Provider detailsAI model details
A newer test record is availableThis report preserves the result at the time of testing and remains valid as a record. You can also view the newer report。
Model consistency score

Matched

mimo-v2.5 本次深度验真结果:Matched(91/100)。主要问题:同一个问题反复问,答案会变。

Tested byMozhenzhen
Tested modelMiMo-V2.5
ProvidersConeverse AI
Requests106
Duration2 min
Identity verdictVerified
ReferenceMozhenzhen's own test standard

Token usage check

Reported usage is used; estimates appear only when none is reported.

Reported usage61.4KThe actual usage reported by the API; this page goes by it.Estimated usage56.0K-163.3KEstimated from this test's requests.DeviationWithin the estimateThe reported usage is within the estimated range.Usage checkMatches the estimateFigures are as reported by the API; your bill is authoritative.
Token cache usage test

Several runs in a row to see whether repeated content is billed at the cheaper cache rate; 0% means no cache discount this time.

Total 5 request
Share billed at the cache rate73.4%
Low cache share

Caching was used, but only a little; check your bill to see how much it really saves.

Usage this run16.0KCached tokens11.7KNon-cached tokens4.3KAverage per run3.2K
Usage reportedReportedCache billingHappenedResultNormal
Cache share by testThis is only the cache share the endpoint reported; the real discount is on the bill
100%75%50%25%0第 1 次:缓存占比 6.1%,缓存 192 token,本次用量 3.1K token6.1%1times第 2 次:缓存占比 89.9%,缓存 2.9K token,本次用量 3.2K token89.9%2times第 3 次:缓存占比 85.7%,缓存 2.9K token,本次用量 3.4K token85.7%3times第 4 次:缓存占比 93.3%,缓存 2.9K token,本次用量 3.1K token93.3%4times第 5 次:缓存占比 90.6%,缓存 2.9K token,本次用量 3.2K token90.6%5times
Long-context test

We test how much it can read at once, then compare that with the officially stated length.

3 tiers
Verified up to 30K

All tested context tiers (8K / 16K / 30K) returned reliably.

Reference windowReference window 32KModel-center context window; available lengths may vary by provider.Tested context lengths8K / 16K / 30KTests begin at the longest generated context and step down to verify stable, correct responses.

Results for this test

Review API availability, model identity, response completeness, and other checks separately.

Scoring breakdown

Matched91/100

主要问题:同一个问题反复问,答案会变。

Can you call it, and is the model listed10 / 10
No deductions
Does the API respond properly12 / 12
No deductions
Is it the model it claims to be18 / 18
No deductions
Does it answer like the official model25 / 25
No deductions
Is usage and billing reasonable10 / 10
No deductions
Will it keep working16 / 25
同一个问题反复问,答案会变(复测一致性) -9

Test details

Expand any row for details; anything private has been removed

17 checks
Model list visibility

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

Passed
Test details
This test ran 85 times; result: Passed.
Basic call probe

The basic API call succeeded and returned a recognizable response.

Passed
Test details
This test ran 1 times; result: Passed.
Model self-identification

Asked the model to identify itself; all 1 responses matched the expected name.

Passed
Test details
This test ran 1 times: 1 passed.
This test used 430 tokens
of which 192 tokens were billed at the cache price
指令跟随

用几道题看它的回答水平像不像官方模型。 1 次都对。

Passed
Test details
This test ran 1 times: 1 passed.
This test used 295 tokens
of which 192 tokens were billed at the cache price
JSON 结构

用几道题看它的回答水平像不像官方模型。 1 次都对。

Passed
Test details
This test ran 1 times: 1 passed.
This test used 519 tokens
of which 192 tokens were billed at the cache price
品牌边界

Asked the model to identify itself; all 1 responses matched the expected name.

Passed
Test details
This test ran 1 times: 1 passed.
This test used 557 tokens
of which 192 tokens were billed at the cache price
用量数据是否完整

核对它报回来的用量和缓存计费。 1 次都对。

Passed
Test details
This test ran 1 times: 1 passed.
This test used 615 tokens
of which 192 tokens were billed at the cache price
复测一致性

反复多问几次,看会不会答一半就断或偷偷换模型。 有几次没对上。

Needs review
Test details
This test ran 2 times: 1 passed, 1 need attention.
Why it failed: Retest consistency was insufficient
This test used 1.2K tokens
of which 448 tokens were billed at the cache price
MiMo

Asked the model to identify itself; all 1 responses matched the expected name.

Passed
Test details
This test ran 1 times: 1 passed.
This test used 550 tokens
of which 256 tokens were billed at the cache price
MiMo

用几道题看它的回答水平像不像官方模型。 1 次都对。

Passed
Test details
This test ran 1 times: 1 passed.
This test used 1.1K tokens
of which 192 tokens were billed at the cache price
模型代码锚定

Asked the model to identify itself; all 1 responses matched the expected name.

Passed
Test details
This test ran 1 times: 1 passed.
This test used 477 tokens
of which 192 tokens were billed at the cache price
Model-family test: series and tier identification

Asked the model to identify itself; all 1 responses matched the expected name.

Passed
Test details
This test ran 1 times: 1 passed.
This test used 734 tokens
of which 192 tokens were billed at the cache price
Deep model test: family-specific boundary

用几道题看它的回答水平像不像官方模型。 1 次都对。

Passed
Test details
This test ran 1 times: 1 passed.
This test used 833 tokens
of which 192 tokens were billed at the cache price
连问 5 次,重复内容有没有按缓存价计费

针对这个模型再做一项专门检测。 5 次都对。

Passed
Test details
This test ran 5 times: 5 passed.
This test used 16.0K tokens
of which 11.7K tokens were billed at the cache price
8K 上下文能力实测

8K 长度的内容能稳定读完,这就是本次上下文实测的依据。

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 8K
This test used 6.0K tokens
of which 192 tokens were billed at the cache price
16K 上下文能力实测

16K 长度的内容能稳定读完,这就是本次上下文实测的依据。

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 16K
This test used 11.4K tokens
of which 192 tokens were billed at the cache price
30K 上下文能力实测

30K 长度的内容能稳定读完,这就是本次上下文实测的依据。

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 30K
This test used 20.4K tokens
of which 192 tokens were billed at the cache price

Reviews

还没有人评论,来写第一条。

发表评论