Is qwen3.7-plus genuine? Quick check result

Report ID MZZR202607220916448F7D7AGenerated at 2026/07/22 17:16

High risk

qwen3.7-plus 本次快速验真结果：High risk（40/100）。主要问题：接口根本调不通；有检测项没Passed。

40Model consistency score

主要问题：接口根本调不通；有检测项没Passed。

Tested byMozhenzhen

Tested modelQwen3.7 Plus

Providersxinlicloud.top

Requests10

Duration2 sec

Identity verdictNot verified

ReferenceMozhenzhen's own test standard

This call did not complete

Reason for failure

The basic call returned no recognizable answer. The available records cannot establish a specific cause.

What to do

Check the endpoint address, key and model permissions. If this persists, give the provider the report ID for troubleshooting.

Token usage check

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

Estimated usage1.7MThe API did not report actual usage; the estimate is shown.DeviationNoneThe API did not report actual usage; only the estimate is shown.Usage checkEstimate onlyFigures 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 0 request

Share billed at the cache rate--

No usage record

This provider's endpoint does not report usage reliably; check it against your bill.

Usage this run0Cached tokens0Non-cached tokens0Average per run--

Usage reportedNot reportedCache billingDid not happenResultNormal

Cache share by testThis is only the cache share the endpoint reported; the real discount is on the bill

No per-test records are available; only the aggregate result is shown.

Long-context test

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

7 tiers

No stable result this time

The basic call failed (Basic API call unavailable), so the long-context add-on was skipped.

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

Current guidance

The basic call failed (Basic API call unavailable), so the long-context add-on was skipped.

Results for this test

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

Scoring breakdown

High risk40/100

主要问题：接口根本调不通；有检测项没Passed。

Can you call it, and is the model listed15 / 30

接口根本调不通（基础调用探针） -15

Does the most basic call work0 / 25

接口根本调不通（基础调用探针） -25

Is it the model it claims to be17 / 25

接口根本调不通（基础调用探针） -8

Will it keep working8 / 20

接口根本调不通（基础调用探针） -10有检测项没Passed -2

Test details

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

11 checks

Model list visibility

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

Passed

Test details

This test ran 9 times; result: Passed.

Basic call probe

基础调用未成功，可能是 Key 权限、额度、接口路径或模型能力类型问题。

Failed

Test details

This test ran 1 times; result: Failed.
Why it failed: Basic API call unavailable

Model self-identification

问它自己是什么模型，看答案对不对。基础调用探针Failed，后续题包已跳过，避免继续消耗 token。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: 基础调用探针Failed，后续题包已跳过，避免继续消耗 token。

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

针对这个模型再做一项专门检测。基础调用探针Failed，专项检测已跳过，避免继续消耗 token。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: 基础调用探针Failed，专项检测已跳过，避免继续消耗 token。

32K 上下文能力实测

针对这个模型再做一项专门检测。基础调用探针Failed，专项检测已跳过，避免继续消耗 token。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: 基础调用探针Failed，专项检测已跳过，避免继续消耗 token。

64K 上下文能力实测

针对这个模型再做一项专门检测。基础调用探针Failed，专项检测已跳过，避免继续消耗 token。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: 基础调用探针Failed，专项检测已跳过，避免继续消耗 token。

100K 上下文能力实测

针对这个模型再做一项专门检测。基础调用探针Failed，专项检测已跳过，避免继续消耗 token。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: 基础调用探针Failed，专项检测已跳过，避免继续消耗 token。

200K 上下文能力实测

针对这个模型再做一项专门检测。基础调用探针Failed，专项检测已跳过，避免继续消耗 token。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: 基础调用探针Failed，专项检测已跳过，避免继续消耗 token。

400K 上下文能力实测

针对这个模型再做一项专门检测。基础调用探针Failed，专项检测已跳过，避免继续消耗 token。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: 基础调用探针Failed，专项检测已跳过，避免继续消耗 token。

800K 上下文能力实测

针对这个模型再做一项专门检测。基础调用探针Failed，专项检测已跳过，避免继续消耗 token。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: 基础调用探针Failed，专项检测已跳过，避免继续消耗 token。

1M 上下文能力实测

针对这个模型再做一项专门检测。基础调用探针Failed，专项检测已跳过，避免继续消耗 token。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: 基础调用探针Failed，专项检测已跳过，避免继续消耗 token。

Reviews

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

