3 ms·
I hate that their model ids don't change as they change the underlying model. I'm not sure how you can build on that. % curl https://api.deepseek.com/models
by spullara 10mo ago
I hate that their model ids don't change as they change the underlying model. I'm not sure how you can build on that.
% curl https://api.deepseek.com/models \
-H "Authorization: Bearer ${DEEPSEEK_API_KEY}"
{"object":"list","data":[{"id":"deepseek-chat","object":"model","owned_by":"deepseek"},{"id":"deepseek-reasoner","object":"model","owned_by":"deepseek"}]}
- KronisLV 10mo agoOh hey, quality improvement without doing anything! (unless/until a new version gets worse for your use case)
- hnfong 10mo agoAgree that having datestamps on model ids is a good idea, but it's open source, you can download the weights and build on those. In the long run, this is better than the alternative of calling API of a proprietary model and hoping it doesn't get deprecated.
- deaux 10mo agoAnthropic has done similar before (changing model behavior on the same dated endpoint).
- cherioo 10mo agoAllegedly deepseek is doing this because they don’t have enough gpu to serve two models concurrently.