UndeterminedBelow decision threshold
Identity could not be determined this time
The answers are not close enough to any known model, so it cannot be determined.
Brand consistency—/100
Model match score (gpt-5.6-sol)—/100
Checks0/4 Passed
- Providers
- 君黎API
- Claimed model
- gpt-5.6-sol
- Plan
- Standard verification
- Reference
- Official reference samples
- Requests
- 5
- Duration
- 2 分钟
01Identity check
Behaviour compared with each official referenceSimilarity 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-5.6-solClaimed model65%
- gpt-5.521%
- gpt-5.6-luna7%
- gpt-5.45%
- gpt-5.6-terra<1%
02Test details
4 items · 0 passed · 4 notes · 0 failed| No. | Check | Result | Methodology |
|---|---|---|---|
| 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 0; 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 |
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage4.8KThe actual usage reported by the API; this page goes by it.Estimated usage3.0K-30.0KEstimated from this test's requests.DeviationWithin the estimateThe reported usage is within the estimated range.Usage checkMatches 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
Is gpt-5.6-sol genuine? Verification result
UndeterminedBelow decision threshold
Identity could not be determined this time
The answers are not close enough to any known model, so it cannot be determined.
Brand consistency—/100
Model match score (gpt-5.6-sol)—/100
Checks0/4 Passed
- Providers
- 君黎API
- Claimed model
- gpt-5.6-sol
- Plan
- Standard verification
- Reference
- Official reference samples
- Requests
- 5
- Duration
- 2 分钟
01Identity check
Behaviour compared with each official referenceSimilarity 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-5.6-solClaimed model65%
- gpt-5.521%
- gpt-5.6-luna7%
- gpt-5.45%
- gpt-5.6-terra<1%
02Test details
4 items · 0 passed · 4 notes · 0 failed| No. | Check | Result | Methodology |
|---|---|---|---|
| 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 0; 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 |
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage4.8KThe actual usage reported by the API; this page goes by it.Estimated usage3.0K-30.0KEstimated from this test's requests.DeviationWithin the estimateThe reported usage is within the estimated range.Usage checkMatches 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.