uttapen

Sonar vs DeepSeek V3 0324

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 0324 comes out about 1.6× cheaper.

FeatureSonarDeepSeek V3 0324
ProviderPerplexityDeepSeek
Model idperplexity/sonardeepseek/deepseek-chat-v3-0324
Context127,072 tokens163,840 tokens
Max output114,364 tokens147,456 tokens
Input / 1M tokens290,125 toman72,531 toman
Output / 1M tokens290,125 toman290,125 toman
≈ one 1,000-word request754 toman471 toman
Input cachingNoNo
Image inputYesNo
File inputNoNo
Tool callingNoYes
JSON outputNoYes
Reasoning modeNoNo

Which one for what?

Sonar

  • Reading screenshots, invoices, and scanned forms
754 toman per 1,000 words · Model page

DeepSeek V3 0324

  • Agents that call your own APIs and database
  • High-volume work where cost per call decides
471 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": "perplexity/sonar",
    "messages": [{"role": "user", "content": "Introduce yourself in one sentence."}],
    "stream": true
  }'

model = "deepseek/deepseek-chat-v3-0324"

More comparisons: all pairs · model rankings · full catalogue

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