Verification report details

Is MiniMax-M2 genuine? Deep check result

Report ID MZZR202608220953280BA7A4Generated at 2026/08/22 17:53

Matched

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

86Model consistency score

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

Tested byMozhenzhen
Tested modelMiniMax-M2
Providers无限星河AI(国内站)
Requests132
Duration4 min 25 sec
Identity verdictVerified
Reference模真真既有版本化基线

Token usage check

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

Reported usage123.8KThe actual usage reported by the API; this page goes by it.Estimated usage186.4KEstimated from this test's requests.Deviation34% 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 rate0.0%
No cache discount this time

The endpoint reported real usage but no cached part; this seller may not offer cache pricing, or nothing hit the cache this time.

Usage this run11.6KCached tokens0Non-cached tokens11.6KAverage per run2.3K
Usage reportedReportedCache billingDid not happenResultHigh risk
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 次:缓存占比 0.0%,缓存 0 token,本次用量 2.9K token0.0%1times第 2 次:缓存占比 0.0%,缓存 0 token,本次用量 2.9K token0.0%2times第 3 次:缓存占比 0.0%,缓存 0 token,本次用量 3.0K token0.0%3times第 4 次:缓存占比 0.0%,缓存 0 token,本次用量 2.8K token0.0%4times第 5 次:没有返回用量未返回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 100K

All tested context tiers (32K / 64K / 100K) returned reliably.

Reference windowReference window 192KModel-center context window; available lengths may vary by provider.Tested context lengths32K / 64K / 100KTests 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.

20 checks
Model list visibility

MiniMax-M2 is visible in the API model list.

Passed
Test details
This test ran 108 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 324 tokens
指令跟随

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 245 tokens
JSON 结构

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 204 tokens
标签结构复述

按官方接口的标准调用,看返回是否规范。 1 次都对。

Passed
Test details
This test ran 1 times: 1 passed.
This test used 297 tokens
隐藏提示词边界

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 269 tokens
品牌边界

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 737 tokens
用量数据是否完整

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 306 tokens
逻辑网格推理

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

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 480 tokens
MiniMax 中文能力边界

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 461 tokens
MiniMax 中文能力边界

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 1.1K tokens
模型代码锚定

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 321 tokens
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 408 tokens
Deep model test: family-specific boundary

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 872 tokens
连问 5 次,重复内容有没有按缓存价计费

针对这个模型再做一项专门检测。 有几次没对上。

Failed
Test details
This test ran 5 times: 4 passed, 1 failed.
This test used 11.6K tokens
32K 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 32K
This test used 17.6K tokens
64K 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 64K
This test used 34.8K tokens
100K 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 100K
This test used 53.4K tokens

Reviews

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

发表评论

编辑器加载中…
MozhenzhenBefore you buy AI, check Mozhenzhen
Scan to view reportOpen full report
Mozhenzhen verification report · Measured with real calls

Is MiniMax-M2 genuine? Deep check result

Report ID:MZZR202608220953280BA7A4Generated at:2026/08/22 17:53
Provider detailsAI model details
Model consistency score

Matched

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

Tested byMozhenzhen
Tested modelMiniMax-M2
Providers无限星河AI(国内站)
Requests132
Duration4 min
Identity verdictVerified
Reference模真真既有版本化基线

Token usage check

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

Reported usage123.8KThe actual usage reported by the API; this page goes by it.Estimated usage186.4KEstimated from this test's requests.Deviation34% 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 rate0.0%
No cache discount this time

The endpoint reported real usage but no cached part; this seller may not offer cache pricing, or nothing hit the cache this time.

Usage this run11.6KCached tokens0Non-cached tokens11.6KAverage per run2.3K
Usage reportedReportedCache billingDid not happenResultHigh risk
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 次:缓存占比 0.0%,缓存 0 token,本次用量 2.9K token0.0%1times第 2 次:缓存占比 0.0%,缓存 0 token,本次用量 2.9K token0.0%2times第 3 次:缓存占比 0.0%,缓存 0 token,本次用量 3.0K token0.0%3times第 4 次:缓存占比 0.0%,缓存 0 token,本次用量 2.8K token0.0%4times第 5 次:没有返回用量未返回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 100K

All tested context tiers (32K / 64K / 100K) returned reliably.

Reference windowReference window 192KModel-center context window; available lengths may vary by provider.Tested context lengths32K / 64K / 100KTests 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

20 checks
Model list visibility

MiniMax-M2 is visible in the API model list.

Passed
Test details
This test ran 108 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 324 tokens
指令跟随

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 245 tokens
JSON 结构

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 204 tokens
标签结构复述

按官方接口的标准调用,看返回是否规范。 1 次都对。

Passed
Test details
This test ran 1 times: 1 passed.
This test used 297 tokens
隐藏提示词边界

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 269 tokens
品牌边界

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 737 tokens
用量数据是否完整

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 306 tokens
逻辑网格推理

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

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 480 tokens
MiniMax 中文能力边界

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 461 tokens
MiniMax 中文能力边界

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 1.1K tokens
模型代码锚定

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 321 tokens
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 408 tokens
Deep model test: family-specific boundary

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 872 tokens
连问 5 次,重复内容有没有按缓存价计费

针对这个模型再做一项专门检测。 有几次没对上。

Failed
Test details
This test ran 5 times: 4 passed, 1 failed.
This test used 11.6K tokens
32K 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 32K
This test used 17.6K tokens
64K 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 64K
This test used 34.8K tokens
100K 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 100K
This test used 53.4K tokens

Reviews

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

发表评论

编辑器加载中…