Repository navigation
Discrepancy in AI usage credit calculation for OpenCode Go subscription ($12.42 tracked vs $19.20 billed) #40280
Closed as not planned
Description
I subscribed to the OpenCode Go plan, which offers $60 worth of AI usage for a $5 promotional price in the first month. However, there is a clear discrepancy between my manually tracked daily expenses and the usage percentage displayed in the account dashboard.
Steps to reproduce / How I calculated this:
- I logged and calculated my actual AI usage expenses day by day (including models like
deepseek-v4-flash,mimo-v2.5,kimi-k3, anddeepseek-v4-pro). - The total sum of my actual daily usage is exactly $12.42.
- My dashboard currently shows 32% of the usage limit consumed.
- Based on the $60 total pool, 32% equals $19.20.
- This creates an unverified overcharge/discrepancy of $6.78.
Expected behavior
The dashboard consumption metrics should precisely reflect the accumulated cost of individual API requests ($12.42 instead of $19.20).
Screenshots / Data
I have attached the exact data spreadsheet showing the daily breakdown per model:
| Date | Model | Price |
|---|---|---|
| 2026-07-28 | deepseek-v4-flash | 0.40 |
| 2026-07-28 | mimo-v2.5 | 0.10 |
| 2026-07-29 | deepseek-v4-flash | 1.52 |
| 2026-07-29 | mimo-v2.5 | 0.16 |
| 2026-07-30 | deepseek-v4-flash | 0.54 |
| 2026-07-30 | kimi-k3 | 3.45 |
| 2026-07-30 | mimo-v2.5 | 0.04 |
| 2026-07-31 | deepseek-v4-flash | 0.93 |
| 2026-07-31 | deepseek-v4-pro | 1.30 |
| 2026-07-31 | mimo-v2.5 | 0.09 |
| 2026-08-01 | deepseek-v4-flash | 1.57 |
| 2026-08-01 | mimo-v2.5 | 0.01 |
| 2026-08-02 | deepseek-v4-flash | 1.02 |
| 2026-08-02 | mimo-v2.5 | 0.15 |
| 2026-08-03 | deepseek-v4-flash | 1.08 |
| 2026-08-03 | mimo-v2.5 | 0.06 |
| Total Tracked | $12.42 | |
| Dashboard (32%) | $19.20 |
Plugins
No response
OpenCode version
No response
Steps to reproduce
No response
Screenshot and/or share link
No response
Operating System
No response
Terminal
No response
Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon Aug 3, 2026
This issue might be a duplicate of existing issues. Please check:
Please review those issues and consider adding your data as a comment there if they describe the same problem you're experiencing.
github-actions commentedon Oct 3, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.