Comment by sparkling
7 hours ago
Yes, but with subpar caching and higher cached token pricing, compared to directly using the DeepSeek platform.
7 hours ago
Yes, but with subpar caching and higher cached token pricing, compared to directly using the DeepSeek platform.
For caching, only if you don't specify your preferred providers and let OpenRouter route each request itself. I have stuff like this in my OpenCode config for each model I use and I regularly get ~90-95% cache hit rates.
It still won't be quite as high as you'd get by just using DeepSeek because occasionally a request will fail and you'll get routed to a backup provider with nothing cached, but it's close enough not to matter in most instances.
But I can't argue with the lower off-peak pricing when using DeepSeek directly. The downside is they train their models on your input, which might be a deal-breaker for many users (as it is for me).