Confirmed as the official glm-5.3
Behavior matches the official glm-5.3.
- Relay · group
- a6api · default
- Claimed model
- glm-5.3
- Plan
- Standard verification
- Reference
- 102 official models
- Requests
- 6
- Duration
- 2 分钟
01Identity check
Behaviour compared with each official referenceAnswer by answer3 answers: 3 match glm-5.3
- glm-5.3Claimed model>99%
- claude-fable-5<1%
- claude-fable-5-1<1%
- glm-5.3-flash<1%
- claude-opus-4-8<1%
02Test details
12 items · 12 passed · 0 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 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 | Match | Behavior belongs to the Zhipu GLM family; brand match score 100 |
| C-03 | Model consistency | Match | 与官方 glm-5.3 吻合,型号一致度 100 |
| C-04 | Cross-brand swap check | None found | Similarity to other brands' models totals under 1% |
Token usage check
Reported usage is used; estimates appear only when none is reported.
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 Mozhenzhenglm-5.3 verification report
Confirmed as the official glm-5.3
Behavior matches the official glm-5.3.
- Relay · group
- a6api · default
- Claimed model
- glm-5.3
- Plan
- Standard verification
- Reference
- 102 official models
- Requests
- 6
- Duration
- 2 分钟
01Identity check
Behaviour compared with each official referenceAnswer by answer3 answers: 3 match glm-5.3
- glm-5.3Claimed model>99%
- claude-fable-5<1%
- claude-fable-5-1<1%
- glm-5.3-flash<1%
- claude-opus-4-8<1%
02Test details
12 items · 12 passed · 0 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 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 | Match | Behavior belongs to the Zhipu GLM family; brand match score 100 |
| C-03 | Model consistency | Match | 与官方 glm-5.3 吻合,型号一致度 100 |
| C-04 | Cross-brand swap check | None found | Similarity to other brands' models totals under 1% |
Token usage check
Reported usage is used; estimates appear only when none is reported.
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.