Identity mismatchSubstitution detected
Does not match the claimed model glm-5.3
行为特征与官方 glm-5.3 不符，最接近官方 grok-4.7。
Brand consistency0/100
Model match score (glm-5.3)0/100
Checks11/17 Passed
- Providers
- PcPc.AI
- Claimed model
- glm-5.3
- Plan
- Full check
- Reference
- 103 official models
- Requests
- 18
- Duration
- 2 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AValidIndependent sample B采样 BValidIndependent sample C采样 CValidReference103 official models · 3/3 Valid
Answer by answer3 answers: 0 match glm-5.3；another 3 look more like grok-4.7
Similarity to official modelsTop 5
- grok-4.7>99%
- grok-4.5<1%
- claude-opus-4-5<1%
- grok-4.6<1%
- grok-4.20-0309-reasoning<1%
02Test details
17 items · 11 passed · 3 notes · 3 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 glm-5.3 |
| 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 | 3 / 3 valid | All independent samples can be used for comparison |
| C-02 | Brand consistency | Mismatch | Behavior does not belong to the Zhipu GLM family; brand match score 0 |
| C-03 | Model consistency | Mismatch | Model match score 0; closest to the official grok-4.7 |
| C-04 | Cross-brand swap check | Substitution detected | Behavior is closest to grok-4.7 from another brand |
| Billing & capabilities | |||
| D-01 | Cache billing | Partly works | On average 79% of repeated requests were billed at the cache price; the rest at the regular price. |
| D-02 | Context length | 400K passed | Read in full up to 400K; 1M failed: 接口返回 HTTP 400. |
| D-03 | Streaming output | Incomplete content | The streamed content did not match the instruction |
| 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 ratio78.6%
Partly works
On average 79% of repeated requests were billed at the cache price; the rest at the regular price.
Usage this run36.5KCached tokens23.8KNon-cached tokens12.7KAverage per run7.3K
Usage reportedReportedCache billingHappenedResultPartly 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 windowReference window 1MModel-center context window; available lengths may vary by provider.Tested context lengths32K / 128K / 400K / 1MTested from short to long, stopping at the first failure.
- 32KRead in full · 31.5K received
- 128KRead in full · 118.0K received
- 400KRead in full · 374.6K received
- 1M接口返回 HTTP 400
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage576.5KThe 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.
Reviews
还没有人评论，来写第一条。
Before you buy AI, check MozhenzhenScan to view reportOpen full report
Mozhenzhen verification report · Measured with real calls
glm-5.3 verification report
Identity mismatchSubstitution detected
Does not match the claimed model glm-5.3
行为特征与官方 glm-5.3 不符，最接近官方 grok-4.7。
Brand consistency0/100
Model match score (glm-5.3)0/100
Checks11/17 Passed
- Providers
- PcPc.AI
- Claimed model
- glm-5.3
- Plan
- Full check
- Reference
- 103 official models
- Requests
- 18
- Duration
- 2 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AValidIndependent sample B采样 BValidIndependent sample C采样 CValidReference103 official models · 3/3 Valid
Answer by answer3 answers: 0 match glm-5.3；another 3 look more like grok-4.7
Similarity to official modelsTop 5
- grok-4.7>99%
- grok-4.5<1%
- claude-opus-4-5<1%
- grok-4.6<1%
- grok-4.20-0309-reasoning<1%
02Test details
17 items · 11 passed · 3 notes · 3 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 glm-5.3 |
| 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 | 3 / 3 valid | All independent samples can be used for comparison |
| C-02 | Brand consistency | Mismatch | Behavior does not belong to the Zhipu GLM family; brand match score 0 |
| C-03 | Model consistency | Mismatch | Model match score 0; closest to the official grok-4.7 |
| C-04 | Cross-brand swap check | Substitution detected | Behavior is closest to grok-4.7 from another brand |
| Billing & capabilities | |||
| D-01 | Cache billing | Partly works | On average 79% of repeated requests were billed at the cache price; the rest at the regular price. |
| D-02 | Context length | 400K passed | Read in full up to 400K; 1M failed: 接口返回 HTTP 400. |
| D-03 | Streaming output | Incomplete content | The streamed content did not match the instruction |
| 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 ratio78.6%
Partly works
On average 79% of repeated requests were billed at the cache price; the rest at the regular price.
Usage this run36.5KCached tokens23.8KNon-cached tokens12.7KAverage per run7.3K
Usage reportedReportedCache billingHappenedResultPartly 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 windowReference window 1MModel-center context window; available lengths may vary by provider.Tested context lengths32K / 128K / 400K / 1MTested from short to long, stopping at the first failure.
- 32KRead in full · 31.5K received
- 128KRead in full · 118.0K received
- 400KRead in full · 374.6K received
- 1M接口返回 HTTP 400
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage576.5KThe 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.
Reviews
还没有人评论，来写第一条。
发表评论