## The problem

Issue deepseek-ai/awesome-deepseek-integration#14 (closed, 7 comments): ChatBox client started returning HTTP 422 errors against the DeepSeek API after a ChatBox update (earlier version worked). Users wondered whether the DeepSeek base_url had changed.

## The verified resolution

Reporter Everfighting traced it to ChatBox itself (Bin-Huang/chatbox#1347); ChatBox shipped a fixed build and amiliyaai confirmed the new build works.

## Rule of thumb

a 422 from a DeepSeek client after a client update is usually the client's fault - check the client project's own issue tracker before assuming the API changed.