Verification report details

Is minimax-m3 genuine? Deep check result

Report ID MZZR20260812024418F0205CGenerated at 2026/08/12 10:44

Matched

minimax-m3 本次深度验真结果:Matched(86/100)。主要问题:被限量或限速了;有检测项没Passed。

86Model consistency score

主要问题:被限量或限速了;有检测项没Passed。

Tested byMozhenzhen
Tested modelMiniMax-M3
Providersnextapi.store
Requests13
Duration12 sec
Identity verdictVerified
Reference模真真既有版本化基线
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。

This call did not complete

Reason for failure

The provider limited the allowance or request rate.

What to do

Check the key allowance and concurrency limit. If this is temporary rate limiting, try again later.

Token usage check

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

Reported usage995The actual usage reported by the API; this page goes by it.Estimated usage6.8KEstimated from this test's requests.Deviation85% 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.

Results for this test

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

Scoring breakdown

Matched86/100

主要问题:被限量或限速了;有检测项没Passed。

Can you call it, and is the model listed6 / 10
被限量或限速了(标签结构复述) -4
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 working15 / 25
被限量或限速了(标签结构复述) -8有检测项没Passed -2

Test details

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

16 checks
Model list visibility

minimax-m3 is visible in the API model list.

Passed
Test details
This test ran 8 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 291 tokens
of which 219 tokens were billed at the cache price
指令跟随

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

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

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 222 tokens
of which 193 tokens were billed at the cache price
标签结构复述

按官方接口的标准调用,看返回是否规范。 有几次没对上。

Failed
Test details
This test ran 1 times: 1 failed.
Why it failed: Quota or rate limit reached
隐藏提示词边界

用几道题看它的回答水平像不像官方模型。 前序检测已确认被限量或限速了,为避免继续制造无效请求,本项已跳过。

Skipped
Test details
Result of this test: Skipped.
Why it failed: Quota or rate limit reached
Why it was not tested: service_failure_circuit_breaker
品牌边界

问它自己是什么模型,看答案对不对。 前序检测已确认被限量或限速了,为避免继续制造无效请求,本项已跳过。

Skipped
Test details
Result of this test: Skipped.
Why it failed: Quota or rate limit reached
Why it was not tested: service_failure_circuit_breaker
用量数据是否完整

核对它报回来的用量和缓存计费。 前序检测已确认被限量或限速了,为避免继续制造无效请求,本项已跳过。

Skipped
Test details
Result of this test: Skipped.
Why it failed: Quota or rate limit reached
Why it was not tested: service_failure_circuit_breaker
逻辑网格推理

用几道题看它的回答水平像不像官方模型。 前序检测已确认被限量或限速了,为避免继续制造无效请求,本项已跳过。

Skipped
Test details
Result of this test: Skipped.
Why it failed: Quota or rate limit reached
Why it was not tested: service_failure_circuit_breaker
复测一致性

反复多问几次,看会不会答一半就断或偷偷换模型。 前序检测已确认被限量或限速了,为避免继续制造无效请求,本项已跳过。

Skipped
Test details
Result of this test: Skipped.
Why it failed: Quota or rate limit reached
Why it was not tested: service_failure_circuit_breaker
MiniMax 中文能力边界

问它自己是什么模型,看答案对不对。 前序检测已确认被限量或限速了,为避免继续制造无效请求,本项已跳过。

Skipped
Test details
Result of this test: Skipped.
Why it failed: Quota or rate limit reached
Why it was not tested: service_failure_circuit_breaker
MiniMax 中文能力边界

用几道题看它的回答水平像不像官方模型。 前序检测已确认被限量或限速了,为避免继续制造无效请求,本项已跳过。

Skipped
Test details
Result of this test: Skipped.
Why it failed: Quota or rate limit reached
Why it was not tested: service_failure_circuit_breaker
模型代码锚定

问它自己是什么模型,看答案对不对。 前序检测已确认被限量或限速了,为避免继续制造无效请求,本项已跳过。

Skipped
Test details
Result of this test: Skipped.
Why it failed: Quota or rate limit reached
Why it was not tested: service_failure_circuit_breaker
Model-family test: series and tier identification

问它自己是什么模型,看答案对不对。 前序检测已确认被限量或限速了,为避免继续制造无效请求,本项已跳过。

Skipped
Test details
Result of this test: Skipped.
Why it failed: Quota or rate limit reached
Why it was not tested: service_failure_circuit_breaker
Deep model test: family-specific boundary

用几道题看它的回答水平像不像官方模型。 前序检测已确认被限量或限速了,为避免继续制造无效请求,本项已跳过。

Skipped
Test details
Result of this test: Skipped.
Why it failed: Quota or rate limit reached
Why it was not tested: service_failure_circuit_breaker

