uttapen

GPT-4.1 API: toman pricing and code

openai/gpt-4.1

visiontoolsjsonfiles
Input · per 1M tokens
580,250 toman
Output · per 1M tokens
2,321,000 toman
One 1,000-word request ≈
3,772 toman

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

GPT-4.1 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-4.1",
    "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-4.1 good for?

GPT-4.1 is one of OpenAI's models. Put "openai/gpt-4.1" in the model field and the rest of your code stays as it is. GPT-4.1 keeps 1,047,576 tokens in view at once, and that number is what caps the conversation history in your product. A single response can run to 32,768 tokens. On price it sits in the "mid-range" band — cheaper than 317 and dearer than 89 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. All of it works through the standard parameters of the official OpenAI SDK — no custom client, no wrapper.

Input runs at 580,250 toman per 1M tokens and output at 2,321,000 — output costs 4× input, so trimming the answer saves more than trimming the prompt. It supports cached input: repeated context is billed at 145,063 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 4.5 (batch): GPT-4.1 works out roughly 1.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 27 thousand-word requests on GPT-4.1, and every 1,000 toman is about 265 words of round trip. A job with one million input tokens and one million output tokens comes to 2,901,250 toman in total. Filling this model's 1,047,576-token window costs 607,856 toman on the input side alone, which is the real reason to keep conversation history short.

This id gets confused with "openai/gpt-4.1: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 (3,772 against 1,886 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 — all through the standard request body. It does not support include_reasoning, reasoning, 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 GLM 5.3 Flash (batch) at 1,048,575 tokens.

Where it makes sense: product chatbots and internal assistants, where cost and quality have to balance, 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-4.1 is a flagship large language model optimized for advanced instruction following, real-world software engineering, and long-context reasoning. It supports a 1 million token context window and outperforms GPT-4o and...

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,799 toman
Summarising a ten-page document4,000 in + 600 out3,714 toman
Classifying a thousand short rows120,000 in + 20,000 out116,050 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-4.1:batch1,160,5001,047,576

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

Frequently asked

How do I call GPT-4.1 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-4.1". Nothing else in your code changes.
What does GPT-4.1 cost in toman?
580,250 toman per 1M input tokens and 2,321,000 toman per 1M output tokens; a 1,000-word request is around 3,772 toman. You pay for the usage that request actually reported, and a failed request costs nothing.
How much input does GPT-4.1 take?
Up to 1,047,576 tokens per request, roughly 786k words. A single answer can reach 32,768 tokens.
Does GPT-4.1 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.