Verification report details

Is qwen3-max genuine? Deep check result

Report ID MZZR2026070605303323CA56Generated at 2026/07/06 13:30

Highly matched

qwen3-max 本次深度验真结果:Highly matched(100/100)。本轮主要检测项均已Passed。

100Model consistency score

All primary checks passed in this run.

Tested byMozhenzhen
Tested modelQwen3 Max
ProvidersConeverse AI
Requests108
Duration1 min 16 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 usage91.3KThe actual usage reported by the API; this page goes by it.Estimated usage372.1KEstimated from this test's requests.Deviation75% 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 rate76.4%
Low cache share

Caching was used, but only a little; check your bill to see how much it really saves.

Usage this run13.4KCached tokens10.2KNon-cached tokens3.2KAverage per run2.7K
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 次:缓存占比 0.0%,缓存 0 token,本次用量 2.7K token0.0%1times第 2 次:缓存占比 95.5%,缓存 2.6K token,本次用量 2.7K token95.5%2times第 3 次:缓存占比 95.5%,缓存 2.6K token,本次用量 2.7K token95.5%3times第 4 次:缓存占比 95.5%,缓存 2.6K token,本次用量 2.7K token95.5%4times第 5 次:缓存占比 95.5%,缓存 2.6K token,本次用量 2.7K token95.5%5times
Long-context test

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

5 tiers
Verified up to 64K

128K 需要关注,原因:接口服务异常。

Reference windowReference window 256KModel-center context window; available lengths may vary by provider.Tested context lengths8K / 16K / 32K / 64K / 128KTests begin at the longest generated context and step down to verify stable, correct responses.
Current guidance

The 128K tier did not return reliably this time; do not rely on this length.

Results for this test

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

Scoring breakdown

Highly matched100/100

All primary checks passed in this run.

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 model25 / 25
No deductions
Is usage and billing reasonable10 / 10
No deductions
Will it keep working25 / 25
No deductions

Test details

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

19 checks
Model list visibility

qwen3-max 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 75 tokens
指令跟随

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

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

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

Passed
Test details
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.

Passed
Test details
This test ran 1 times: 1 passed.
This test used 83 tokens
用量数据是否完整

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 38 tokens
复测一致性

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

Passed
Test details
This test ran 2 times: 2 passed.
This test used 72 tokens
Qwen 中文和视觉边界

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 94 tokens
Qwen 中文和视觉边界

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

Passed
Test details
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.

Passed
Test details
This test ran 1 times: 1 passed.
This test used 99 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 81 tokens
Deep model test: family-specific boundary

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

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

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

Passed
Test details
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 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 8K
This test used 5.1K tokens
16K 上下文能力实测

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

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

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

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

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

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

128K 长度的内容没能稳定读完,这次就记到这里为止。

Needs review
Test details
This test ran 1 times: 1 need attention.
Why it failed: API service error
Content length used: 128K

Reviews

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

发表评论

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

Is qwen3-max genuine? Deep check result

Report ID:MZZR2026070605303323CA56Generated at:2026/07/06 13:30
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

Highly matched

qwen3-max 本次深度验真结果:Highly matched(100/100)。本轮主要检测项均已Passed。

Tested byMozhenzhen
Tested modelQwen3 Max
ProvidersConeverse AI
Requests108
Duration1 min
Identity verdictVerified
ReferenceMozhenzhen's own test standard

Token usage check

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

Reported usage91.3KThe actual usage reported by the API; this page goes by it.Estimated usage372.1KEstimated from this test's requests.Deviation75% 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 rate76.4%
Low cache share

Caching was used, but only a little; check your bill to see how much it really saves.

Usage this run13.4KCached tokens10.2KNon-cached tokens3.2KAverage per run2.7K
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 次:缓存占比 0.0%,缓存 0 token,本次用量 2.7K token0.0%1times第 2 次:缓存占比 95.5%,缓存 2.6K token,本次用量 2.7K token95.5%2times第 3 次:缓存占比 95.5%,缓存 2.6K token,本次用量 2.7K token95.5%3times第 4 次:缓存占比 95.5%,缓存 2.6K token,本次用量 2.7K token95.5%4times第 5 次:缓存占比 95.5%,缓存 2.6K token,本次用量 2.7K token95.5%5times
Long-context test

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

5 tiers
Verified up to 64K

128K 需要关注,原因:接口服务异常。

Reference windowReference window 256KModel-center context window; available lengths may vary by provider.Tested context lengths8K / 16K / 32K / 64K / 128KTests begin at the longest generated context and step down to verify stable, correct responses.
Current guidance

The 128K tier did not return reliably this time; do not rely on this length.

Results for this test

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

Scoring breakdown

Highly matched100/100

All primary checks passed in this run.

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 model25 / 25
No deductions
Is usage and billing reasonable10 / 10
No deductions
Will it keep working25 / 25
No deductions

Test details

Expand any row for details; anything private has been removed

19 checks
Model list visibility

qwen3-max 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 75 tokens
指令跟随

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

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

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

Passed
Test details
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.

Passed
Test details
This test ran 1 times: 1 passed.
This test used 83 tokens
用量数据是否完整

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

Passed
Test details
This test ran 1 times: 1 passed.
This test used 38 tokens
复测一致性

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

Passed
Test details
This test ran 2 times: 2 passed.
This test used 72 tokens
Qwen 中文和视觉边界

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 94 tokens
Qwen 中文和视觉边界

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

Passed
Test details
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.

Passed
Test details
This test ran 1 times: 1 passed.
This test used 99 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 81 tokens
Deep model test: family-specific boundary

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

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

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

Passed
Test details
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 上下文能力实测

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

Passed
Test details
This test ran 1 times: 1 passed.
Content length used: 8K
This test used 5.1K tokens
16K 上下文能力实测

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

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

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

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

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

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

128K 长度的内容没能稳定读完,这次就记到这里为止。

Needs review
Test details
This test ran 1 times: 1 need attention.
Why it failed: API service error
Content length used: 128K

Reviews

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

发表评论

编辑器加载中…