If you are considering GLM for an application, buying model access and buying stock require different evidence. In its November 10 disclosure, Z.AI said it had received chairman Liu Debing's proposal to repurchase H shares on the open market. That intention is not a guarantee about API pricing or availability.
The filing appears in the HKEX announcement directory. In its report on the announcement, The Paper describes two ceilings: HK$4 billion in spending and 1% of shares outstanding on the announcement date. Execution remains subject to the board's judgment and market conditions; the company does not promise to complete the full repurchase.
Price the input and the answer separately
Developers have a more useful reference in Z.AI's official USD pricing table. Per million tokens, GLM-5.3 lists ordinary input at $1.4 and output at $4.4. GLM-5.3-Flash lists $0.15 for ordinary input and $0.50 for output. Input served from cache costs $0.26 and $0.03 respectively. Cache storage is a separate category, currently free for a limited time, rather than an additional storage charge payable now.
These are the API rates displayed on the page, not a price change announced with the buyback, and not the price of a coding subscription. Web Search is separately listed at $0.01 per use. A workflow that invokes tools needs a budget beyond the model's token charges.
Our assessment: compare the total cost of getting the same task accepted before deciding to switch models. A cheaper token does not necessarily buy a cheaper deliverable. Retries, longer answers and manual corrections can change the result.
Charge failed attempts to the accepted result
For a hypothetical budget calculation, assume a GLM-5.3 task uses one million ordinary input tokens, one million output tokens and one search per attempt, with no cache hits. The first attempt fails acceptance; one complete retry passes. Each attempt costs $1.4 + $4.4 + $0.01 in model and search fees. Add both attempts to find the API bill for the accepted result, not just the successful attempt. Record human review and editing time separately from that bill.
Use existing tasks with clear acceptance criteria for a small comparison. Keep the inputs and passing conditions fixed, then record model charges, tool calls and time spent editing the result. If Flash is a candidate, check whether it meets the same requirements rather than assuming it substitutes for the other model.
Check the actual billing items in your console and set a spending cap before testing. For important workflows, keep inputs and outputs portable and maintain a backup service plan.