uttapen

GPT-5.6 Sol Pro API: toman pricing and code

openai/gpt-5.6-sol-pro

visiontoolsreasoningjsonfiles
Input · per 1M tokens
580,250 toman
Output · per 1M tokens
2,901,250 toman
One 1,000-word request ≈
4,526 toman

You are billed for the usage the request actually reported. Prices follow the market. Cached input: 58,025 toman / 1M. Web search: 2,901.25 toman / request.Pricing and top-ups

GPT-5.6 Sol Pro 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": "openai/gpt-5.6-sol-pro",
    "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 GPT-5.6 Sol Pro good for?

The id for GPT-5.6 Sol Pro in our API is "openai/gpt-5.6-sol-pro", served from OpenAI. Context is 1,050,000 tokens; past that you have to summarise the history yourself. A single response can run to 128,000 tokens. On price it sits in the "mid-range" band — cheaper than 322 and dearer than 84 of the other paid models in the catalogue.

What you get on top of text in, text out: it reads images directly, which makes it a real option for invoices, forms and screenshots; it takes files such as PDFs as input; 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 2,901,250 — output costs 5× input, so trimming the answer saves more than trimming the prompt. It supports cached input: repeated context is billed at 58,025 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 Claude Sonnet 5: GPT-5.6 Sol Pro works out roughly 1× more expensive, 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 22 thousand-word requests on GPT-5.6 Sol Pro, and every 1,000 toman is about 221 words of round trip. A job with one million input tokens and one million output tokens comes to 3,481,500 toman in total. Filling this model's 1,050,000-token window costs 609,263 toman on the input side alone, which is the real reason to keep conversation history short.

This id gets confused with "openai/gpt-5.6-sol-pro:batch", because the underlying model is the same. The difference is the suffix: no suffix (the standard variant) against "batch". On a thousand-word request this variant works out 2× dearer (4,526 against 2,263 toman). On parameters, this one takes max_completion_tokens.

OpenAI has 95 models in our catalogue; the cheapest is gpt-oss-20b at 60 toman per thousand words and the dearest o1-pro at 282,872. Among the less common parameters it accepts max_completion_tokens, reasoning_effort — all through the standard request body. It does not support temperature, top_p, which most models here do, so test before switching if your code relies on them. By context size the nearest option from another provider is MiMo-V2.5 at 1,050,000 tokens.

Where it makes sense: product chatbots and internal assistants, where cost and quality have to balance, 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

GPT-5.6 Sol Pro is the same underlying model as [GPT-5.6 Sol](https://openrouter.ai/openai/gpt-5.6-sol), served with `reasoning.mode` set to `pro` for higher-quality responses on complex tasks. Learn more in OpenAI's docs: https://developers.openai.com/api/docs/guides/reasoning#reasoning-mode

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 out2,031 toman
Summarising a ten-page document4,000 in + 600 out4,062 toman
Classifying a thousand short rows120,000 in + 20,000 out127,655 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)openai/gpt-5.6-sol-pro:batch1,450,6251,050,000

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

Frequently asked

How do I call GPT-5.6 Sol Pro 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 "openai/gpt-5.6-sol-pro". Nothing else in your code changes.
What does GPT-5.6 Sol Pro cost in toman?
580,250 toman per 1M input tokens and 2,901,250 toman per 1M output tokens; a 1,000-word request is around 4,526 toman. You pay for the usage that request actually reported, and a failed request costs nothing.
How much input does GPT-5.6 Sol Pro take?
Up to 1,050,000 tokens per request, roughly 788k words. A single answer can reach 128,000 tokens.
Does GPT-5.6 Sol Pro 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.