uttapen

Reka Flash 3 vs UI-TARS 7B

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.

FeatureReka Flash 3UI-TARS 7B
ProviderRekaByteDance
Model idrekaai/reka-flash-3bytedance/ui-tars-1.5-7b
Context65,536 tokens128,000 tokens
Max output58,982 tokens2,048 tokens
Input / 1M tokens29,013 toman29,013 toman
Output / 1M tokens58,025 toman58,025 toman
≈ one 1,000-word request113 toman113 toman
Input cachingNo29,013 toman / 1M
Image inputNoYes
File inputNoNo
Tool callingNoNo
JSON outputYesYes
Reasoning modeYesNo

Which one for what?

Reka Flash 3

  • Multi-step problems, maths, and tracking down a bug
  • High-volume work where cost per call decides
113 toman per 1,000 words · Model page

UI-TARS 7B

  • Reading screenshots, invoices, and scanned forms
  • High-volume work where cost per call decides
113 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": "rekaai/reka-flash-3",
    "messages": [{"role": "user", "content": "Introduce yourself in one sentence."}],
    "stream": true
  }'

model = "bytedance/ui-tars-1.5-7b"

More comparisons: all pairs · model rankings · full catalogue

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