uttapen

Qwen3.8 2.4T A95B API: toman pricing and code

qwen/qwen3.8-2.4t-a95b

toolsreasoningjson
Input · per 1M tokens
580,250 toman
Output · per 1M tokens
1,740,750 toman
One 1,000-word request ≈
3,017 toman

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

Qwen3.8 2.4T A95B example: a multi-step problem with reasoning

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

from openai import OpenAI

client = OpenAI(base_url="https://api.uttapen.ir/v1", api_key="sk-up-…")

resp = client.chat.completions.create(
    model="qwen/qwen3.8-2.4t-a95b",
    messages=[{"role": "user", "content": (
        "A shop has 3 warehouses. A ships 120 orders a day, B ships 85 and C ships 40. "
        "If C closes and its load is split between A and B in proportion to their capacity, how many does each ship a day? "
        "Work through it step by step and give just the two numbers at the end."
    )}],
    reasoning_effort="medium",   # low | medium | high
)
print(resp.choices[0].message.content)
# reasoning tokens count as output tokens too:
print(resp.usage.completion_tokens_details)

What is Qwen3.8 2.4T A95B good for?

Qwen3.8 2.4T A95B comes from Qwen (Alibaba); in uttapen you reach it with the model id "qwen/qwen3.8-2.4t-a95b". It accepts up to 1,048,576 tokens of input per call, so a long document or several source files fit in a single request. A single response can run to 262,144 tokens. On price it sits in the "mid-range" band — cheaper than 297 and dearer than 109 of the other paid models in the catalogue.

What you get on top of text in, text out: 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.

Input runs at 580,250 toman per 1M tokens and output at 1,740,750 — output costs 3× input, so trimming the answer saves more than trimming the prompt. It supports cached input: repeated context is billed at 72,531 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 Aion-3.0: Qwen3.8 2.4T A95B works out roughly 1.1× cheaper, and its context window is larger. 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 33 thousand-word requests on Qwen3.8 2.4T A95B, and every 1,000 toman is about 331 words of round trip. A job with one million input tokens and one million output tokens comes to 2,321,000 toman in total. Filling this model's 1,048,576-token window costs 608,436 toman on the input side alone, which is the real reason to keep conversation history short.

This id gets confused with "qwen/qwen3.8-2.4t-a95b:batch", because the underlying model is the same. The difference is the suffix: no suffix (the standard variant) against "batch". Both land at nearly the same price on a thousand-word request (3,017 and 3,017 toman). The context windows differ too: 1,048,576 against 1,010,000 tokens. Maximum answer length differs as well: 262,144 against 909,000 tokens. On parameters, this one takes seed.

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, reasoning_effort, repetition_penalty, top_k — all through the standard request body. By context size the nearest option from another provider is DeepSeek V4 Flash 0423 at 1,048,576 tokens.

Where it makes sense: product chatbots and internal assistants, where cost and quality have to balance, logic puzzles and code review, 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.8 2.4T A95B is an open-weight sparse mixture-of-experts model from Qwen and the open-weight variant of [Qwen3.8 Max](/qwen/qwen3.8-max), with 95 billion active parameters out of 2.4 trillion total. It is...

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 out1,567 toman
Summarising a ten-page document4,000 in + 600 out3,365 toman
Classifying a thousand short rows120,000 in + 20,000 out104,445 toman

Other variants of this model

Same core model, different execution terms and different price. This page is the standard variant.

VariantModel idOutput / 1MContext
batch (cheaper, slower)qwen/qwen3.8-2.4t-a95b:batch1,740,7501,010,000

Put the variant's id verbatim in the model field; nothing else in your code changes.

Frequently asked

How do I call Qwen3.8 2.4T A95B 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.8-2.4t-a95b". Nothing else in your code changes.
What does Qwen3.8 2.4T A95B cost in toman?
580,250 toman per 1M input tokens and 1,740,750 toman per 1M output tokens; a 1,000-word request is around 3,017 toman. You pay for the usage that request actually reported, and a failed request costs nothing.
How much input does Qwen3.8 2.4T A95B take?
Up to 1,048,576 tokens per request, roughly 786k words. A single answer can reach 262,144 tokens.
Does Qwen3.8 2.4T A95B support streaming and tool calling?
Streaming (stream=true) works on every model here. This one supports tool calling in the standard OpenAI shape. Structured output through response_format works too.