UndeterminedBelow decision threshold
Identity could not be determined this time
行为特征与已收录的官方型号均不够接近，本次无法判定。
Brand consistency90/100
Model match score (glm-5.3)90/100
Checks8/16 Passed
- Providers
- surplusintelligence.ai
- Claimed model
- glm-5.3
- Plan
- Full check
- Reference
- 104 official models
- Requests
- 14
- Duration
- 1 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AValidIndependent sample B采样 BInvalidIndependent sample C采样 CValidIndependent sample D采样 DInvalidIndependent sample E采样 EInvalidIndependent sample F采样 FInvalidReference104 official models · 2/6 Valid
Answer by answer2 answers: 1 match glm-5.3；another 1 look more like claude-opus-5
Similarity to official modelsTop 5
- glm-5.3Claimed model90%
- claude-fable-54%
- claude-opus-53%
- claude-fable-5-11%
- claude-opus-4-8<1%
02Test details
16 items · 8 passed · 8 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 | 2 / 6 valid | 首轮未能判定，已追加一轮；部分采样结果不可用于比对 |
| C-02 | Brand consistency | Pending review | Brand match score 90; below the decision threshold |
| C-03 | Model consistency | Undetermined | Model match score 90; below the decision threshold |
| C-04 | Cross-brand swap check | Needs attention | Similarity to other brands' models totals about 10% |
| Billing & capabilities | |||
| D-01 | Cache billing | Not completed | 接口返回 HTTP 404，本项未完成。 |
| D-02 | Context length | 32K failed | 32K failed: 接口返回 HTTP 404. |
| D-03 | Streaming output | Not supported | 流式请求未成功（接口返回 HTTP 404） |
| D-04 | Tool use | Not supported | 带工具的请求未成功（接口返回 HTTP 404） |
| D-05 | Structured output | Not supported | 结构化输出请求未成功（接口返回 HTTP 404） |
03Which apps can connect
Tried once per app with glm-5.3, 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 | Didn't connect | This API rejected the key. Copy a valid key again and check its permission for this model（HTTP 403）Connected the way Codex does (OpenAI Responses format) |
| Cherry Studio, Chatbox, LobeChat, Open WebUI, Cline | Didn't connect | This API route was not found. Check the address for this app, or ask the provider whether it is supported（HTTP 404）Connected the way Cherry Studio and similar apps do (OpenAI-compatible format) |
接口返回 HTTP 404，本项未完成。
Tested:1 times
Context length check
Long documents are sent tier by tier to check whether the whole document is read.
Boundary at 32K
32K failed: 接口返回 HTTP 404.
Reference windowReference window 1MModel-center context window; available lengths may vary by provider.Tested context lengths32KTested from short to long, stopping at the first failure.
- 32K接口返回 HTTP 404
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage6.5KThe actual usage reported by the API; this page goes by it.Estimated usage158.0K-304.3KEstimated from this test's requests.Deviation96% 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
UndeterminedBelow decision threshold
Identity could not be determined this time
行为特征与已收录的官方型号均不够接近，本次无法判定。
Brand consistency90/100
Model match score (glm-5.3)90/100
Checks8/16 Passed
- Providers
- surplusintelligence.ai
- Claimed model
- glm-5.3
- Plan
- Full check
- Reference
- 104 official models
- Requests
- 14
- Duration
- 1 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AValidIndependent sample B采样 BInvalidIndependent sample C采样 CValidIndependent sample D采样 DInvalidIndependent sample E采样 EInvalidIndependent sample F采样 FInvalidReference104 official models · 2/6 Valid
Answer by answer2 answers: 1 match glm-5.3；another 1 look more like claude-opus-5
Similarity to official modelsTop 5
- glm-5.3Claimed model90%
- claude-fable-54%
- claude-opus-53%
- claude-fable-5-11%
- claude-opus-4-8<1%
02Test details
16 items · 8 passed · 8 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 | 2 / 6 valid | 首轮未能判定，已追加一轮；部分采样结果不可用于比对 |
| C-02 | Brand consistency | Pending review | Brand match score 90; below the decision threshold |
| C-03 | Model consistency | Undetermined | Model match score 90; below the decision threshold |
| C-04 | Cross-brand swap check | Needs attention | Similarity to other brands' models totals about 10% |
| Billing & capabilities | |||
| D-01 | Cache billing | Not completed | 接口返回 HTTP 404，本项未完成。 |
| D-02 | Context length | 32K failed | 32K failed: 接口返回 HTTP 404. |
| D-03 | Streaming output | Not supported | 流式请求未成功（接口返回 HTTP 404） |
| D-04 | Tool use | Not supported | 带工具的请求未成功（接口返回 HTTP 404） |
| D-05 | Structured output | Not supported | 结构化输出请求未成功（接口返回 HTTP 404） |
03Which apps can connect
Tried once per app with glm-5.3, 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 | Didn't connect | This API rejected the key. Copy a valid key again and check its permission for this model（HTTP 403）Connected the way Codex does (OpenAI Responses format) |
| Cherry Studio, Chatbox, LobeChat, Open WebUI, Cline | Didn't connect | This API route was not found. Check the address for this app, or ask the provider whether it is supported（HTTP 404）Connected the way Cherry Studio and similar apps do (OpenAI-compatible format) |
接口返回 HTTP 404，本项未完成。
Tested:1 times
Context length check
Long documents are sent tier by tier to check whether the whole document is read.
Boundary at 32K
32K failed: 接口返回 HTTP 404.
Reference windowReference window 1MModel-center context window; available lengths may vary by provider.Tested context lengths32KTested from short to long, stopping at the first failure.
- 32K接口返回 HTTP 404
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage6.5KThe actual usage reported by the API; this page goes by it.Estimated usage158.0K-304.3KEstimated from this test's requests.Deviation96% 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
还没有人评论，来写第一条。
发表评论