Comment by onlyrealcuzzo
6 hours ago
OpenRouter is complete garbage.
Buy directly from DeepSeek's API.
You can literally get overcharged 100x on DeepSeek on OpenRouter (or more).
6 hours ago
OpenRouter is complete garbage.
Buy directly from DeepSeek's API.
You can literally get overcharged 100x on DeepSeek on OpenRouter (or more).
One of the reasons I use OpenRouter is because they offer zero data retention. As far as I can tell, DeepSeek's own API doesn't support ZDR.
DeepInfra does and it's the same price. That's what I use.
Youre doing something so special you need that?
It’s a pretty common requirement in the enterprise world. If you’re processing data for enterprise customers, it’s a lot easier to retain nothing than to deal with all the compliance issues that arise if you’re retaining data.
1 reply →
I've got a toilet cam to install in your bathroom
I'm all in for saving money and _can_ move to using DS directly from them, but maybe I am missing something here:
OpenRouter Pricing:
$0.02/M input tokens $0.60/M output tokens
DeepSeek Pricing (cache miss, off-peak):
$0.15/M Input $0.60/m output
When 98.5% of my requests are cache hits (according to Pi for the last week), the cache miss price isn’t that important to me, and $0.003-0.006 per 1M input tokens is shockingly cheap.
It’s also the major difference between using DeepSeek directly vs other providers also serving it, though I have not looked lately: it’s possible other providers have matched its cache hit pricing better?
Interesting, if the cache hit is that good, I think HN convinced me to toss $20 at DS official, and see how long that lasts.
2 replies →
I've heard that certain inference providers may have different quality of caching implementations, so even if the listed numbers are as you say, the practical cache hit % you get might be significantly different/incur significantly different costs.
There’s a big difference in speed & quality between using DeepSeek API directly with DSH vs. DeepSeek in Opencode Go with Opencode CLI. Can’t tell if it’s the provider or the harness - but worth to give it a try.
DeepSeek trains on your inputs. That's why people go on OpenRouter and choose ZDR providers.
This isn't true at least on the API. If you read their privacy policy you'll see the training clause is scoped specifically to the consumer terms i.e. for the chat product. No such clause exists for the API service, and it would absolutely be required under Chinese law if it was taking place.
Contrary to popular belief, DeepSeek really aren't interested in your prompts.
Let me get this straight you guys really like deep seek because it’s open but you don’t wanna help them improve.
No, we just want a choice on how to license our work.
Why does liking a product mean you have to give them all of your data? People are so outraged at LG because they make the best TVs and people wanted their expensive product, yet some MBA convinced them they could make more money by spying on your entire household all the time.
It actually was awesome in the early Facebook days where you could have your entire phone contacts and other apps filled out with a profile picture and Birthday by connecting them together. But that relationship has been completely abused, privacy has been invaded, and my data has been sold to multiple companies.
The goal going forward is to keep that data private. If your company can't survive without it then I hope your company goes out of business
Just pin your config to a single provider, or several providers with the params `order` and `allow_fallbacks: false`. I regularly get ~98-99% cache hit rates with OpenCode. And some providers are much faster than DeepSeek; I was getting 200-300 tokens/second the other day with Together as my provider.
It's regrettable that OpenRouter doesn't even try to pin you to a single provider per session, but once you know about it, it's a problem that's easily solved.
Or.. BYOK Deepseek because OpenRouter's UX is much nicer?
Zero Data Retention and not having company source code leak to "CHINA!" (said in Trumps annoying voice) would be two reasons not to