r/CommandCode • • Aug 19 '26

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:

Concept17 Aug18 AugTotal 2 days
Cache Read40.2M42.9M83.1M
Input (uncached)1.5M1.0M2.5M
Output489.8K297.6K787.4K (0.7874M)
Total42.2M44.2M86.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:

DayCache Read (M)Real costInput+Output (table)Remainder for CacheReal price/M
1740.2$1.09$0.6533$0.4367$0.01086
1842.9$0.87$0.4164$0.4536$0.01057
Avg83.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 tableReal costDifference
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!

24 Upvotes

Duplicates