Identity confirmedModel verified
Confirmed as the official glm-5.2
行为特征与官方 glm-5.2 吻合；与同代近似型号 glm-5 几乎相同，均高度符合。
Brand consistency100/100
Model match score (含同代近似型号 glm-5)100/100
Checks11/12 Passed
- Providers
- token6688.com
- Claimed model
- glm-5.2
- Plan
- Standard verification
- Reference
- 105 official models
- Requests
- 5
- Duration
- 7 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AValidIndependent sample B采样 BValidIndependent sample C采样 CInvalidReference105 official models · 2/3 Valid
Answer by answer2 answers: 2 match glm-5.2 / glm-5
Similarity to official modelsTop 5
- glm-5.2 · glm-5Claimed model and its near-identical sibling — both match closely>99%
- gpt-4.1-mini<1%
- gpt-5.1-codex-mini<1%
- MiniMax-M2.5<1%
02Test details
12 items · 11 passed · 1 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.2 |
| 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 | 2 / 3 valid | Some samples could not 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.2 吻合；与同代近似型号 glm-5 几乎相同 |
| C-04 | Cross-brand swap check | None found | Similarity to other brands' models totals under 1% |
03Which apps can connect
Tried once per app with glm-5.2, the way each app connectsUsing this test’s address, key and model, we test responses and tool calls in each app’s API format. We do not launch the apps or test installation, sign-in or complete tasks.
| Software | Result | Methodology |
|---|---|---|
| Codex | Connects | Replied normally and called the toolConnected the way Codex does (OpenAI Responses format) |
| Cherry Studio, Chatbox, LobeChat, Open WebUI, Cline | Connects | Replied normally and called the toolConnected the way Cherry Studio and similar apps do (OpenAI-compatible format) |
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage44.7KThe actual usage reported by the API; this page goes by it.Estimated usage3.6K-92.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.
Reviews
还没有人评论，来写第一条。
Before you buy AI, check MozhenzhenScan to view reportOpen full report
Mozhenzhen verification report · Measured with real calls
glm-5.2 verification report
Identity confirmedModel verified
Confirmed as the official glm-5.2
行为特征与官方 glm-5.2 吻合；与同代近似型号 glm-5 几乎相同，均高度符合。
Brand consistency100/100
Model match score (含同代近似型号 glm-5)100/100
Checks11/12 Passed
- Providers
- token6688.com
- Claimed model
- glm-5.2
- Plan
- Standard verification
- Reference
- 105 official models
- Requests
- 5
- Duration
- 7 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AValidIndependent sample B采样 BValidIndependent sample C采样 CInvalidReference105 official models · 2/3 Valid
Answer by answer2 answers: 2 match glm-5.2 / glm-5
Similarity to official modelsTop 5
- glm-5.2 · glm-5Claimed model and its near-identical sibling — both match closely>99%
- gpt-4.1-mini<1%
- gpt-5.1-codex-mini<1%
- MiniMax-M2.5<1%
02Test details
12 items · 11 passed · 1 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.2 |
| 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 | 2 / 3 valid | Some samples could not 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.2 吻合；与同代近似型号 glm-5 几乎相同 |
| C-04 | Cross-brand swap check | None found | Similarity to other brands' models totals under 1% |
03Which apps can connect
Tried once per app with glm-5.2, the way each app connectsUsing this test’s address, key and model, we test responses and tool calls in each app’s API format. We do not launch the apps or test installation, sign-in or complete tasks.
| Software | Result | Methodology |
|---|---|---|
| Codex | Connects | Replied normally and called the toolConnected the way Codex does (OpenAI Responses format) |
| Cherry Studio, Chatbox, LobeChat, Open WebUI, Cline | Connects | Replied normally and called the toolConnected the way Cherry Studio and similar apps do (OpenAI-compatible format) |
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage44.7KThe actual usage reported by the API; this page goes by it.Estimated usage3.6K-92.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.
Reviews
还没有人评论，来写第一条。
发表评论
编辑器加载中…
发表评论