发表评论

Before you buy AI, check Mozhenzhen

Scan to view reportOpen full report

Mozhenzhen verification report · Measured with real calls

Is qwen3.7-plus genuine? Quick check result

Report ID:MZZR202607220916448F7D7AGenerated at：2026/07/22 17:16

Provider details AI model details

Model consistency score

High risk

qwen3.7-plus 本次快速验真结果：High risk（40/100）。主要问题：接口根本调不通；有检测项没Passed。

Tested byMozhenzhen

Tested modelQwen3.7 Plus

Providersxinlicloud.top

Requests10

Duration2 sec

Identity verdictNot verified

ReferenceMozhenzhen's own test standard

This call did not complete

Reason for failure

The basic call returned no recognizable answer. The available records cannot establish a specific cause.

What to do

Check the endpoint address, key and model permissions. If this persists, give the provider the report ID for troubleshooting.

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 0 request

Share billed at the cache rate--

No usage record

This provider's endpoint does not report usage reliably; check it against your bill.

Usage this run0Cached tokens0Non-cached tokens0Average per run--

Usage reportedNot reportedCache billingDid not happenResultNormal

Cache share by testThis is only the cache share the endpoint reported; the real discount is on the bill

No per-test records are available; only the aggregate result is shown.

Long-context test

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

7 tiers

No stable result this time

The basic call failed (Basic API call unavailable), so the long-context add-on was skipped.

Current guidance

The basic call failed (Basic API call unavailable), so the long-context add-on was skipped.

Results for this test

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

Scoring breakdown

High risk40/100

主要问题：接口根本调不通；有检测项没Passed。

Can you call it, and is the model listed15 / 30

接口根本调不通（基础调用探针） -15

Does the most basic call work0 / 25

接口根本调不通（基础调用探针） -25

Is it the model it claims to be17 / 25

接口根本调不通（基础调用探针） -8

Will it keep working8 / 20

接口根本调不通（基础调用探针） -10有检测项没Passed -2

Test details

Expand any row for details; anything private has been removed

11 checks

Model list visibility

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

Passed

Test details

This test ran 9 times; result: Passed.

Basic call probe

基础调用未成功，可能是 Key 权限、额度、接口路径或模型能力类型问题。

Failed

Test details

This test ran 1 times; result: Failed.
Why it failed: Basic API call unavailable

Model self-identification

问它自己是什么模型，看答案对不对。基础调用探针Failed，后续题包已跳过，避免继续消耗 token。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: 基础调用探针Failed，后续题包已跳过，避免继续消耗 token。

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

针对这个模型再做一项专门检测。基础调用探针Failed，专项检测已跳过，避免继续消耗 token。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: 基础调用探针Failed，专项检测已跳过，避免继续消耗 token。

32K 上下文能力实测

针对这个模型再做一项专门检测。基础调用探针Failed，专项检测已跳过，避免继续消耗 token。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: 基础调用探针Failed，专项检测已跳过，避免继续消耗 token。

64K 上下文能力实测

针对这个模型再做一项专门检测。基础调用探针Failed，专项检测已跳过，避免继续消耗 token。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: 基础调用探针Failed，专项检测已跳过，避免继续消耗 token。

100K 上下文能力实测

针对这个模型再做一项专门检测。基础调用探针Failed，专项检测已跳过，避免继续消耗 token。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: 基础调用探针Failed，专项检测已跳过，避免继续消耗 token。

200K 上下文能力实测

针对这个模型再做一项专门检测。基础调用探针Failed，专项检测已跳过，避免继续消耗 token。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: 基础调用探针Failed，专项检测已跳过，避免继续消耗 token。

400K 上下文能力实测

针对这个模型再做一项专门检测。基础调用探针Failed，专项检测已跳过，避免继续消耗 token。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: 基础调用探针Failed，专项检测已跳过，避免继续消耗 token。

800K 上下文能力实测

针对这个模型再做一项专门检测。基础调用探针Failed，专项检测已跳过，避免继续消耗 token。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: 基础调用探针Failed，专项检测已跳过，避免继续消耗 token。

1M 上下文能力实测

针对这个模型再做一项专门检测。基础调用探针Failed，专项检测已跳过，避免继续消耗 token。

Skipped

Test details

Result of this test: Skipped.
Why it was not tested: 基础调用探针Failed，专项检测已跳过，避免继续消耗 token。

Reviews

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