Highly similarBelow confirmation threshold
与官方 glm-5.3 高度相似
行为特征与官方 glm-5.3 高度相似，未达确认标准，与 glm-5.3-flash 难以区分。
Brand consistency99/100
Model match score (glm-5.3)99/100
Checks12/17 Passed
- Providers
- MoeRouter — 萌力连接,智汇所长
- Claimed model
- glm-5.3
- Plan
- Full check
- Reference
- 107 official models
- Requests
- 23
- Duration
- 7 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AInvalidIndependent sample B采样 BValidIndependent sample C采样 CValidIndependent sample D采样 DInvalidIndependent sample E采样 EValidIndependent sample F采样 FValidIndependent sample G采样 GValidIndependent sample H采样 HValidIndependent sample I采样 IValidReference107 official models · 7/9 Valid
Answer by answer7 answers: 3 match glm-5.3；another 4 match no model clearly on their own
Similarity to official modelsTop 5
These answers are not close to any official model on file. The percentages below only rank them against each other and do not mean the answers resemble any of these models.
- glm-5.3Claimed model99%
- claude-sonnet-5-5<1%
- claude-fable-5<1%
- qwen3-max<1%
- qwen3.8-max<1%
02Test details
17 items · 12 passed · 5 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 | 7 / 9 valid | 首轮未能判定，已追加两轮；部分采样结果不可用于比对 |
| C-02 | Brand consistency | Match | Behavior belongs to the Zhipu GLM family; brand match score 99 |
| C-03 | Model consistency | Below confirmation threshold | 型号一致度 99，与 glm-5.3-flash 难以区分 |
| C-04 | Cross-brand swap check | None found | Similarity to other brands' models totals under 5% |
| Billing & capabilities | |||
| D-01 | Cache billing | Partly works | On average 37% 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 403. |
| 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 |
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 ratio37.1%
Partly works
On average 37% of repeated requests were billed at the cache price; the rest at the regular price.
Usage this run43.9KCached tokens16.3KNon-cached tokens27.7KAverage per run8.8K
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 403.
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.4K received
- 128KRead in full · 120.0K received
- 400KRead in full · 383.6K received
- 1M接口返回 HTTP 403
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage614.9KThe actual usage reported by the API; this page goes by it.Estimated usage1.3M-1.8MEstimated from this test's requests.Deviation52% 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
Highly similarBelow confirmation threshold
与官方 glm-5.3 高度相似
行为特征与官方 glm-5.3 高度相似，未达确认标准，与 glm-5.3-flash 难以区分。
Brand consistency99/100
Model match score (glm-5.3)99/100
Checks12/17 Passed
- Providers
- MoeRouter — 萌力连接,智汇所长
- Claimed model
- glm-5.3
- Plan
- Full check
- Reference
- 107 official models
- Requests
- 23
- Duration
- 7 分钟
01Identity check
Behaviour compared with each official referenceIndependent sample A采样 AInvalidIndependent sample B采样 BValidIndependent sample C采样 CValidIndependent sample D采样 DInvalidIndependent sample E采样 EValidIndependent sample F采样 FValidIndependent sample G采样 GValidIndependent sample H采样 HValidIndependent sample I采样 IValidReference107 official models · 7/9 Valid
Answer by answer7 answers: 3 match glm-5.3；another 4 match no model clearly on their own
Similarity to official modelsTop 5
These answers are not close to any official model on file. The percentages below only rank them against each other and do not mean the answers resemble any of these models.
- glm-5.3Claimed model99%
- claude-sonnet-5-5<1%
- claude-fable-5<1%
- qwen3-max<1%
- qwen3.8-max<1%
02Test details
17 items · 12 passed · 5 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 | 7 / 9 valid | 首轮未能判定，已追加两轮；部分采样结果不可用于比对 |
| C-02 | Brand consistency | Match | Behavior belongs to the Zhipu GLM family; brand match score 99 |
| C-03 | Model consistency | Below confirmation threshold | 型号一致度 99，与 glm-5.3-flash 难以区分 |
| C-04 | Cross-brand swap check | None found | Similarity to other brands' models totals under 5% |
| Billing & capabilities | |||
| D-01 | Cache billing | Partly works | On average 37% 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 403. |
| 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 |
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 ratio37.1%
Partly works
On average 37% of repeated requests were billed at the cache price; the rest at the regular price.
Usage this run43.9KCached tokens16.3KNon-cached tokens27.7KAverage per run8.8K
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 403.
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.4K received
- 128KRead in full · 120.0K received
- 400KRead in full · 383.6K received
- 1M接口返回 HTTP 403
Token usage check
Reported usage is used; estimates appear only when none is reported.
Reported usage614.9KThe actual usage reported by the API; this page goes by it.Estimated usage1.3M-1.8MEstimated from this test's requests.Deviation52% 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
还没有人评论，来写第一条。
发表评论
编辑器加载中…
发表评论