Create an API key

Gemma 3 27B API: toman pricing and code

google/gemma-3-27b-it

Image inputTool callingJSON output
Create a keyTry it
Input · per 1M tokens
27,698 toman
Output · per 1M tokens
121,177 toman
One 1,000-word request ≈
194 toman

You are billed for the usage the request actually reported. Prices follow the market. Cached input: 13,849 toman per 1M tokens.Pricing and top-ups

Gemma 3 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": "google/gemma-3-27b-it",
    "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"}}
      ]
    }]
  }'
import base64, json
from openai import OpenAI

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

img = base64.b64encode(open("factor.jpg", "rb").read()).decode()

resp = client.chat.completions.create(
    model="google/gemma-3-27b-it",
    messages=[{
        "role": "user",
        "content": [
            {"type": "text", "text": "Return the invoice number, the date and the total as JSON."},
            {"type": "image_url", "image_url": {"url": f"data:image/jpeg;base64,{img}"}},
        ],
    }],
    response_format={"type": "json_object"},
)
print(json.loads(resp.choices[0].message.content))
import OpenAI from "openai";
import { readFileSync } from "node:fs";

const client = new OpenAI({ baseURL: "https://api.uttapen.ir/v1", apiKey: "sk-up-…" });
const img = readFileSync("factor.jpg").toString("base64");

const resp = await client.chat.completions.create({
  model: "google/gemma-3-27b-it",
  messages: [{
    role: "user",
    content: [
      { type: "text", text: "Return the invoice number, the date and the total as JSON." },
      { type: "image_url", image_url: { url: `data:image/jpeg;base64,${img}` } },
    ],
  }],
  response_format: { type: "json_object" },
});
console.log(JSON.parse(resp.choices[0].message.content));

What is Gemma 3 27B good for?

Gemma 3 27B comes from Google; in uttapen you reach it with the model id "google/gemma-3-27b-it". It accepts up to 131,072 tokens of input per call, so a long document or several source files fit in a single request. A single response can run to 117,964 tokens. On price it sits in the "very cheap" band — cheaper than 326 and dearer than 71 of the other paid models in the catalogue.

Capabilities available on this id: 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. All of it works through the standard parameters of the official OpenAI SDK — no custom client, no wrapper.

For a back-of-envelope figure: about 194 toman per 1,000-word exchange (27,698 in, 121,177 out, per 1M tokens). It supports cached input: repeated context is billed at 13,849 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 DeepSeek V4.1 Flash (batch), and Gemma 3 27B costs about the same, and its context window is smaller. 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 515 thousand-word requests on Gemma 3 27B, and every 1,000 toman is about 5,155 words of round trip. A job with one million input tokens and one million output tokens comes to 148,874 toman in total. Filling this model's 131,072-token window costs 3,630 toman on the input side alone, which is the real reason to keep conversation history short.

Its nearest relative in the catalogue is "google/gemma-3-12b-it", and choosing between those two is where most people hesitate. On a thousand-word request this variant works out about 2.2× more expensive (194 against 90 toman). Maximum answer length differs as well: 117,964 against 16,384 tokens. On parameters, this one takes logprobs, top_logprobs.

Google has 43 models in our catalogue; the cheapest is Gemma 4 26B A4B at 67 toman per thousand words and the dearest Gemini 3.1 Pro Preview Custom Tools at 6,301. Among the less common parameters it accepts logit_bias, logprobs, min_p, presence_penalty, repetition_penalty, top_k — 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 Aion-2.0 at 131,072 tokens.

What to use it for: high-volume work such as classification, tagging and bulk summarising, pulling text and fields out of images, agents that reach out to APIs and databases, extracting data against a fixed schema.

Provider's own description

Gemma 3 introduces multimodality, supporting vision-language input and text outputs. It handles context windows up to 128k tokens, understands over 140 languages, and offers improved math, reasoning, and chat capabilities,...

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 out90 toman
Summarising a ten-page document4,000 in + 600 out183 toman
Classifying a thousand short rows120,000 in + 20,000 out5,747 toman

Price history

DateInput (toman/1M)Output (toman/1M)
18 Oct 202627,698121,177
7 Sep 202627,698155,799

Every price change for this model is recorded. Toman figures use today's rate.

Frequently asked

How do I call Gemma 3 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 "google/gemma-3-27b-it". Nothing else in your code changes.
What does Gemma 3 27B cost in toman?
27,698 toman per 1M input tokens and 121,177 toman per 1M output tokens; a 1,000-word request is around 194 toman. You pay for the usage that request actually reported, and a failed request costs nothing.
How much input does Gemma 3 27B take?
Up to 131,072 tokens per request, roughly 98k words. A single answer can reach 117,964 tokens.
Does Gemma 3 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.