uttapen

Qwen3.6 27B API: toman pricing and code

qwen/qwen3.6-27b

visiontoolsreasoningjson
Input · per 1M tokens
87,038 toman
Output · per 1M tokens
580,250 toman
One 1,000-word request ≈
867 toman

You are billed for the usage the request actually reported. Prices follow the market. Cached input: 8,704 toman / 1M.Pricing and top-ups

Qwen3.6 27B example: reading an image into JSON

The example is picked from this model's own capabilities. Drop in your key and it runs as is.

# tip: a data URI works too — base64 the file and prefix it with data:image/jpeg;base64,
curl https://api.uttapen.ir/v1/chat/completions \
  -H "Authorization: Bearer sk-up-…" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "qwen/qwen3.6-27b",
    "messages": [{
      "role": "user",
      "content": [
        {"type": "text", "text": "Return only the invoice number and the total, as JSON."},
        {"type": "image_url", "image_url": {"url": "https://example.com/factor.jpg"}}
      ]
    }]
  }'

What is Qwen3.6 27B good for?

Qwen (Alibaba) publishes this model; we expose it under the id "qwen/qwen3.6-27b". Its context window is 262,144 tokens, roughly 197k English words in one request. A single response can run to 65,536 tokens. On price it sits in the "cheap" band — cheaper than 200 and dearer than 206 of the other paid models in the catalogue.

What it can do beyond plain text: it reads images directly, which makes it a real option for invoices, forms and screenshots; it supports tool calling, so it can invoke your own functions with valid arguments; it returns schema-valid JSON through response_format, ready to hand to your code; it has a reasoning mode that pays off on multi-step problems, maths and debugging. All of it works through the standard parameters of the official OpenAI SDK — no custom client, no wrapper. Keep in mind that reasoning tokens are output tokens and do appear on the bill.

Pricing is 87,038 toman per 1M input tokens and 580,250 per 1M output tokens. A 1,000-word round trip on Qwen3.6 27B lands near 867 toman. It supports cached input: repeated context is billed at 8,704 toman per 1M, which matters a lot if your system prompt is long. You are always charged for the usage the request actually reported, never for the estimate, and a failed request costs nothing.

The closest alternative with the same capabilities from a different provider is Seed 1.6: Qwen3.6 27B works out roughly 1× more expensive, and its context window is the same size. Both run on the same key and the same code, so trying the other one is a single string change.

To make the figure concrete: 100,000 toman of credit buys roughly 115 thousand-word requests on Qwen3.6 27B, and every 1,000 toman is about 1,153 words of round trip. A job with one million input tokens and one million output tokens comes to 667,288 toman in total. Filling this model's 262,144-token window costs 22,816 toman on the input side alone, which is the real reason to keep conversation history short.

Its nearest relative in the catalogue is "qwen/qwen3-vl-30b-a3b-thinking", and choosing between those two is where most people hesitate. Both land at nearly the same price on a thousand-word request (867 and 981 toman). Maximum answer length differs as well: 65,536 against 32,768 tokens. On parameters, this one takes logit_bias, min_p, repetition_penalty.

Qwen (Alibaba) has 53 models in our catalogue; the cheapest is Qwen3.7 Flash at 60 toman per thousand words and the dearest Qwen3.8 Max (0902) at 3,017. Among the less common parameters it accepts logit_bias, logprobs, min_p, repetition_penalty, top_k, top_logprobs — all through the standard request body. By context size the nearest option from another provider is Trinity Large Thinking at 262,144 tokens.

Good fits: high-volume work such as classification, tagging and bulk summarising, logic puzzles and code review, pulling text and fields out of images, agents that reach out to APIs and databases, extracting data against a fixed schema, analysing a long document or codebase in one request.

Provider's own description

Qwen3.6 27B is a dense 27-billion-parameter language model from the Qwen Team at Alibaba, released in April 2026. It features hybrid multimodal capabilities — accepting text, image, and video inputs...

Three real jobs, priced on this model

Each figure is derived from the prices above and moves when they do.

JobTokensCost
One chat turn with a medium history1,500 in + 400 out363 toman
Summarising a ten-page document4,000 in + 600 out696 toman
Classifying a thousand short rows120,000 in + 20,000 out22,050 toman

Frequently asked

How do I call Qwen3.6 27B from Iran?
Sign up with your mobile number, top the wallet up in toman, create an API key, then in the official OpenAI SDK point base_url at https://api.uttapen.ir/v1 and set model to "qwen/qwen3.6-27b". Nothing else in your code changes.
What does Qwen3.6 27B cost in toman?
87,038 toman per 1M input tokens and 580,250 toman per 1M output tokens; a 1,000-word request is around 867 toman. You pay for the usage that request actually reported, and a failed request costs nothing.
How much input does Qwen3.6 27B take?
Up to 262,144 tokens per request, roughly 197k words. A single answer can reach 65,536 tokens.
Does Qwen3.6 27B support streaming and tool calling?
Streaming (stream=true) works on every model here. This one supports tool calling in the standard OpenAI shape. Image input is accepted through image_url, as a data URI or a public URL. Structured output through response_format works too.