GigaChat 3 Pro API — price in US dollars
GigaChat 3 Pro, the working version of GigaChat: the same 262K context as the flagship, a quarter cheaper per million tokens. Connect it through the kosareva.cloud OpenAI-compatible API; companies outside Russia pay by USD invoice.
What GigaChat 3 Pro is
GigaChat 3 Pro is the working version of Sber’s GigaChat: the same context as the flagship at a lower price per million tokens. It has a 262,144-token context window, takes text in and gives text out, and belongs to the chat and text generation category. Through kosareva.cloud it is available via one OpenAI-compatible API: the same code as for OpenAI — just change base_url and the key.
GigaChat is not on OpenRouter as of October 2026, and a direct contract for the GigaChat API needs a Russian company or sole proprietor. Here a company outside Russia gets GigaChat 3 Pro with an English invoice in US dollars from Kosareva Cloud LLC (Armenia) and pays by bank transfer. Requests to GigaChat 3 Pro are processed in Russia.
One key opens more than GigaChat 3 Pro: the catalog has over a hundred models, including the other GigaChat and Yandex models. That matters more than it seems: models age within months, and moving to the next version is one line of code, not a new contract and a new integration.
GigaChat 3 Pro strengths and weaknesses
The same 262,144-token context and the same tool calling as the flagship, and a million input tokens costs $1.20 against $1.58 — a quarter less. On output the gap is larger: $2.89 against $4.73, almost 40%. On long answers this shows in the monthly bill.
The main thing to know before you connect: the vendor adds a service prompt of about 1,200 tokens to every request. We measured it: a two-letter question is billed as 1,216 input tokens. That is about $0.0015 per request however short it is, and on a stream of short requests this overhead, not the price per million, decides the bill. No backup route, the maximum answer length is not published, no cache discount.
Who it suits. Long requests: reviewing large documents, summaries of correspondence, texts in Russian. Where a request already runs to thousands of tokens, the service overhead gets lost in the total.
What to compare it with. Against GigaChat 3.5 Ultra ($1.58 / $4.73): cheaper per million, but with a service overhead almost twenty times larger. Counting input only, the overhead eats the saving up to about 3,500 tokens of your text: shorter — Ultra is cheaper, longer — Pro. When the model also writes a lot, Pro wins sooner: its output is 40% cheaper.
GigaChat 3 Pro among the GigaChat models
GigaChat 3 Pro sits between GigaChat 3.5 Ultra and GigaChat 3 Lightning: the same 262K context as both, a quarter cheaper than Ultra per million input tokens and six times more expensive than Lightning. Of the four GigaChat models it has the largest service prompt, about 1,214 tokens, so it pays off on long requests. GigaChat 2 Max is the previous generation, for existing integrations only.
GigaChat 3 Pro price in US dollars
| Input | $1.20 per 1M tokens |
| Output | $2.89 per 1M tokens |
Approximate: the catalog price (102.24 ₽ input and 246.94 ₽ output per 1M tokens) divided by 85.5 ₽ per $1, ID Bank’s non-cash rate on 3 October 2026. Your balance is kept in rubles; a USD invoice is converted at ID Bank’s non-cash rate on the invoice date. The vendor’s service prompt, about 1,214 tokens per request, is billed as input. You pay only for actual usage.
What a typical task costs on GigaChat 3 Pro
A price per million tokens says little on its own, so here are four common tasks at GigaChat 3 Pro rates: $1.20 per million input tokens and $2.89 per million output tokens, plus the vendor’s service prompt of about 1,214 input tokens on every request.
| Chat or bot answer1,000 tokens in, 500 out | $0.0041 |
| 30-page document review40,000 tokens in, a 2,000-token summary out | $0.06 |
| Article or sales proposal2,000 tokens of brief in, 4,000 out | $0.02 |
| A month of support: 1,000 requests1,500 tokens in and 400 out each | $4.40 |
Calculated from the current kosareva.cloud price list, in US dollars at 85.5 ₽ per $1, with the service prompt included.
GigaChat 3 Pro cost calculator
Move the sliders to your volume — the monthly cost in US dollars updates at once, with no sign-up.
At $1.20 per million input tokens and $2.89 per million output tokens; approximate, at 85.5 ₽ per $1. Each request also carries the vendor’s service prompt of about 1,214 input tokens — it is already in the numbers. Billed for actual usage.
How to connect GigaChat 3 Pro
Use the standard OpenAI SDK with the kosareva.cloud base_url and the model gigachat-3-pro. In existing code you change exactly two lines: the address and the key.
Python, OpenAI SDK
from openai import OpenAI
client = OpenAI(
api_key="YOUR_KOSAREVA_KEY",
base_url="https://api.kosareva.cloud/v1",
)
response = client.chat.completions.create(
model="gigachat-3-pro",
messages=[{"role": "user", "content": "Hello!"}],
)
print(response.choices[0].message.content)Python without the SDK: requests
import requests
response = requests.post(
"https://api.kosareva.cloud/v1/chat/completions",
headers={"Authorization": "Bearer YOUR_KOSAREVA_KEY"},
json={
"model": "gigachat-3-pro",
"messages": [{"role": "user", "content": "Hello!"}],
},
timeout=600,
)
print(response.json()["choices"][0]["message"]["content"])cURL
curl https://api.kosareva.cloud/v1/chat/completions \
-H "Authorization: Bearer YOUR_KOSAREVA_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"gigachat-3-pro","messages":[{"role":"user","content":"Hello!"}]}'The same key works with any client that supports an OpenAI-compatible endpoint: LangChain, LlamaIndex, Cursor, Continue, n8n. You don’t need a separate key per model — one key opens the whole catalog.
GigaChat 3 Pro endpoints and parameters
The gateway follows the OpenAI schema, so parameter names and the response format are the ones you know. One base address for every model in the catalog.
| base_url | https://api.kosareva.cloud/v1 |
| Endpoint | /chat/completions |
| Model name | gigachat-3-pro |
| Authorization | Authorization: Bearer <key> |
| Streaming | stream: true — the answer arrives as it is generated |
| Main parameters | temperature, max_tokens, top_p, stop, tools |
| Model list | GET /v1/models |
Request long answers with stream: true: with a large max_tokens, a regular request stays silent until generation ends and can hit your HTTP client’s timeout. In streaming mode the first tokens arrive within seconds, and the timeout problem goes away.
Specifications
| Provider | Sber |
| Type | Chat and text generation |
| Context | 262K tokens |
| Input | Text |
| Output | Text |
| API | OpenAI-compatible |
| Tool calling | Declared by the vendor |
| Service prompt | About 1,214 tokens per request |
| Processing | In Russia |
What GigaChat 3 Pro is good for
- Chatbots, assistants, Q&A and customer support in Russian
- Copy, newsletters, product descriptions and content marketing in Russian
- Reviews and summaries of long documents
What to keep in mind with GigaChat 3 Pro
Count your average request in tokens before you choose. If it is shorter than 3,500 tokens, the 1,200-token overhead inflates your real volume so much that the price list misleads. It’s easy to check: send a dozen real requests and look at the actual input tokens in the dashboard, not the ones you sent.
First, context runs out faster than it seems. In a dialogue the whole conversation goes into the input, not just the last message, so a long chat gets more expensive with every turn. If the history isn’t needed for the answer, trim it: savings on input tokens usually matter more than picking a cheaper model.
Second, the 262K-token window is shared between the request and the answer: the more you send, the less room the model has to generate. Set max_tokens on purpose, not “with a margin”.
Third, the balance is shared by all models in the catalog. You don’t have to decide in advance how much money to “put on GigaChat 3 Pro”: the same funds go to any other model if you switch tomorrow. Usage per model is shown in the dashboard on a separate line, with the number of requests and tokens.
GigaChat 3 Pro for companies outside Russia
GigaChat 3 Pro, the working version of GigaChat: the same 262K context as the flagship, a quarter cheaper per million tokens. Access through kosareva.cloud with an OpenAI-compatible API and a USD invoice for companies.
- Register as “Company or sole proprietor” → “In another country”: country of registration, company registration number, tax ID if you have one.
- In “Top up balance”, “Issue invoice (companies)” gives an English invoice in US dollars from Kosareva Cloud LLC (Armenia): minimum $50, due in 10 days.
- Pay by bank transfer to our USD account at ID Bank. The balance is credited after the bank confirms the payment, usually in 1–3 business days.
- Cards issued outside Russia are not accepted. Invoices are in USD; for EUR, write to us.
- Pay only for actual usage, no subscription. One OpenAI-compatible API for GigaChat 3 Pro and over a hundred other models with one key.
Contract and payment. Your contract and payment are with Kosareva Cloud LLC (Armenia), not with the model vendor. You are responsible for compliance with the rules of your jurisdiction; if in doubt, check with your counsel.
Requests to GigaChat 3 Pro are processed in Russia. If data protection rules apply to you, assess the transfer before you send personal data.
Other GigaChat models
Price per 1M input tokens. Output prices and a monthly estimate for each — on the GigaChat page.
GigaChat 3 Pro questions
How much does GigaChat 3 Pro cost?
$1.20 per 1M input tokens and $2.89 per 1M output tokens: 102.24 ₽ and 246.94 ₽ in the catalog, converted at 85.5 ₽ per $1 (ID Bank’s non-cash rate on 3 October 2026). The vendor’s service prompt adds about 1,214 input tokens to each request. You pay only for the tokens you use.
How do I connect GigaChat 3 Pro by API?
Register at kosareva.cloud, create a key, set base_url https://api.kosareva.cloud/v1 and the model gigachat-3-pro in the standard OpenAI SDK.
What is the context size of GigaChat 3 Pro?
262,144 tokens, shared between the prompt and the answer.
Who is GigaChat 3 Pro for, and where is it weaker?
Long requests: reviewing large documents, summaries of correspondence, texts in Russian. Its weak point is the service prompt of about 1,200 tokens the vendor adds to every request: on short requests it decides the bill. No backup route and no cache discount.
Which models should I compare GigaChat 3 Pro with?
With GigaChat 3.5 Ultra ($1.58 / $4.73): Pro is cheaper per million, but on input alone Ultra is cheaper for requests shorter than about 3,500 tokens because of Pro’s service prompt. With GigaChat 3 Lightning ($0.20 for input and output): Lightning is cheaper at any request size, but it is a much smaller model.
Why does the dashboard show more input tokens than I sent?
The vendor adds its own service prompt to every request to GigaChat 3 Pro, and it is billed as input: about 1,214 tokens by our measurement on 20 September 2026. Look at the actual input tokens in the dashboard before you estimate a monthly bill.
Where are requests to GigaChat 3 Pro processed?
In Russia. If data protection rules apply to you, assess the transfer before sending personal data. You are responsible for compliance with the rules of your jurisdiction.
Can a company in the EU use GigaChat 3 Pro?
Yes. Your contract and payment are with Kosareva Cloud LLC (Armenia), not with the model vendor. Whether your own compliance rules allow it is for you to check, with your counsel if needed.
How does a company outside Russia pay?
Register as “Company or sole proprietor” → “In another country”, then click “Issue invoice (companies)” in “Top up balance”. You get an English invoice in US dollars from Kosareva Cloud LLC (Armenia), minimum $50, due in 10 days. The balance is credited after the bank confirms the payment, usually in 1–3 business days. Cards issued outside Russia are not accepted.
Connect GigaChat 3 Pro in a couple of minutes
Get an API key and call GigaChat 3 Pro through an OpenAI-compatible endpoint. Companies outside Russia pay by USD invoice. Questions: ceo@kosareva.cloud or @kosareva_cloud in Telegram.