A newer test record is availableThis report preserves the result at the time of testing and remains valid as a record. You can also view the newer report。
Identity confirmedModel verified
Confirmed as the official glm-5.3
Behavior matches the official glm-5.3.
Brand consistency100/100
Model match score (glm-5.3)100/100
Checks13/17 Passed
- Providers
- inferhub.dev
- Claimed model
- glm-5.3
- Plan
- Full check
- Reference
- 104 official models
- Requests
- 15
- Duration
- 2 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AValidIndependent sample B采样 BValidIndependent sample C采样 CValidReference104 official models · 3/3 Valid
Answer by answer3 answers: 3 match glm-5.3
Similarity to official modelsTop 5
- glm-5.3Claimed model>99%
- hy4-preview<1%
- claude-sonnet-5-5<1%
- glm-5.1<1%
- claude-fable-5<1%
02Test details
17 items · 13 passed · 4 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 | Inconsistent | Total 83 does not equal the sum 24 |
| 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% |
| Billing & capabilities | |||
| D-01 | Cache billing | Partly works | On average 50% of repeated requests were billed at the cache price; the rest at the regular price. |
| D-02 | Context length | 32K passed | Read in full up to 32K; 128K failed: Input truncated; about 62K actually received. |
| D-03 | Streaming output | Normal | Streamed content is complete |
| D-04 | Tool use | Supported | Returns the correct function name and arguments |
| D-05 | Structured output | Did not follow the schema | The response did not follow the required JSON schema |
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 | 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) |
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 ratio50.2%
Partly works
On average 50% of repeated requests were billed at the cache price; the rest at the regular price.
Usage this run50.0KCached tokens22.3KNon-cached tokens27.7KAverage per run10.0K
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 32K
Read in full up to 32K; 128K failed: Input truncated; about 62K actually received.
Reference windowReference window 1MModel-center context window; available lengths may vary by provider.Tested context lengths32K / 128KTested from short to long, stopping at the first failure.
- 32KRead in full · 60.1K received
- 128KInput truncated; about 62K actually received
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage178.2KThe actual usage reported by the API; this page goes by it.Estimated usage158.0K-304.3KEstimated 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.3 verification report
A newer test record is availableThis report preserves the result at the time of testing and remains valid as a record. You can also view the newer report。
Identity confirmedModel verified
Confirmed as the official glm-5.3
Behavior matches the official glm-5.3.
Brand consistency100/100
Model match score (glm-5.3)100/100
Checks13/17 Passed
- Providers
- inferhub.dev
- Claimed model
- glm-5.3
- Plan
- Full check
- Reference
- 104 official models
- Requests
- 15
- Duration
- 2 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AValidIndependent sample B采样 BValidIndependent sample C采样 CValidReference104 official models · 3/3 Valid
Answer by answer3 answers: 3 match glm-5.3
Similarity to official modelsTop 5
- glm-5.3Claimed model>99%
- hy4-preview<1%
- claude-sonnet-5-5<1%
- glm-5.1<1%
- claude-fable-5<1%
02Test details
17 items · 13 passed · 4 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 | Inconsistent | Total 83 does not equal the sum 24 |
| 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% |
| Billing & capabilities | |||
| D-01 | Cache billing | Partly works | On average 50% of repeated requests were billed at the cache price; the rest at the regular price. |
| D-02 | Context length | 32K passed | Read in full up to 32K; 128K failed: Input truncated; about 62K actually received. |
| D-03 | Streaming output | Normal | Streamed content is complete |
| D-04 | Tool use | Supported | Returns the correct function name and arguments |
| D-05 | Structured output | Did not follow the schema | The response did not follow the required JSON schema |
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 | 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) |
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 ratio50.2%
Partly works
On average 50% of repeated requests were billed at the cache price; the rest at the regular price.
Usage this run50.0KCached tokens22.3KNon-cached tokens27.7KAverage per run10.0K
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 32K
Read in full up to 32K; 128K failed: Input truncated; about 62K actually received.
Reference windowReference window 1MModel-center context window; available lengths may vary by provider.Tested context lengths32K / 128KTested from short to long, stopping at the first failure.
- 32KRead in full · 60.1K received
- 128KInput truncated; about 62K actually received
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage178.2KThe actual usage reported by the API; this page goes by it.Estimated usage158.0K-304.3KEstimated 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
还没有人评论，来写第一条。
发表评论