Reviews

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

发表评论

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

Is minimax-m3 genuine? Deep check result

Report ID:MZZR20260812024418F0205CGenerated at:2026/08/12 10:44
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

minimax-m3 本次深度验真结果:Matched(86/100)。主要问题:被限量或限速了;有检测项没Passed。

Tested byMozhenzhen
Tested modelMiniMax-M3
Providersnextapi.store
Requests13
Duration12 sec
Identity verdictVerified
Reference模真真既有版本化基线

This call did not complete

Reason for failure

The provider limited the allowance or request rate.

What to do

Check the key allowance and concurrency limit. If this is temporary rate limiting, try again later.

Token usage check

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

Reported usage995The actual usage reported by the API; this page goes by it.Estimated usage6.8KEstimated from this test's requests.Deviation85% 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.

Results for this test

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

Scoring breakdown

Matched86/100

主要问题:被限量或限速了;有检测项没Passed。

Can you call it, and is the model listed6 / 10
被限量或限速了(标签结构复述) -4
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 working15 / 25
被限量或限速了(标签结构复述) -8有检测项没Passed -2

Test details

Expand any row for details; anything private has been removed

16 checks
Model list visibility

minimax-m3 is visible in the API model list.

Passed
Test details
This test ran 8 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 291 tokens
of which 219 tokens were billed at the cache price
指令跟随

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

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

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 222 tokens
of which 193 tokens were billed at the cache price
标签结构复述

按官方接口的标准调用,看返回是否规范。 有几次没对上。

Failed
Test details
This test ran 1 times: 1 failed.
Why it failed: Quota or rate limit reached
隐藏提示词边界

用几道题看它的回答水平像不像官方模型。 前序检测已确认被限量或限速了,为避免继续制造无效请求,本项已跳过。

Skipped
Test details
Result of this test: Skipped.
Why it failed: Quota or rate limit reached
Why it was not tested: service_failure_circuit_breaker
品牌边界

问它自己是什么模型,看答案对不对。 前序检测已确认被限量或限速了,为避免继续制造无效请求,本项已跳过。

Skipped
Test details
Result of this test: Skipped.
Why it failed: Quota or rate limit reached
Why it was not tested: service_failure_circuit_breaker
用量数据是否完整

核对它报回来的用量和缓存计费。 前序检测已确认被限量或限速了,为避免继续制造无效请求,本项已跳过。

Skipped
Test details
Result of this test: Skipped.
Why it failed: Quota or rate limit reached
Why it was not tested: service_failure_circuit_breaker
逻辑网格推理

用几道题看它的回答水平像不像官方模型。 前序检测已确认被限量或限速了,为避免继续制造无效请求,本项已跳过。

Skipped
Test details
Result of this test: Skipped.
Why it failed: Quota or rate limit reached
Why it was not tested: service_failure_circuit_breaker
复测一致性

反复多问几次,看会不会答一半就断或偷偷换模型。 前序检测已确认被限量或限速了,为避免继续制造无效请求,本项已跳过。

Skipped
Test details
Result of this test: Skipped.
Why it failed: Quota or rate limit reached
Why it was not tested: service_failure_circuit_breaker
MiniMax 中文能力边界

问它自己是什么模型,看答案对不对。 前序检测已确认被限量或限速了,为避免继续制造无效请求,本项已跳过。

Skipped
Test details
Result of this test: Skipped.
Why it failed: Quota or rate limit reached
Why it was not tested: service_failure_circuit_breaker
MiniMax 中文能力边界

用几道题看它的回答水平像不像官方模型。 前序检测已确认被限量或限速了,为避免继续制造无效请求,本项已跳过。

Skipped
Test details
Result of this test: Skipped.
Why it failed: Quota or rate limit reached
Why it was not tested: service_failure_circuit_breaker
模型代码锚定

问它自己是什么模型,看答案对不对。 前序检测已确认被限量或限速了,为避免继续制造无效请求,本项已跳过。

Skipped
Test details
Result of this test: Skipped.
Why it failed: Quota or rate limit reached
Why it was not tested: service_failure_circuit_breaker
Model-family test: series and tier identification

问它自己是什么模型,看答案对不对。 前序检测已确认被限量或限速了,为避免继续制造无效请求,本项已跳过。

Skipped
Test details
Result of this test: Skipped.
Why it failed: Quota or rate limit reached
Why it was not tested: service_failure_circuit_breaker
Deep model test: family-specific boundary

用几道题看它的回答水平像不像官方模型。 前序检测已确认被限量或限速了,为避免继续制造无效请求,本项已跳过。

Skipped
Test details
Result of this test: Skipped.
Why it failed: Quota or rate limit reached
Why it was not tested: service_failure_circuit_breaker

Reviews

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

发表评论