Is qwen3.5-plus genuine? Quick check result

Report ID MZZR20260703063220CB4741Generated at 2026/07/03 14:32

Matched

qwen3.5-plus 本次快速验真结果：Matched（92/100）。主要问题：这家的接口当时有故障。

92Model consistency score

主要问题：这家的接口当时有故障。

Tested byMozhenzhen

Tested modelQwen3.5 Plus

ProvidersConeverse AI

Requests98

Duration3 min 36 sec

Identity verdictVerified

ReferenceMozhenzhen's own test standard

This call did not complete

Reason for failure

The provider’s API returned a service error at the time.

What to do

Try again later. Contact the provider if this persists.

Token usage check

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

Reported usage164.7KThe actual usage reported by the API; this page goes by it.Estimated usage1.3MEstimated from this test's requests.Deviation88% 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 rate0.0%

No cache discount this time

The endpoint reported real usage but no cached part; this seller may not offer cache pricing, or nothing hit the cache this time.

Usage this run15.3KCached tokens0Non-cached tokens15.3KAverage per run3.1K

Usage reportedReportedCache billingDid not happenResultNeeds attention

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.

6 tiers

Verified up to 128K

256K 需要关注，原因：接口服务异常。

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

Current guidance

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

Matched92/100

主要问题：这家的接口当时有故障。

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

No deductions

Does the most basic call work25 / 25

No deductions

Is it the model it claims to be25 / 25

No deductions

Will it keep working12 / 20

这家的接口当时有故障（模型身份自报） -8

Test details

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

10 checks

Model list visibility

qwen3.5-plus 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

问它自己是什么模型，看答案对不对。有几次没对上。

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: API service error

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

针对这个模型再做一项专门检测。有几次没对上。

Needs review

Test details

This test ran 5 times: 5 passed, 1 need attention.
Why it failed: Cache-usage fields were not observable
This test used 15.3K tokens

8K 上下文能力实测

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

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 8K
This test used 5.5K tokens

16K 上下文能力实测

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

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 16K
This test used 10.4K tokens

32K 上下文能力实测

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

Passed

Test details

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

64K 上下文能力实测

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

Passed

Test details

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

128K 上下文能力实测

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

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 128K
This test used 75.8K tokens

256K 上下文能力实测

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

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: API service error
Content length used: 256K

Reviews

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

发表评论

Before you buy AI, check Mozhenzhen

Scan to view reportOpen full report

Mozhenzhen verification report · Measured with real calls

Is qwen3.5-plus genuine? Quick check result

Report ID:MZZR20260703063220CB4741Generated at：2026/07/03 14:32

Provider details AI model details

Model consistency score

Matched

qwen3.5-plus 本次快速验真结果：Matched（92/100）。主要问题：这家的接口当时有故障。

Tested byMozhenzhen

Tested modelQwen3.5 Plus

ProvidersConeverse AI

Requests98

Duration4 min

Identity verdictVerified

ReferenceMozhenzhen's own test standard

This call did not complete

Reason for failure

The provider’s API returned a service error at the time.

What to do

Try again later. Contact the provider if this persists.

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 rate0.0%

No cache discount this time

The endpoint reported real usage but no cached part; this seller may not offer cache pricing, or nothing hit the cache this time.

Usage this run15.3KCached tokens0Non-cached tokens15.3KAverage per run3.1K

Usage reportedReportedCache billingDid not happenResultNeeds attention

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.

6 tiers

Verified up to 128K

256K 需要关注，原因：接口服务异常。

Current guidance

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

Matched92/100

主要问题：这家的接口当时有故障。

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

No deductions

Does the most basic call work25 / 25

No deductions

Is it the model it claims to be25 / 25

No deductions

Will it keep working12 / 20

这家的接口当时有故障（模型身份自报） -8

Test details

Expand any row for details; anything private has been removed

10 checks

Model list visibility

qwen3.5-plus 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

问它自己是什么模型，看答案对不对。有几次没对上。

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: API service error

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

针对这个模型再做一项专门检测。有几次没对上。

Needs review

Test details

This test ran 5 times: 5 passed, 1 need attention.
Why it failed: Cache-usage fields were not observable
This test used 15.3K tokens

8K 上下文能力实测

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

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 8K
This test used 5.5K tokens

16K 上下文能力实测

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

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 16K
This test used 10.4K tokens

32K 上下文能力实测

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

Passed

Test details

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

64K 上下文能力实测

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

Passed

Test details

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

128K 上下文能力实测

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

Passed

Test details

This test ran 1 times: 1 passed.
Content length used: 128K
This test used 75.8K tokens

256K 上下文能力实测

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

Needs review

Test details

This test ran 1 times: 1 need attention.
Why it failed: API service error
Content length used: 256K

Reviews

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