Identity confirmedModel verified
Confirmed as the official qwen3.8-flash
Behavior matches the official qwen3.8-flash.
Brand consistency97/100
Model match score (qwen3.8-flash)96/100
Checks15/17 Passed
- Providers
- opencode
- Claimed model
- qwen3.8-flash
- Plan
- Full check
- Reference
- 102 official models
- Requests
- 20
- Duration
- 15 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AInvalidIndependent sample B采样 BValidIndependent sample C采样 CInvalidIndependent sample D采样 DValidIndependent sample E采样 EValidIndependent sample F采样 FValidReference102 official models · 4/6 Valid
Answer by answer4 answers: 2 match qwen3.8-flash；another 1 look more like doubao-seed-2-0-lite；another 1 match no model clearly on their own
Similarity to official modelsTop 5
- qwen3.8-flashClaimed model96%
- gpt-5.53%
- qwen3.8-max<1%
- doubao-seed-2-1-pro<1%
- gpt-5.3-codex<1%
02Test details
17 items · 15 passed · 2 notes · 0 failed| No. | Check | Result | Methodology |
|---|---|---|---|
| Connectivity & auth | |||
| A-01 | Endpoint reachable | Passed | The endpoint responds normally |
| A-02 | Key authentication | Passed | API key is valid and allowed to make calls |
| A-03 | Model on sale | Passed | The model list includes qwen3.8-flash |
| API conformance | |||
| B-01 | Basic call | Passed | Returns the expected content as instructed |
| B-02 | Response structure | Meets the spec | All OpenAI-compatible fields are present |
| B-03 | Model ID echoed back | Match | The model ID in the response matches the request |
| B-04 | Usage record | Complete and consistent | Input, output and total are all present, and the total equals the sum |
| B-05 | Output cleanliness | Nothing added | No inserted ads, watermarks or extra notes found |
| Identity check | |||
| C-01 | Independent sampling | 4 / 6 valid | 首轮未能判定，已追加一轮；部分采样结果不可用于比对 |
| C-02 | Brand consistency | Match | Behavior belongs to the Qwen family; brand match score 97 |
| C-03 | Model consistency | Match | 与官方 qwen3.8-flash 吻合，型号一致度 96 |
| C-04 | Cross-brand swap check | None found | Similarity to other brands' models totals under 5% |
| Billing & capabilities | |||
| D-01 | Cache billing | Cache billing works | On average 93% of repeated requests were billed at the cache price. |
| D-02 | Context length | 128K passed | Read in full up to 128K; 400K failed: The endpoint returned no result. |
| D-03 | Streaming output | Normal | Streamed content is complete |
| D-04 | Tool use | Supported | Returns the correct function name and arguments |
| D-05 | Structured output | Supported | Returned in the required JSON structure |
Cache billing check
The same long content was sent 5 times: the 1st is billed at the regular price, and from the 2nd on the repeated part should be billed at the cache price.
Cache billing ratio92.6%
Cache billing works
On average 93% of repeated requests were billed at the cache price.
Usage this run29.3KCached tokens21.5KNon-cached tokens7.7KAverage per run5.9K
Usage reportedReportedCache billingHappenedResultCache billing works
Cache share by testThis is only the cache share the endpoint reported; the real discount is on the bill
Context length check
Long documents are sent tier by tier to check whether the whole document is read.
Verified up to 128K
Read in full up to 128K; 400K failed: The endpoint returned no result.
Reference windowVerified up to 128KThe model center has no reference context window for this model yet.Tested context lengths32K / 128K / 400KTested from short to long, stopping at the first failure.
- 32KRead in full · 31.8K received
- 128KRead in full · 121.8K received
- 400KThe endpoint returned no result
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage231.3KThe actual usage reported by the API; this page goes by it.Estimated usage1.3M-1.8MEstimated from this test's requests.Deviation82% 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.
Method: independent samples from the tested endpoint are compared against reference samples collected from official channels; billing, context and capability items come from real calls. API keys, request bodies and raw model output are not stored.
This report reflects the endpoint at the time of testing.
Post an anonymous comment
Before you buy AI, check MozhenzhenScan to view reportOpen full report
Mozhenzhen verification report · Measured with real calls
qwen3.8-flash verification report
Identity confirmedModel verified
Confirmed as the official qwen3.8-flash
Behavior matches the official qwen3.8-flash.
Brand consistency97/100
Model match score (qwen3.8-flash)96/100
Checks15/17 Passed
- Providers
- opencode
- Claimed model
- qwen3.8-flash
- Plan
- Full check
- Reference
- 102 official models
- Requests
- 20
- Duration
- 15 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AInvalidIndependent sample B采样 BValidIndependent sample C采样 CInvalidIndependent sample D采样 DValidIndependent sample E采样 EValidIndependent sample F采样 FValidReference102 official models · 4/6 Valid
Answer by answer4 answers: 2 match qwen3.8-flash；another 1 look more like doubao-seed-2-0-lite；another 1 match no model clearly on their own
Similarity to official modelsTop 5
- qwen3.8-flashClaimed model96%
- gpt-5.53%
- qwen3.8-max<1%
- doubao-seed-2-1-pro<1%
- gpt-5.3-codex<1%
02Test details
17 items · 15 passed · 2 notes · 0 failed| No. | Check | Result | Methodology |
|---|---|---|---|
| Connectivity & auth | |||
| A-01 | Endpoint reachable | Passed | The endpoint responds normally |
| A-02 | Key authentication | Passed | API key is valid and allowed to make calls |
| A-03 | Model on sale | Passed | The model list includes qwen3.8-flash |
| API conformance | |||
| B-01 | Basic call | Passed | Returns the expected content as instructed |
| B-02 | Response structure | Meets the spec | All OpenAI-compatible fields are present |
| B-03 | Model ID echoed back | Match | The model ID in the response matches the request |
| B-04 | Usage record | Complete and consistent | Input, output and total are all present, and the total equals the sum |
| B-05 | Output cleanliness | Nothing added | No inserted ads, watermarks or extra notes found |
| Identity check | |||
| C-01 | Independent sampling | 4 / 6 valid | 首轮未能判定，已追加一轮；部分采样结果不可用于比对 |
| C-02 | Brand consistency | Match | Behavior belongs to the Qwen family; brand match score 97 |
| C-03 | Model consistency | Match | 与官方 qwen3.8-flash 吻合，型号一致度 96 |
| C-04 | Cross-brand swap check | None found | Similarity to other brands' models totals under 5% |
| Billing & capabilities | |||
| D-01 | Cache billing | Cache billing works | On average 93% of repeated requests were billed at the cache price. |
| D-02 | Context length | 128K passed | Read in full up to 128K; 400K failed: The endpoint returned no result. |
| D-03 | Streaming output | Normal | Streamed content is complete |
| D-04 | Tool use | Supported | Returns the correct function name and arguments |
| D-05 | Structured output | Supported | Returned in the required JSON structure |
Cache billing check
The same long content was sent 5 times: the 1st is billed at the regular price, and from the 2nd on the repeated part should be billed at the cache price.
Cache billing ratio92.6%
Cache billing works
On average 93% of repeated requests were billed at the cache price.
Usage this run29.3KCached tokens21.5KNon-cached tokens7.7KAverage per run5.9K
Usage reportedReportedCache billingHappenedResultCache billing works
Cache share by testThis is only the cache share the endpoint reported; the real discount is on the bill
Context length check
Long documents are sent tier by tier to check whether the whole document is read.
Verified up to 128K
Read in full up to 128K; 400K failed: The endpoint returned no result.
Reference windowVerified up to 128KThe model center has no reference context window for this model yet.Tested context lengths32K / 128K / 400KTested from short to long, stopping at the first failure.
- 32KRead in full · 31.8K received
- 128KRead in full · 121.8K received
- 400KThe endpoint returned no result
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage231.3KThe actual usage reported by the API; this page goes by it.Estimated usage1.3M-1.8MEstimated from this test's requests.Deviation82% 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.
Method: independent samples from the tested endpoint are compared against reference samples collected from official channels; billing, context and capability items come from real calls. API keys, request bodies and raw model output are not stored.
This report reflects the endpoint at the time of testing.