Paying to Know What You're Served

That is the DeepSeek API as people meet it, a price list with a clock on it and a set of cheaper routes to the same models. For people weighing a cheaper route to DeepSeek models, the direct API is the reference they check it against. One user asks whether DeepSeek on OpenRouter, said to be several times cheaper, delivers the same quality for coding tasks, and finds the gap strange. The question treats the direct API as the answer key. Another says anyone who skips the DeepSeek API cannot know what level of quantization they are being served, and that others could be serving a 3-bit version without saying so. These posts share one worry: that cheaper is another word for different.

The cheaper routes are collecting complaints of their own. One title reads "DeepSeek API, opencode rugpulled and the usage decreased dramatically". The week before, people were asking which providers to move to; this week the people who made the move describe a discount that came with a cost. A user who tried OpenCode Go says the performance drop was quite noticeable compared with the direct API, then tried another service where requests failed constantly, and went back to the direct API for coding tasks, calling its higher cost worth paying. In that account the direct API is the fixed point, the place the user returned to for coding after trying other routes.

The DeepSeek API is also an engine rather than a destination. People plug it into other labs' tools. One user ran it behind Claude Code through a free repository and watched a recursive loop produce output they found "kind of terrifying". What the people in these setups share is that the interface belongs to someone else and the model is the part that gets swapped. Another says you can plug the DeepSeek API into Claude Code and run two parallel sessions that hand the same document back and forth.

Whether that arrangement is a bargain depends on how you pay. One user whose Copilot credits were drained by the default models runs DeepSeek V4 Flash as a custom model with their own key, and calls it the cheapest frontier-class setup. The dispute is less about the model than about the meter. Another used the API for work other than coding and found that it significantly underperformed, and says that for coding the plans are subsidized enough that DeepSeek makes sense only in niche cases.

For agent work, the price that matters is the price of the cache. One user says agentic work depends heavily on cache reads, and that other providers charged significantly more for them than the DeepSeek API did. Cache pricing is a figure people check when they cost agentic work. A summary of the rates announced the week before led with the cache-hit prices. So the line where people say the DeepSeek API undercut other providers is the one that summary called a dramatic increase.

The audience for the API is builders. One user says the price change mainly affects coders, because the DeepSeek chatbot is free. That makes the customers people who do the arithmetic, and for some of them the arithmetic ends in shopping around. Someone running a personal bot around the clock, with background tasks and periodic checks, says DeepSeek was their go-to because it was dirt cheap and handled structured outputs well, and is looking for another primary API.

Data handling is another place people press on the reference. One user comparing routes says the direct API allows training on prompt payloads by default unless you opt out, where OpenCode Go routes through providers that follow zero data retention, and frames the choice as a trade between agent stability and what happens to the prompts. That choice is about whose terms to trust, not about which model is better. Another argues that if the standard API pricing already includes data collection, then it is just a data collection tier, and that transparent collection is a different thing from opaque collection. For both of these users, what the direct API does with prompts is part of the choice. Being the reference has a cost: the route that other routes are checked against is checked on its own terms too.