Astra’s quota accounting looks broken — users report 4–5× Sol’s consumption, not the expected 2.5×

Multiple users across Chinese-language communities, particularly Linux.do and NodeSeek, have been reporting a possible discrepancy in Astra’s Codex quota accounting. The concern is not simply that Astra uses up the allowance quickly, but that it appears to consume more quota than its published pricing would suggest.

The published standard credit rates put Astra at 2.5× Sol for input, cached input, and output tokens. That higher price is already expected.

What users are reporting is an additional multiplier beyond that difference. One user explicitly reports approximately 1.8× relative to API-priced usage, while another reports that the same five-hour allowance corresponds to roughly $18 of Sol usage but only $10 of Astra usage, with the same pattern across four accounts. Those dollar figures are usage valued at each model’s own API rates—not actual API charges.

In other words, the allegation is that $1 of Astra usage, calculated at Astra’s own API prices, consumes around 1.8× as much subscription quota as $1 of Sol usage calculated at Sol’s prices. If accurate, that would mean an effective difference of approximately 2.5 × 1.8 = 4.5×, rather than the expected 2.5×.

Other reports point in a similar direction, although the estimates vary:

- A Linux.do thread reports Astra consuming approximately 4–5× Sol’s quota based on token usage, with reported cache hit rates of 97–98% for both models.

- A separate six-account comparison using third-party usage tracking estimates an additional 1.4–1.6× after applying each model’s API prices.

- A NodeSeek thread also flags the discrepancy and suggests applying a 1.6× accounting correction.