DeepSeek API Pricing in India
DeepSeek models are served through Lumino's OpenAI-compatible chat completions API. You change the base URL, add one API key, and send the same request shape your existing client already uses. Pricing is quoted in INR per million tokens so you can forecast spend without converting USD rates.
DeepSeek models and pricing
| Model | Input / 1M tokens | Output / 1M tokens | Context window | Max output |
|---|---|---|---|---|
| DeepSeek V4 Pro | ₹200 | ₹390 | 256,000 tokens | 16,384 tokens |
| DeepSeek V4.1 Flash | ₹30 | ₹100 | 1,048,576 tokens | 131,072 tokens |
| DeepSeek V4 Flash | ₹10 | ₹30 | 1,000,000 tokens | 65,536 tokens |
The gap between V4 Pro and V4 Flash is about 13x on input and 13x on output. Model choice is usually the single largest cost lever on a DeepSeek workload, larger than any prompt optimisation.
What a DeepSeek request costs in practice
Take a typical coding-agent turn: 2,000 input tokens of repository context plus 800 output tokens of generated code and explanation.
- On DeepSeek V4 Pro that single turn costs roughly ₹0.71 (₹200 × 2,000 / 1M + ₹390 × 800 / 1M).
- On DeepSeek V4 Flash the same turn costs about ₹0.04.
- At 500 such turns per day, Pro runs about ₹10,650 per month and Flash about ₹600.
This is why short agent loops are expensive on Pro and cheap on Flash, and why routing by task difficulty beats picking one model for everything.
Why DeepSeek output length drives your bill
DeepSeek output is priced about 2x input on Pro and 3x on Flash. Reasoning models also generate hidden reasoning tokens before the visible answer. Three patterns dominate real-world DeepSeek spend:
- Unbounded max_tokens. The model uses whatever ceiling you allow. Cap it to what the task actually needs.
- Retry loops. A failed tool call that re-sends full history bills the whole history again on every attempt.
- User regenerate. Every "try again" is a fresh billed request. Rate-limit the regenerate button, not just the API.
Trimming input context and setting a realistic max_tokens typically cuts a DeepSeek bill more than switching models.
Calling the DeepSeek API
One key covers every DeepSeek model. Send a standard OpenAI chat completions request and change only the model id.
curl https://api.luminoai.co.in/api/v1/chat/completions \
-H "Authorization: Bearer nm-your-key" \
-H "Content-Type: application/json" \
-d '{
"model": "deepseek-v4-pro",
"messages": [{"role": "user", "content": "Review this diff for race conditions."}],
"max_tokens": 2048,
"stream": true
}'
Swap deepseek-v4-pro for deepseek-v4-flash or deepseek-v4-1-flash to change tier without touching any other code.
DeepSeek API or a rented GPU?
| Decision point | Practical rule |
|---|---|
| Use the hosted DeepSeek API when | You want reasoning or coding capability through a single integration, and traffic is bursty rather than sustained. |
| Consider a rented GPU when | Utilisation is steady above roughly 60% around the clock, or you need private weights, custom sampling flags, or a self-hosted checkpoint. |
| Break-even maths | Compare monthly API spend against continuous GPU hours. On a V4 Flash class workload, self-hosting usually wins once you are running flat out for most of the month. |