Model limit probe

Z.ai: GLM 4 32B | RPM limit

Z.ai: GLM 4 32B RPM limit decides whether a key can enter a production route. TestKey reads model ID z-ai/glm-4-32b, provider Zhipu AI (GLM), catalog context, real-key headers, 429 errors, and region signals together.

Model

z-ai/glm-4-32b

Z.ai: GLM 4 32B

Provider

Zhipu AI (GLM)

13 models in catalog

Limit dimension

RPM limit

rpm-limit

Visible signal

real key probe required

Context window: 128,000

Limit matrix summary

Model

z-ai/glm-4-32b

Limit dimension

rpm-limit

Visible signal

real key probe required

Read-only check. Detection data burns after 5 minutes.

Why this limit matters

Z.ai: GLM 4 32B RPM limit decides whether a key can enter a production route. TestKey reads model ID z-ai/glm-4-32b, provider Zhipu AI (GLM), catalog context, real-key headers, 429 errors, and region signals together.

Model: z-ai/glm-4-32b
Provider: Zhipu AI (GLM)
Limit dimension: RPM limit

How to prove it

Read-only check. Detection data burns after 5 minutes.

Start with the visible signal: real key probe required, then read headers and error bodies with read-only requests.
RPM limit must bind model ID z-ai/glm-4-32b; limits from another model at the same provider cannot be reused.
RPM limit · real key probe required · 128,000

Operator action

Z.ai: GLM 4 32B RPM limit is not just a number. It should become route throttling, sale tags, headroom alerts, fallback model suggestions, and price protection.

Read-only check. Detection data burns after 5 minutes.
Visible signal: real key probe required
Context window: 128,000

Open key checker

Read-only check. Detection data burns after 5 minutes.