Identity mismatchSubstitution detected
Does not match the claimed model gpt-5.6-sol
行为特征与官方 gpt-5.6-sol 明显不符。
Brand consistency55/100
Model match score (gpt-5.6-sol)0/100
Checks9/17 Passed
- Providers
- CodeCraft API
- Claimed model
- gpt-5.6-sol
- Plan
- Full check
- Reference
- 101 official models
- Requests
- 18
- Duration
- 1 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AValidIndependent sample B采样 BValidIndependent sample C采样 CValidIndependent sample D采样 DValidIndependent sample E采样 EValidIndependent sample F采样 FValidReference101 official models · 6/6 Valid
Answer by answer6 answers: 0 match gpt-5.6-sol；another 6 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-532%
- qwen3-max31%
- gpt-6-sol10%
- gpt-5.59%
- deepseek-v4-pro4%
02Test details
17 items · 9 passed · 7 notes · 1 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 | 6 / 6 valid | 首轮未能判定，已追加一轮；独立采样均可用于比对 |
| C-02 | Brand consistency | Pending review | Brand match score 55; below the decision threshold |
| C-03 | Model consistency | Mismatch | 型号一致度 0，与官方 gpt-5.6-sol 明显不同 |
| 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 | 32K failed | 32K 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 run21.6KCached tokens0Non-cached tokens21.6KAverage per run4.3K
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.
Boundary at 32K
32K failed: 接口返回 HTTP 429.
Reference windowHighest tested: 32KThe model center has no reference context window for this model yet.Tested context lengths32KTested from short to long, stopping at the first failure.
- 32K接口返回 HTTP 429
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage49.0KThe actual usage reported by the API; this page goes by it.Estimated usage1.3M-1.8MEstimated from this test's requests.Deviation96% 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
Identity mismatchSubstitution detected
Does not match the claimed model gpt-5.6-sol
行为特征与官方 gpt-5.6-sol 明显不符。
Brand consistency55/100
Model match score (gpt-5.6-sol)0/100
Checks9/17 Passed
- Providers
- CodeCraft API
- Claimed model
- gpt-5.6-sol
- Plan
- Full check
- Reference
- 101 official models
- Requests
- 18
- Duration
- 1 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AValidIndependent sample B采样 BValidIndependent sample C采样 CValidIndependent sample D采样 DValidIndependent sample E采样 EValidIndependent sample F采样 FValidReference101 official models · 6/6 Valid
Answer by answer6 answers: 0 match gpt-5.6-sol；another 6 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-532%
- qwen3-max31%
- gpt-6-sol10%
- gpt-5.59%
- deepseek-v4-pro4%
02Test details
17 items · 9 passed · 7 notes · 1 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 | 6 / 6 valid | 首轮未能判定，已追加一轮；独立采样均可用于比对 |
| C-02 | Brand consistency | Pending review | Brand match score 55; below the decision threshold |
| C-03 | Model consistency | Mismatch | 型号一致度 0，与官方 gpt-5.6-sol 明显不同 |
| 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 | 32K failed | 32K 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 run21.6KCached tokens0Non-cached tokens21.6KAverage per run4.3K
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.
Boundary at 32K
32K failed: 接口返回 HTTP 429.
Reference windowHighest tested: 32KThe model center has no reference context window for this model yet.Tested context lengths32KTested from short to long, stopping at the first failure.
- 32K接口返回 HTTP 429
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage49.0KThe actual usage reported by the API; this page goes by it.Estimated usage1.3M-1.8MEstimated from this test's requests.Deviation96% 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.