Is minimax-m3 genuine? Deep check result
High risk
minimax-m3 本次深度验真结果:High risk(55/100)。主要问题:复杂推理题答得不稳;等太久没回应;问到不该说的内容时把握不住分寸。
主要问题:复杂推理题答得不稳;等太久没回应;问到不该说的内容时把握不住分寸。
minimax-m3 本次深度验真结果:High risk(55/100)。主要问题:复杂推理题答得不稳;等太久没回应;问到不该说的内容时把握不住分寸。
主要问题:复杂推理题答得不稳;等太久没回应;问到不该说的内容时把握不住分寸。
The API did not return a result within this test’s waiting period.
Try again later. If this persists, ask the provider whether this model is responding normally.
Reported usage is used; estimates appear only when none is reported.
We test how much it can read at once, then compare that with the officially stated length.
All tested context tiers (32K) returned reliably.
Review API availability, model identity, response completeness, and other checks separately.
主要问题:复杂推理题答得不稳;等太久没回应;问到不该说的内容时把握不住分寸。
Expand any row for details; anything private has been removed.
minimax-m3 is visible in the API model list.
This test ran 8 times; result: Passed.
The basic API call succeeded and returned a recognizable response.
This test ran 1 times; result: Passed.
Asked the model to identify itself; all 1 responses matched the expected name.
This test ran 1 times: 1 passed. This test used 284 tokens of which 219 tokens were billed at the cache price
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 238 tokens of which 114 tokens were billed at the cache price
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 226 tokens of which 193 tokens were billed at the cache price
按官方接口的标准调用,看返回是否规范。 1 次都对。
This test ran 1 times: 1 passed. This test used 268 tokens of which 217 tokens were billed at the cache price
用几道题看它的回答水平像不像官方模型。 有几次没对上。
This test ran 1 times: 1 need attention. Why it failed: Hidden-prompt boundary was unclear This test used 466 tokens of which 207 tokens were billed at the cache price
Asked the model to identify itself; all 1 responses matched the expected name.
This test ran 1 times: 1 passed. This test used 310 tokens of which 114 tokens were billed at the cache price
核对它报回来的用量和缓存计费。 1 次都对。
This test ran 1 times: 1 passed. This test used 245 tokens of which 198 tokens were billed at the cache price
用几道题看它的回答水平像不像官方模型。 有几次没对上。
This test ran 1 times: 1 need attention. Why it failed: Logic-grid reasoning was unstable
反复多问几次,看会不会答一半就断或偷偷换模型。 有几次没对上。
This test ran 2 times: 1 passed, 1 need attention. Why it failed: Retest consistency was insufficient This test used 1.0K tokens of which 390 tokens were billed at the cache price
Asked the model to identify itself; all 1 responses matched the expected name.
This test ran 1 times: 1 passed. This test used 890 tokens of which 220 tokens were billed at the cache price
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 1.2K tokens of which 220 tokens were billed at the cache price
Asked the model to identify itself; all 1 responses matched the expected name.
This test ran 1 times: 1 passed. This test used 554 tokens of which 231 tokens were billed at the cache price
问它自己是什么模型,看答案对不对。 有几次没对上。
This test ran 1 times: 1 failed.
用几道题看它的回答水平像不像官方模型。 前序检测已确认等太久没回应,为避免继续制造无效请求,本项已跳过。
Result of this test: Skipped. Why it was not tested: service_failure_circuit_breaker
32K 长度的内容能稳定读完,这就是本次上下文实测的依据。
This test ran 1 times: 1 passed. Content length used: 32K This test used 17.6K tokens of which 128 tokens were billed at the cache price
还没有人评论,来写第一条。
Before you buy AI, check Mozhenzhenminimax-m3 本次深度验真结果:High risk(55/100)。主要问题:复杂推理题答得不稳;等太久没回应;问到不该说的内容时把握不住分寸。
The API did not return a result within this test’s waiting period.
Try again later. If this persists, ask the provider whether this model is responding normally.
Reported usage is used; estimates appear only when none is reported.
We test how much it can read at once, then compare that with the officially stated length.
All tested context tiers (32K) returned reliably.
Review API availability, model identity, response completeness, and other checks separately.
主要问题:复杂推理题答得不稳;等太久没回应;问到不该说的内容时把握不住分寸。
Expand any row for details; anything private has been removed
minimax-m3 is visible in the API model list.
This test ran 8 times; result: Passed.
The basic API call succeeded and returned a recognizable response.
This test ran 1 times; result: Passed.
Asked the model to identify itself; all 1 responses matched the expected name.
This test ran 1 times: 1 passed. This test used 284 tokens of which 219 tokens were billed at the cache price
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 238 tokens of which 114 tokens were billed at the cache price
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 226 tokens of which 193 tokens were billed at the cache price
按官方接口的标准调用,看返回是否规范。 1 次都对。
This test ran 1 times: 1 passed. This test used 268 tokens of which 217 tokens were billed at the cache price
用几道题看它的回答水平像不像官方模型。 有几次没对上。
This test ran 1 times: 1 need attention. Why it failed: Hidden-prompt boundary was unclear This test used 466 tokens of which 207 tokens were billed at the cache price
Asked the model to identify itself; all 1 responses matched the expected name.
This test ran 1 times: 1 passed. This test used 310 tokens of which 114 tokens were billed at the cache price
核对它报回来的用量和缓存计费。 1 次都对。
This test ran 1 times: 1 passed. This test used 245 tokens of which 198 tokens were billed at the cache price
用几道题看它的回答水平像不像官方模型。 有几次没对上。
This test ran 1 times: 1 need attention. Why it failed: Logic-grid reasoning was unstable
反复多问几次,看会不会答一半就断或偷偷换模型。 有几次没对上。
This test ran 2 times: 1 passed, 1 need attention. Why it failed: Retest consistency was insufficient This test used 1.0K tokens of which 390 tokens were billed at the cache price
Asked the model to identify itself; all 1 responses matched the expected name.
This test ran 1 times: 1 passed. This test used 890 tokens of which 220 tokens were billed at the cache price
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 1.2K tokens of which 220 tokens were billed at the cache price
Asked the model to identify itself; all 1 responses matched the expected name.
This test ran 1 times: 1 passed. This test used 554 tokens of which 231 tokens were billed at the cache price
问它自己是什么模型,看答案对不对。 有几次没对上。
This test ran 1 times: 1 failed.
用几道题看它的回答水平像不像官方模型。 前序检测已确认等太久没回应,为避免继续制造无效请求,本项已跳过。
Result of this test: Skipped. Why it was not tested: service_failure_circuit_breaker
32K 长度的内容能稳定读完,这就是本次上下文实测的依据。
This test ran 1 times: 1 passed. Content length used: 32K This test used 17.6K tokens of which 128 tokens were billed at the cache price
还没有人评论,来写第一条。
发表评论