Confirmed as the official glm-5.3-flash
Behavior matches the official glm-5.3-flash.
- Providers
- foxrouter.org
- Claimed model
- glm-5.3-flash
- Plan
- Full check
- Reference
- 115 official models
- Requests
- 22
- Duration
- 7 分钟
01Identity check
Behaviour compared with each official referenceAnswer by answer3 answers: 3 match glm-5.3-flash
- glm-5.3-flashClaimed model>99%
- glm-5.3<1%
- mistral-large-4<1%
- claude-sonnet-5-5<1%
- claude-fable-5<1%
02Test details
17 items · 14 passed · 3 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-flash |
| 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 / 9 valid | 首轮未能判定,已追加两轮;部分采样结果不可用于比对 |
| C-02 | Brand consistency | Match | Behavior belongs to the Zhipu GLM family; brand match score 100 |
| C-03 | Model consistency | Match | 与官方 glm-5.3-flash 吻合,型号一致度 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 48% 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 6K 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 | Supported | Returned in the required JSON structure |
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.
On average 48% of repeated requests were billed at the cache price; the rest at the regular price.
Long documents are sent tier by tier to check whether the whole document is read.
Read in full up to 32K; 128K failed: Input truncated; about 6K actually received.
- 32KRead in full · 34.8K received
- 128KInput truncated; about 6K actually received
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.
Reviews
还没有人评论,来写第一条。
Before you buy AI, check Mozhenzhenglm-5.3-flash verification report
Confirmed as the official glm-5.3-flash
Behavior matches the official glm-5.3-flash.
- Providers
- foxrouter.org
- Claimed model
- glm-5.3-flash
- Plan
- Full check
- Reference
- 115 official models
- Requests
- 22
- Duration
- 7 分钟
01Identity check
Behaviour compared with each official referenceAnswer by answer3 answers: 3 match glm-5.3-flash
- glm-5.3-flashClaimed model>99%
- glm-5.3<1%
- mistral-large-4<1%
- claude-sonnet-5-5<1%
- claude-fable-5<1%
02Test details
17 items · 14 passed · 3 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-flash |
| 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 / 9 valid | 首轮未能判定,已追加两轮;部分采样结果不可用于比对 |
| C-02 | Brand consistency | Match | Behavior belongs to the Zhipu GLM family; brand match score 100 |
| C-03 | Model consistency | Match | 与官方 glm-5.3-flash 吻合,型号一致度 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 48% 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 6K 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 | Supported | Returned in the required JSON structure |
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.
On average 48% of repeated requests were billed at the cache price; the rest at the regular price.
Long documents are sent tier by tier to check whether the whole document is read.
Read in full up to 32K; 128K failed: Input truncated; about 6K actually received.
- 32KRead in full · 34.8K received
- 128KInput truncated; about 6K actually received
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.
Reviews
还没有人评论,来写第一条。
发表评论