Never Hit a DeepSeek 402 Mid-Run

The DeepSeek API runs on a prepaid balance. You add credits, and every call deducts from that balance based on the input and output tokens it uses. Your balance is the sum of granted credits and topped-up credits, and once it reaches zero, requests stop going through.

Granted balance is free or promotional credit DeepSeek adds to your account; topped-up balance is what you paid for. The balance API reports them as separate fields, and your total balance is the two combined. Granted credit is generally spent first and can carry an expiry date, while paid credit stays until you use it.

You can open the usage page at platform.deepseek.com, or call the balance endpoint directly at GET https://api.deepseek.com/user/balance with your API key as a Bearer token. CostGoat runs that call for you and keeps your live balance on your desktop, so you never have to log in to check.

DeepSeek returns HTTP 402 with an 'Insufficient Balance' message once your account balance reaches zero, and every request fails until you top up. It usually lands mid-workflow with no warning. CostGoat watches your balance and alerts you at a threshold you choose, so you refill before the 402 ever shows up.

Topped-up credits that you paid for do not expire and stay on your account until they are used. Granted or promotional credits often come with an expiry date set by DeepSeek. CostGoat shows your combined balance so you can spend expiring credit first.