UndeterminedBelow decision threshold
Identity could not be determined this time
行为特征与已收录的官方型号均不够接近，本次无法判定。
Brand consistency48/100
Model match score (gpt-5.6-sol)0/100
Checks8/17 Passed
- Providers
- cleanapis.com
- Claimed model
- gpt-5.6-sol
- Plan
- Full check
- Reference
- 101 official models
- Requests
- 17
- Duration
- 6 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AValidIndependent sample B采样 BInvalidIndependent sample C采样 CValidReference101 official models · 2/3 Valid
Answer by answer2 answers: 0 match gpt-5.6-sol；another 2 match no model clearly on their own
Similarity to official modelsTop 5
These answers are not close to any official model on file. The percentages below only rank them against each other and do not mean the answers resemble any of these models.
- gpt-6-sol37%
- doubao-seed-2-1-turbo23%
- qwen3.6-max-preview9%
- gpt-6-astra5%
- qwen3.7-plus4%
02Test details
17 items · 8 passed · 9 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 gpt-5.6-sol |
| 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 | 2 / 3 valid | Some samples could not be used for comparison |
| C-02 | Brand consistency | Pending review | Brand match score 48; below the decision threshold |
| C-03 | Model consistency | Undetermined | Model match score 0; below the decision threshold |
| C-04 | Cross-brand swap check | Cannot be identified | Not close to any official model on file, so the substitute's vendor cannot be told |
| Billing & capabilities | |||
| D-01 | Cache billing | Does not work | The vendor offers a cache price for this model, but none of the repeated requests were billed at it. |
| D-02 | Context length | 128K passed | Read in full up to 128K; 400K failed: 接口返回 HTTP 429. |
| D-03 | Streaming output | Not supported | 流式请求未成功（接口返回 HTTP 429） |
| D-04 | Tool use | Not supported | 带工具的请求未成功（接口返回 HTTP 429） |
| D-05 | Structured output | Not supported | 结构化输出请求未成功（接口返回 HTTP 429） |
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 ratio0.0%
Does not work
The vendor offers a cache price for this model, but none of the repeated requests were billed at it.
Usage this run27.2KCached tokens0Non-cached tokens27.2KAverage per run5.4K
Usage reportedReportedCache billingDid not happenResultDoes not work
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: 接口返回 HTTP 429.
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 · 30.6K received
- 128KRead in full · 120.7K received
- 400K接口返回 HTTP 429
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage188.6KThe actual usage reported by the API; this page goes by it.Estimated usage1.3M-1.8MEstimated 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.
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
gpt-5.6-sol verification report
UndeterminedBelow decision threshold
Identity could not be determined this time
行为特征与已收录的官方型号均不够接近，本次无法判定。
Brand consistency48/100
Model match score (gpt-5.6-sol)0/100
Checks8/17 Passed
- Providers
- cleanapis.com
- Claimed model
- gpt-5.6-sol
- Plan
- Full check
- Reference
- 101 official models
- Requests
- 17
- Duration
- 6 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AValidIndependent sample B采样 BInvalidIndependent sample C采样 CValidReference101 official models · 2/3 Valid
Answer by answer2 answers: 0 match gpt-5.6-sol；another 2 match no model clearly on their own
Similarity to official modelsTop 5
These answers are not close to any official model on file. The percentages below only rank them against each other and do not mean the answers resemble any of these models.
- gpt-6-sol37%
- doubao-seed-2-1-turbo23%
- qwen3.6-max-preview9%
- gpt-6-astra5%
- qwen3.7-plus4%
02Test details
17 items · 8 passed · 9 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 gpt-5.6-sol |
| 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 | 2 / 3 valid | Some samples could not be used for comparison |
| C-02 | Brand consistency | Pending review | Brand match score 48; below the decision threshold |
| C-03 | Model consistency | Undetermined | Model match score 0; below the decision threshold |
| C-04 | Cross-brand swap check | Cannot be identified | Not close to any official model on file, so the substitute's vendor cannot be told |
| Billing & capabilities | |||
| D-01 | Cache billing | Does not work | The vendor offers a cache price for this model, but none of the repeated requests were billed at it. |
| D-02 | Context length | 128K passed | Read in full up to 128K; 400K failed: 接口返回 HTTP 429. |
| D-03 | Streaming output | Not supported | 流式请求未成功（接口返回 HTTP 429） |
| D-04 | Tool use | Not supported | 带工具的请求未成功（接口返回 HTTP 429） |
| D-05 | Structured output | Not supported | 结构化输出请求未成功（接口返回 HTTP 429） |
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 ratio0.0%
Does not work
The vendor offers a cache price for this model, but none of the repeated requests were billed at it.
Usage this run27.2KCached tokens0Non-cached tokens27.2KAverage per run5.4K
Usage reportedReportedCache billingDid not happenResultDoes not work
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: 接口返回 HTTP 429.
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 · 30.6K received
- 128KRead in full · 120.7K received
- 400K接口返回 HTTP 429
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage188.6KThe actual usage reported by the API; this page goes by it.Estimated usage1.3M-1.8MEstimated 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.
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.