uttapen

Qwen3 Max vs DeepSeek V3

Both sit behind the same key and the same code on uttapen — the only thing that changes is the model string, so you can run each of them against your own workload without touching anything else. On cost, DeepSeek V3 comes out about 3.9× cheaper.

FeatureQwen3 MaxDeepSeek V3
ProviderQwen (Alibaba)DeepSeek
Model idqwen/qwen3-maxdeepseek/deepseek-chat
Context262,144 tokens163,840 tokens
Max output65,536 tokens16,384 tokens
Input / 1M tokens226,298 toman92,840 toman
Output / 1M tokens1,131,488 toman258,211 toman
≈ one 1,000-word request1,765 toman456 toman
Input caching45,260 toman / 1MNo
Image inputNoNo
File inputNoNo
Tool callingYesYes
JSON outputYesYes
Reasoning modeNoNo

Which one for what?

Qwen3 Max

  • Whole documents or a codebase in a single request
  • Agents that call your own APIs and database
1,765 toman per 1,000 words · Model page

DeepSeek V3

  • Agents that call your own APIs and database
  • High-volume work where cost per call decides
456 toman per 1,000 words · Model page

Run both with the same code

Swap the model value between the two ids and send the same request twice; what each answer cost comes back in the X-Uttapen-Cost-Toman header.

curl https://api.uttapen.ir/v1/chat/completions \
  -H "Authorization: Bearer sk-up-…" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "qwen/qwen3-max",
    "messages": [{"role": "user", "content": "Introduce yourself in one sentence."}],
    "stream": true
  }'

model = "deepseek/deepseek-chat"

More comparisons: all pairs · model rankings · full catalogue

base_url = https://api.uttapen.ir/v1