A newer report is availableThis report has been superseded by a later retest. View the latest report。
Identity confirmedModel verified
Confirmed as the official gpt-5.6-sol
Behavior matches the official gpt-5.6-sol.
Brand consistency100/100
Model match score (gpt-5.6-sol)99/100
Checks14/17 Passed
- Providers
- devcorp.me
- Claimed model
- gpt-5.6-sol
- Plan
- Full check
- Reference
- 102 official models
- Requests
- 18
- Duration
- 4 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AValidIndependent sample B采样 BInvalidIndependent sample C采样 CValidReference102 official models · 2/3 Valid
Answer by answer2 answers: 2 match gpt-5.6-sol
Similarity to official modelsTop 5
- gpt-5.6-solClaimed model99%
- gpt-5.5<1%
- gpt-6-luna<1%
- gpt-6-sol<1%
- gpt-5.6-terra<1%
02Test details
17 items · 14 passed · 3 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 | Mismatch | Requested gpt-5.6-sol; the response says SaaSolVip |
| 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 | Match | Behavior belongs to the OpenAI GPT family; brand match score 100 |
| C-03 | Model consistency | Match | 与官方 gpt-5.6-sol 吻合，型号一致度 99 |
| C-04 | Cross-brand swap check | None found | Similarity to other brands' models totals under 1% |
| Billing & capabilities | |||
| D-01 | Cache billing | Cache billing works | On average 100% of repeated requests were billed at the cache price. |
| D-02 | Context length | 400K passed | Read in full up to 400K; 1M failed: 接口返回 HTTP 400. |
| 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 ratio100.0%
Cache billing works
On average 100% of repeated requests were billed at the cache price.
Usage this run34.3KCached tokens27.4KNon-cached tokens6.9KAverage per run6.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 400K
Read in full up to 400K; 1M failed: 接口返回 HTTP 400.
Reference windowVerified up to 400KThe model center has no reference context window for this model yet.Tested context lengths32K / 128K / 400K / 1MTested from short to long, stopping at the first failure.
- 32KRead in full · 34.5K received
- 128KRead in full · 121.0K received
- 400KRead in full · 368K received
- 1M接口返回 HTTP 400
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage575.3KThe actual usage reported by the API; this page goes by it.Estimated usage1.3M-1.8MEstimated from this test's requests.Deviation55% 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
A newer report is availableThis report has been superseded by a later retest. View the latest report。
Identity confirmedModel verified
Confirmed as the official gpt-5.6-sol
Behavior matches the official gpt-5.6-sol.
Brand consistency100/100
Model match score (gpt-5.6-sol)99/100
Checks14/17 Passed
- Providers
- devcorp.me
- Claimed model
- gpt-5.6-sol
- Plan
- Full check
- Reference
- 102 official models
- Requests
- 18
- Duration
- 4 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AValidIndependent sample B采样 BInvalidIndependent sample C采样 CValidReference102 official models · 2/3 Valid
Answer by answer2 answers: 2 match gpt-5.6-sol
Similarity to official modelsTop 5
- gpt-5.6-solClaimed model99%
- gpt-5.5<1%
- gpt-6-luna<1%
- gpt-6-sol<1%
- gpt-5.6-terra<1%
02Test details
17 items · 14 passed · 3 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 | Mismatch | Requested gpt-5.6-sol; the response says SaaSolVip |
| 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 | Match | Behavior belongs to the OpenAI GPT family; brand match score 100 |
| C-03 | Model consistency | Match | 与官方 gpt-5.6-sol 吻合，型号一致度 99 |
| C-04 | Cross-brand swap check | None found | Similarity to other brands' models totals under 1% |
| Billing & capabilities | |||
| D-01 | Cache billing | Cache billing works | On average 100% of repeated requests were billed at the cache price. |
| D-02 | Context length | 400K passed | Read in full up to 400K; 1M failed: 接口返回 HTTP 400. |
| 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 ratio100.0%
Cache billing works
On average 100% of repeated requests were billed at the cache price.
Usage this run34.3KCached tokens27.4KNon-cached tokens6.9KAverage per run6.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 400K
Read in full up to 400K; 1M failed: 接口返回 HTTP 400.
Reference windowVerified up to 400KThe model center has no reference context window for this model yet.Tested context lengths32K / 128K / 400K / 1MTested from short to long, stopping at the first failure.
- 32KRead in full · 34.5K received
- 128KRead in full · 121.0K received
- 400KRead in full · 368K received
- 1M接口返回 HTTP 400
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage575.3KThe actual usage reported by the API; this page goes by it.Estimated usage1.3M-1.8MEstimated from this test's requests.Deviation55% 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.