Verification report details

Is mimo-v2.5-pro genuine? Deep check result

Report ID MZZR202607080809506CF231Generated at 2026/07/08 16:09

Matched

mimo-v2.5-pro 本次深度验真结果:Matched(86/100)。主要问题:复杂推理题答得不稳。

86Model consistency score

主要问题:复杂推理题答得不稳。

Tested byMozhenzhen
Tested modelMiMo-V2.5-Pro
ProvidersConeverse AI
Requests107
Duration4 min 28 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 usage44.1KThe actual usage reported by the API; this page goes by it.Estimated usage82.0KEstimated from this test's requests.Deviation46% belowThe reported usage is below the estimate, possibly because of how tokens are counted or compressed.Usage checkBelow 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 rate93.1%
Cache discount applied consistently

Every run was billed at the cache rate, so long chats save real money.

Usage this run15.5KCached tokens14.4KNon-cached tokens1.1KAverage per run3.1K
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 次:缓存占比 95.0%,缓存 2.9K token,本次用量 3.0K token95.0%1times第 2 次:缓存占比 93.4%,缓存 2.9K token,本次用量 3.1K token93.4%2times第 3 次:缓存占比 92.5%,缓存 2.9K token,本次用量 3.1K token92.5%3times第 4 次:缓存占比 94.4%,缓存 2.9K token,本次用量 3.1K token94.4%4times第 5 次:缓存占比 90.2%,缓存 2.9K token,本次用量 3.2K token90.2%5times
Long-context test

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

1 tiers
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.

Results for this test

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

Scoring breakdown

Matched86/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 model15 / 25
复杂推理题答得不稳(逻辑网格推理) -10
Is usage and billing reasonable10 / 10
No deductions
Will it keep working21 / 25
复杂推理题答得不稳(逻辑网格推理) -4

Test details

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

18 checks
Model list visibility

mimo-v2.5-pro 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 467 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 313 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 314 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 630 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 406 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 485 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 336 tokens
of which 192 tokens were billed at the cache price
逻辑网格推理

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

Needs review
Test details
This test ran 1 times: 1 need attention.
Why it failed: Logic-grid reasoning was unstable
复测一致性

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

Passed
Test details
This test ran 2 times: 2 passed.
This test used 726 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 482 tokens
of which 192 tokens were billed at the cache price
MiMo

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 1.0K 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 570 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 368 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 751 tokens
of which 256 tokens were billed at the cache price
连问 5 次,重复内容有没有按缓存价计费

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

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

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 32K
This test used 21.4K tokens
of which 20.7K 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-pro genuine? Deep check result

Report ID:MZZR202607080809506CF231Generated at:2026/07/08 16:09
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-pro 本次深度验真结果:Matched(86/100)。主要问题:复杂推理题答得不稳。

Tested byMozhenzhen
Tested modelMiMo-V2.5-Pro
ProvidersConeverse AI
Requests107
Duration4 min
Identity verdictVerified
ReferenceMozhenzhen's own test standard

Token usage check

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

Reported usage44.1KThe actual usage reported by the API; this page goes by it.Estimated usage82.0KEstimated from this test's requests.Deviation46% belowThe reported usage is below the estimate, possibly because of how tokens are counted or compressed.Usage checkBelow 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 rate93.1%
Cache discount applied consistently

Every run was billed at the cache rate, so long chats save real money.

Usage this run15.5KCached tokens14.4KNon-cached tokens1.1KAverage per run3.1K
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 次:缓存占比 95.0%,缓存 2.9K token,本次用量 3.0K token95.0%1times第 2 次:缓存占比 93.4%,缓存 2.9K token,本次用量 3.1K token93.4%2times第 3 次:缓存占比 92.5%,缓存 2.9K token,本次用量 3.1K token92.5%3times第 4 次:缓存占比 94.4%,缓存 2.9K token,本次用量 3.1K token94.4%4times第 5 次:缓存占比 90.2%,缓存 2.9K token,本次用量 3.2K token90.2%5times
Long-context test

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

1 tiers
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.

Results for this test

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

Scoring breakdown

Matched86/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 model15 / 25
复杂推理题答得不稳(逻辑网格推理) -10
Is usage and billing reasonable10 / 10
No deductions
Will it keep working21 / 25
复杂推理题答得不稳(逻辑网格推理) -4

Test details

Expand any row for details; anything private has been removed

18 checks
Model list visibility

mimo-v2.5-pro 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 467 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 313 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 314 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 630 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 406 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 485 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 336 tokens
of which 192 tokens were billed at the cache price
逻辑网格推理

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

Needs review
Test details
This test ran 1 times: 1 need attention.
Why it failed: Logic-grid reasoning was unstable
复测一致性

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

Passed
Test details
This test ran 2 times: 2 passed.
This test used 726 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 482 tokens
of which 192 tokens were billed at the cache price
MiMo

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 1.0K 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 570 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 368 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 751 tokens
of which 256 tokens were billed at the cache price
连问 5 次,重复内容有没有按缓存价计费

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

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

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

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

Reviews

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

发表评论