r/opencode • u/xapep • 2d ago
The DeepSeek API price change quietly rewrote the coding-agent cost math
I've been watching this sub and r/DeepSeek over the last couple of weeks, and the same pattern keeps showing up: people who ran heavy coding-agent workloads on the official DeepSeek API are redoing their entire cost math. The interesting part isn't the price increase itself. It's that it exposed how input-heavy agent usage really is.
A few things that keep coming up:
Agent loops are much more token-hungry than chat. Harnesses (OpenCode, Cursor, Cline, Codex) re-send large conversation histories on every step. A user in r/DeepSeek reckoned their Cursor + Cline setup would pass a billion tokens at $20+ for a few weeks of work. The volume is what surprises people, not the per-token price.
Cache persistence is now the real differentiator between providers. The official API's longer cache window was a big part of its value. A provider with a shorter TTL costs more even at a lower sticker price. That's the number people forget to compare.
Peak/off-peak tiering matters more than people think. The official platform bills peak hours at roughly 2x off-peak, which means 'when' your agent runs can matter as much as 'which' model you run.
The aftermath is a wave of 'what's the OpenRouter-but-subscription option?' threads. Flat plans are now being compared against PAYG with real cache math, which is honestly healthier than the old price-per-token comparisons.
What did you switch to after the change, and what number actually decided it for you? Cache TTL, peak pricing, or raw throughput? Curious where people landed.