Unverified50% confidenceFactExact time
GLM Coding Plan's 5-hour window refreshes on a rolling basis (usage is released 5 hours after being consumed), and the weekly window resets every 7 days from the moment of subscription; if either window is exhausted, tool calls fail immediately, and the plan does not fall back to the account balance.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/13/2026
First Seen
Valid until: 1/11/2027
Sources
Related Entities
Related Claims
UnverifiedGLM Coding Plan fully switched to a token-metered credit system on July 30, 2026, after previously evolving from "counting by prompt, with no weekly cap" to "counting by prompt, with 5-hour and weekly caps".70% similarUnverifiedWhen configuring Zhipu GLM, the API timeout can be set longer (e.g., 3,000,000 milliseconds) and environment variables for disabling unnecessary traffic can be set to 1.66% similarUnverifiedMainstream large model API providers typically maintain prompt caches in units of 5 minutes to 1 hour, after which they expire.66% similarUnverifiedTogether's preemptible compute provides a five-minute drain window, giving jobs five minutes to save state before being preempted.65% similarUnverifiedThe 5-hour limit uses a rolling time window mechanism, where the system continuously tracks all requests made by the user within the most recent 5 hours and automatically removes the earliest requests from the count once they exceed 5 hours64% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1019891API
curl https://kongchang.com/api/v1/knowledge/claims/1019891MCP
get_claim(id=1019891)