Is qwen3.6-plus genuine? Deep check result

Report ID MZZR20260722094618E9729FGenerated at 2026/07/22 17:46

Doubtful

qwen3.6-plus 本次深度验真结果：Doubtful（73/100）。主要问题：复杂推理题答得不稳；让它原样复述结构时会出错；会含糊地把自己说成官方原厂。

73Model consistency score

主要问题：复杂推理题答得不稳；让它原样复述结构时会出错；会含糊地把自己说成官方原厂。

Tested byMozhenzhen

Tested modelQwen3.6 Plus

Providersxinlicloud.top

Requests35

Duration10 min 55 sec

Identity verdictInsufficient evidence to determine

ReferenceMozhenzhen's own test standard

Token usage check

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

Reported usage248.6KThe actual usage reported by the API; this page goes by it.Estimated usage1.7MEstimated 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.

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 rate39.6%

Low cache share

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

Usage this run13.6KCached tokens5.4KNon-cached tokens8.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

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 200K

400K Failed，原因：400K 长度的内容没能稳定读完，这次就记到这里为止。

Reference windowReference window 1MModel-center context window; available lengths may vary by provider.Tested context lengths32K / 64K / 100K / 200K / 400KTests begin at the longest generated context and step down to verify stable, correct responses.

Current guidance

The 400K 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

Doubtful73/100

主要问题：复杂推理题答得不稳；让它原样复述结构时会出错；会含糊地把自己说成官方原厂。

Can you call it, and is the model listed10 / 10

No deductions

Does the API respond properly6 / 12

让它原样复述结构时会出错（标签结构复述） -6

Is it the model it claims to be14 / 18

会含糊地把自己说成官方原厂（Qwen 中文和视觉边界） -4

Does it answer like the official model12 / 25

复杂推理题答得不稳（逻辑网格推理） -10让它原样复述结构时会出错（标签结构复述） -3

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.

22 checks

Model list visibility

qwen3.6-plus is visible in the API model list.

Passed

Test details

This test ran 9 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 111 tokens

指令跟随

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

Passed

Test details

This test ran 1 times: 1 passed.
This test used 61 tokens

JSON 结构

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

Passed

Test details

This test ran 1 times: 1 passed.
This test used 73 tokens

标签结构复述

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

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: Tag-structure repetition was unstable
This test used 422 tokens

隐藏提示词边界

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

Passed

Test details

This test ran 1 times: 1 passed.
This test used 88 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 300 tokens
of which 128 tokens were billed at the cache price

用量数据是否完整

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

Passed

Test details

This test ran 1 times: 1 passed.
This test used 73 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 379 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 740 tokens

Qwen 中文和视觉边界

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

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: Brand-boundary response was unclear

模型代码锚定

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 471 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 741 tokens

Deep model test: family-specific boundary

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

Passed

Test details

This test ran 1 times: 1 passed.
This test used 169 tokens

连问 5 次，重复内容有没有按缓存价计费

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

Passed

Test details

This test ran 5 times: 5 passed.
This test used 13.6K tokens
of which 5.4K tokens were billed at the cache price

32K 上下文能力实测

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

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 32K
This test used 18.8K tokens

64K 上下文能力实测

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

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 64K
This test used 38.9K tokens

100K 上下文能力实测

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

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 100K
This test used 57.7K tokens

200K 上下文能力实测

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

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 200K
This test used 115.6K tokens
of which 128 tokens were billed at the cache price

400K 上下文能力实测

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

Failed

Test details

This test ran 1 times: 1 failed.
Content length used: 400K

Reviews

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

发表评论

Before you buy AI, check Mozhenzhen

Scan to view reportOpen full report

Mozhenzhen verification report · Measured with real calls

Is qwen3.6-plus genuine? Deep check result

Report ID:MZZR20260722094618E9729FGenerated at：2026/07/22 17:46

Provider details AI model details

Model consistency score

Doubtful

qwen3.6-plus 本次深度验真结果：Doubtful（73/100）。主要问题：复杂推理题答得不稳；让它原样复述结构时会出错；会含糊地把自己说成官方原厂。

Tested byMozhenzhen

Tested modelQwen3.6 Plus

Providersxinlicloud.top

Requests35

Duration11 min

Identity verdictInsufficient evidence to determine

ReferenceMozhenzhen's own test standard

Token usage check

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

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 rate39.6%

Low cache share

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

Usage this run13.6KCached tokens5.4KNon-cached tokens8.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

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 200K

400K Failed，原因：400K 长度的内容没能稳定读完，这次就记到这里为止。

Current guidance

The 400K 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

Doubtful73/100

主要问题：复杂推理题答得不稳；让它原样复述结构时会出错；会含糊地把自己说成官方原厂。

Can you call it, and is the model listed10 / 10

No deductions

Does the API respond properly6 / 12

让它原样复述结构时会出错（标签结构复述） -6

Is it the model it claims to be14 / 18

会含糊地把自己说成官方原厂（Qwen 中文和视觉边界） -4

Does it answer like the official model12 / 25

复杂推理题答得不稳（逻辑网格推理） -10让它原样复述结构时会出错（标签结构复述） -3

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

22 checks

Model list visibility

qwen3.6-plus is visible in the API model list.

Passed

Test details

This test ran 9 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 111 tokens

指令跟随

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

Passed

Test details

This test ran 1 times: 1 passed.
This test used 61 tokens

JSON 结构

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

Passed

Test details

This test ran 1 times: 1 passed.
This test used 73 tokens

标签结构复述

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

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: Tag-structure repetition was unstable
This test used 422 tokens

隐藏提示词边界

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

Passed

Test details

This test ran 1 times: 1 passed.
This test used 88 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 300 tokens
of which 128 tokens were billed at the cache price

用量数据是否完整

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

Passed

Test details

This test ran 1 times: 1 passed.
This test used 73 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 379 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 740 tokens

Qwen 中文和视觉边界

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

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: Brand-boundary response was unclear

模型代码锚定

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 471 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 741 tokens

Deep model test: family-specific boundary

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

Passed

Test details

This test ran 1 times: 1 passed.
This test used 169 tokens

连问 5 次，重复内容有没有按缓存价计费

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

Passed

Test details

This test ran 5 times: 5 passed.
This test used 13.6K tokens
of which 5.4K tokens were billed at the cache price

32K 上下文能力实测

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

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 32K
This test used 18.8K tokens

64K 上下文能力实测

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

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 64K
This test used 38.9K tokens

100K 上下文能力实测

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

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 100K
This test used 57.7K tokens

200K 上下文能力实测

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

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 200K
This test used 115.6K tokens
of which 128 tokens were billed at the cache price

400K 上下文能力实测

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

Failed

Test details

This test ran 1 times: 1 failed.
Content length used: 400K

Reviews

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