You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I now understand the proposed quota-normalization logic discussed there:
normalized quota usage = visible model cost × (60 / model Usage limit)
So, for example:
a model with a $60 monthly Usage allowance has a 1× factor
a model with a $30 allowance has a 2× factor
a model with a $15 allowance has a 4× factor
I also understand why it is possible for Weekly Usage to be 100% while Monthly Usage is around 50%:
weekly shared limit: $30
monthly shared limit: $60
Therefore, approximately $30 of normalized usage would result in:
Weekly: 100%
Monthly: 50%
So that part of the dashboard is understandable.
However, my actual concern remains: I cannot reconcile my exported token usage with the approximately 51% monthly quota usage shown by the server.
My exported CSV contains only 103 Go requests:
77 × Muse Spark 1.3 Contributor
16 × Grok 4.7
10 × DeepSeek V4.1 Flash
All rows have:
billing_source = go
The CSV contains approximately:
2.79M input tokens
35.62M cache-read tokens
200K output tokens
140K reasoning tokens
I tried recalculating the usage using the currently published model prices and the model-specific quota normalization described in the related issues.
Even when accounting for Grok's smaller Usage allowance and therefore its higher quota multiplier, I cannot reproduce anything close to the ~51% monthly quota displayed on my account.
Using the published pricing and current model allowances, my estimate is roughly in the ~18–20% monthly range.
I also tried deliberately conservative assumptions against my own case, including:
treating Grok requests as long-context / higher-priced where applicable
accounting for reasoning output
using less favorable DeepSeek pricing
applying a smaller DeepSeek Usage allowance instead of the temporary promotional allowance
Even under those assumptions, I get roughly ~34% monthly usage, still materially below the 51% shown by the server.
So I believe there are now two separate questions:
Quota normalization: I understand that model Usage values can apply different effective multipliers to the shared quota.
Actual metering: The normalized usage calculated from my exported requests still does not appear to explain the quota percentage shown on my account.
Could someone from the OpenCode team please confirm the exact server-side calculation for my usage?
Specifically, it would help to know:
What normalized quota amount did the server calculate from these 103 requests?
Which pricing/Usage allowance was applied to Muse Spark 1.3 Contributor, Grok 4.7 and DeepSeek V4.1 Flash?
Are cache reads, reasoning tokens, retries, failed requests, provider-side retries, or any other usage counted toward quota but omitted from the exported CSV?
Was DeepSeek V4.1 Flash calculated using its promotional Usage allowance or its normal allowance?
Is there any server-side usage associated with my Go account that is not present in the exported usage-30d.csv?
The key point is that I am no longer questioning why 100% weekly can correspond to ~50% monthly.
I am specifically questioning how my exported usage became approximately 51% monthly usage in the first place.
If possible, please provide a worked calculation from my attached CSV so that I can compare the server-side quota calculation with the exported usage data.
Activity
github-actions commentedon Sep 21, 2026
This issue might be a duplicate of several existing issues reporting the same Go usage calculation discrepancy. Please check:
If your issue isn't covered by any of the above, feel free to keep this open and add any distinguishing details.
joaoguariglia commentedon Sep 22, 2026
Thanks. I reviewed the related issues, especially #41391, #42985, #41206 and #43149.
I now understand the proposed quota-normalization logic discussed there:
normalized quota usage = visible model cost × (60 / model Usage limit)So, for example:
I also understand why it is possible for Weekly Usage to be 100% while Monthly Usage is around 50%:
Therefore, approximately $30 of normalized usage would result in:
So that part of the dashboard is understandable.
However, my actual concern remains: I cannot reconcile my exported token usage with the approximately 51% monthly quota usage shown by the server.
My exported CSV contains only 103 Go requests:
All rows have:
billing_source = goThe CSV contains approximately:
I tried recalculating the usage using the currently published model prices and the model-specific quota normalization described in the related issues.
Even when accounting for Grok's smaller Usage allowance and therefore its higher quota multiplier, I cannot reproduce anything close to the ~51% monthly quota displayed on my account.
Using the published pricing and current model allowances, my estimate is roughly in the ~18–20% monthly range.
I also tried deliberately conservative assumptions against my own case, including:
Even under those assumptions, I get roughly ~34% monthly usage, still materially below the 51% shown by the server.
So I believe there are now two separate questions:
Could someone from the OpenCode team please confirm the exact server-side calculation for my usage?
Specifically, it would help to know:
usage-30d.csv?The key point is that I am no longer questioning why 100% weekly can correspond to ~50% monthly.
I am specifically questioning how my exported usage became approximately 51% monthly usage in the first place.
If possible, please provide a worked calculation from my attached CSV so that I can compare the server-side quota calculation with the exported usage data.
Tarquinen commentedon Oct 20, 2026
We're tracking this in #42985, so I'm closing this as a duplicate. Please follow that issue for updates.
— from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