Is qwen3-max genuine? Deep check result
Highly matched
qwen3-max 本次深度验真结果:Highly matched(100/100)。本轮主要检测项均已Passed。
All primary checks passed in this run.
qwen3-max 本次深度验真结果:Highly matched(100/100)。本轮主要检测项均已Passed。
All primary checks passed in this run.
Reported usage is used; estimates appear only when none is reported.
Several runs in a row to see whether repeated content is billed at the cheaper cache rate; 0% means no cache discount this time.
Caching was used, but only a little; check your bill to see how much it really saves.
We test how much it can read at once, then compare that with the officially stated length.
128K 需要关注,原因:接口服务异常。
The 128K tier did not return reliably this time; do not rely on this length.
Review API availability, model identity, response completeness, and other checks separately.
All primary checks passed in this run.
Expand any row for details; anything private has been removed.
qwen3-max is visible in the API model list.
This test ran 85 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 75 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 24 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 38 tokens
Asked the model to identify itself; all 1 responses matched the expected name.
This test ran 1 times: 1 passed. This test used 83 tokens
核对它报回来的用量和缓存计费。 1 次都对。
This test ran 1 times: 1 passed. This test used 38 tokens
反复多问几次,看会不会答一半就断或偷偷换模型。 2 次都对。
This test ran 2 times: 2 passed. This test used 72 tokens
Asked the model to identify itself; all 1 responses matched the expected name.
This test ran 1 times: 1 passed. This test used 94 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 239 tokens
Asked the model to identify itself; all 1 responses matched the expected name.
This test ran 1 times: 1 passed. This test used 99 tokens
Asked the model to identify itself; all 1 responses matched the expected name.
This test ran 1 times: 1 passed. This test used 81 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 133 tokens
针对这个模型再做一项专门检测。 5 次都对。
This test ran 5 times: 5 passed. This test used 13.4K tokens of which 10.2K tokens were billed at the cache price
8K 长度的内容能稳定读完,这就是本次上下文实测的依据。
This test ran 1 times: 1 passed. Content length used: 8K This test used 5.1K tokens
16K 长度的内容能稳定读完,这就是本次上下文实测的依据。
This test ran 1 times: 1 passed. Content length used: 16K This test used 10.3K tokens
32K 长度的内容能稳定读完,这就是本次上下文实测的依据。
This test ran 1 times: 1 passed. Content length used: 32K This test used 20.5K tokens
64K 长度的内容能稳定读完,这就是本次上下文实测的依据。
This test ran 1 times: 1 passed. Content length used: 64K This test used 41.0K tokens
128K 长度的内容没能稳定读完,这次就记到这里为止。
This test ran 1 times: 1 need attention. Why it failed: API service error Content length used: 128K
还没有人评论,来写第一条。
Before you buy AI, check Mozhenzhenqwen3-max 本次深度验真结果:Highly matched(100/100)。本轮主要检测项均已Passed。
Reported usage is used; estimates appear only when none is reported.
Several runs in a row to see whether repeated content is billed at the cheaper cache rate; 0% means no cache discount this time.
Caching was used, but only a little; check your bill to see how much it really saves.
We test how much it can read at once, then compare that with the officially stated length.
128K 需要关注,原因:接口服务异常。
The 128K tier did not return reliably this time; do not rely on this length.
Review API availability, model identity, response completeness, and other checks separately.
All primary checks passed in this run.
Expand any row for details; anything private has been removed
qwen3-max is visible in the API model list.
This test ran 85 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 75 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 24 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 38 tokens
Asked the model to identify itself; all 1 responses matched the expected name.
This test ran 1 times: 1 passed. This test used 83 tokens
核对它报回来的用量和缓存计费。 1 次都对。
This test ran 1 times: 1 passed. This test used 38 tokens
反复多问几次,看会不会答一半就断或偷偷换模型。 2 次都对。
This test ran 2 times: 2 passed. This test used 72 tokens
Asked the model to identify itself; all 1 responses matched the expected name.
This test ran 1 times: 1 passed. This test used 94 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 239 tokens
Asked the model to identify itself; all 1 responses matched the expected name.
This test ran 1 times: 1 passed. This test used 99 tokens
Asked the model to identify itself; all 1 responses matched the expected name.
This test ran 1 times: 1 passed. This test used 81 tokens
用几道题看它的回答水平像不像官方模型。 1 次都对。
This test ran 1 times: 1 passed. This test used 133 tokens
针对这个模型再做一项专门检测。 5 次都对。
This test ran 5 times: 5 passed. This test used 13.4K tokens of which 10.2K tokens were billed at the cache price
8K 长度的内容能稳定读完,这就是本次上下文实测的依据。
This test ran 1 times: 1 passed. Content length used: 8K This test used 5.1K tokens
16K 长度的内容能稳定读完,这就是本次上下文实测的依据。
This test ran 1 times: 1 passed. Content length used: 16K This test used 10.3K tokens
32K 长度的内容能稳定读完,这就是本次上下文实测的依据。
This test ran 1 times: 1 passed. Content length used: 32K This test used 20.5K tokens
64K 长度的内容能稳定读完,这就是本次上下文实测的依据。
This test ran 1 times: 1 passed. Content length used: 64K This test used 41.0K tokens
128K 长度的内容没能稳定读完,这次就记到这里为止。
This test ran 1 times: 1 need attention. Why it failed: API service error Content length used: 128K
还没有人评论,来写第一条。
发表评论