What "quota back-calculation" means
Official pages rarely publish a hard token cap. We infer it: Total quota โ tokens already used รท usage-percentage shown. E.g. 15M tokens at 37.3% of the 5h bar implies ~40M for that window. We cross-check across the 5h, 7-day and monthly bars.
Why no official fixed cap is published
Caps are dynamic: they shift with model version, server load, and business strategy. A published number becomes a promise and a target for abuse, so providers keep them fuzzy on purpose. Treat every figure here as a snapshot, not a contract.
How cache hit-rate changes real consumption
In coding/agent workflows the same context is sent again and again. One user logged a 93.7% cache-hit rate โ meaning only ~6% of input was billed at full price. The quota you "feel" is therefore far larger than the raw token count suggests.
Subscription vs pay-as-you-go API
A subscription trades flexibility for a flat price within rolling windows. Pay-as-you-go API bills every token but never rate-limits you. If your usage is steady and predictable, subscriptions win; if it's spiky or you need concurrency, API wins.