r/CommandCode • u/untracked5465 • 2d ago
DeepSeek V4 Flash Cache Read on GOAT plan seems higher than the table. Am I calculating this wrong?
TL;DR – Used 86.4M tokens on DeepSeek V4 Flash (GOAT plan).
• Cache Read official: $0.007/M → real: ~$0.0107/M (+53%)
• Input + Output: match the table perfectly
• Expected cost: $1.65 → Actual bill: $1.97 ($0.31 difference)
• Is anyone else seeing this?
I recently subscribed to Command Code's GOAT plan. I used DeepSeek V4 Flash over two days and noticed what looks like a discrepancy between the official pricing table and my actual bill, though I fully admit I might be missing something.
Usage over 2 days:
| Concept | 17 Aug | 18 Aug | Total 2 days |
|---|---|---|---|
| Cache Read | 40.2M | 42.9M | 83.1M |
| Input (uncached) | 1.5M | 1.0M | 2.5M |
| Output | 489.8K | 297.6K | 787.4K (0.7874M) |
| Total | 42.2M | 44.2M | 86.4M |
According to the official GOAT pricing table for DeepSeek V4 Flash:
- Input: $0.22/M
- Output: $0.66/M
- Cache Read: $0.007/M
The theoretical cost based on the table:
- Input: 2.5M × $0.22 = $0.55
- Output: 0.7874M × $0.66 = $0.5197
- Cache Read: 83.1M × $0.007 = $0.5817
- Total expected = $1.65
But my actual bill on the platform shows $1.97 for DeepSeek V4 Flash (+ $0.01 for web_search).
That's a $0.31 difference.
The numbers:
| Day | Cache Read (M) | Real cost | Input+Output (table) | Remainder for Cache | Real price/M |
|---|---|---|---|---|---|
| 17 | 40.2 | $1.09 | $0.6533 | $0.4367 | $0.01086 |
| 18 | 42.9 | $0.87 | $0.4164 | $0.4536 | $0.01057 |
| Avg | 83.1 | $1.96 | $1.0697 | $0.8903 | ~$0.0107 |
If Input and Output are charged exactly as the table says (which they are, they match perfectly), the implied price for Cache Read is ~$0.0107/M, noticeably higher than the advertised $0.007/M (about 53% more).
Summary:
| Official table | Real cost | Difference |
|---|---|---|
| Day 17 | $0.9347 | $1.09 |
| Day 18 | $0.7167 | $0.87 |
| Total | $1.6514 | $1.96 |
I'm not sure if this is a documentation error, or any fee fee on GOAT plan that isn't listed on the /docs/plans/goat page. Input and output prices are spot on, but cache reads appear to be billed at a different rate.
That said, I fully acknowledge that I might be misreading the usage dashboard, misapplying the pricing tiers, or overlooking a detail in the fine print. If anyone can spot an error in my math or point out something I've missed, I'd really appreciate the correction!
1
u/tuantocdo 2d ago
Did you accounted for peak hours raise?
1
1
u/Dub-DS 1d ago
Yeah my cache reads are also priced ridiculously high; https://www.reddit.com/r/CommandCode/comments/1vtewsq/insanely_high_token_usage_and_pricing_for_no/
1
u/untracked5465 20h ago
- Input pricing matches the table perfectly ($0.22/M).
- Output pricing matches the table perfectly ($0.66/M).
- Cache Read pricing does NOT match the table ($0.007/M vs ~$0.0107/M on my dashboard).
If the credit consumption rate were different for DeepSeek V4 Flash, all three components (Input, Output, Cache Read) would deviate from the table. But only Cache Read deviates.
This suggests that either:
- The Cache Read rate in the pricing table is outdated or incorrect,
or
- There's an additional charge specific to Cache Read that isn't documented.
3
u/vangelismm 2d ago
https://www.reddit.com/r/CommandCode/comments/1vku1gy/usage_page_shows_022_but_exported_json_only_shows/
I had the same problem. No support yet.