uttapen

DeepSeek V3.2 vs DeepSeek V3.2 Exp

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.

FeatureDeepSeek V3.2DeepSeek V3.2 Exp
ProviderDeepSeekDeepSeek
Model iddeepseek/deepseek-v3.2deepseek/deepseek-v3.2-exp
Context163,840 tokens163,840 tokens
Max output65,536 tokens65,536 tokens
Input / 1M tokens78,044 toman78,334 toman
Output / 1M tokens116,050 toman118,951 toman
≈ one 1,000-word request252 toman256 toman
Input caching39,022 toman / 1MNo
Image inputNoNo
File inputNoNo
Tool callingYesYes
JSON outputYesYes
Reasoning modeYesYes

Which one for what?

DeepSeek V3.2

  • Multi-step problems, maths, and tracking down a bug
  • Agents that call your own APIs and database
  • High-volume work where cost per call decides
252 toman per 1,000 words · Model page

DeepSeek V3.2 Exp

  • Multi-step problems, maths, and tracking down a bug
  • Agents that call your own APIs and database
  • High-volume work where cost per call decides
256 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": "deepseek/deepseek-v3.2",
    "messages": [{"role": "user", "content": "Introduce yourself in one sentence."}],
    "stream": true
  }'

model = "deepseek/deepseek-v3.2-exp"

More comparisons: all pairs · model rankings · full catalogue

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