This is a debate post about a discrepancy between usage charges and the listed price when using GLM 5.3 on the OpenCode platform—involving GLM 5.3 quota measurement, token efficiency, and platform billing transparency.
OP: GLM 5.3 is listed at $15 per month, but the dashboard's usage percentage is increasing against a $60 quota—"it goes up 1% every 60 cents, rather than every 15 cents."
OP update: Further measurement put the usage basis closer to $45—$3.98 on the "Cost" dashboard corresponded to a 9% increase in "Monthly Usage."
Top-voted reply (+23, @BlacksmithLittle7005): "No it's not $60, it's just that GLM5.3 is a lot more efficient than GLM5.2 in token usage. Tasks that were costing me $0.45 on 5.2 are $0.2 on 5.3. They did a good job with post training."—in other words, the same "quota percentage" corresponds to more tasks, and the efficiency gain creates the impression of a billing discrepancy.
(+5, @look): In testing, a $1.51 cost increased the percentage by only 2%, not 10%, and the token count calculated at the listed price matched $1.51—questioning the pricing model itself.
(+22, @Schlickeysen): "Jeez, OpenCode's transparency is about as good as a paper bag."
(+5, @ThePi7on): "They really need to improve how they communicate/visualize the pricing model."
(+1, @mestar12345): "I saw it listed as free in omp. There is a weekly usage limit, and one hour used up half a month's quota."
The improvement in GLM 5.3's token efficiency (the official claim is that output tokens per task fell from ~96K to ~75K) is noticeable in real-world use, but billing bases differ across platforms ($-denominated pricing vs. quota percentages vs. credits), making it easy to get the impression that the price has "gone up/down."
For users: focus on the actual cost per task (5.3 is cheaper) rather than the monthly quota percentage; for platforms: credit/quota models need to be more transparent.
"No it's not $60, it's just that GLM5.3 is a lot more efficient than GLM5.2 in token usage. Tasks that were costing me $… This is a necessary excerpt; read the original source for full context.
GLM-5.3
