Skip to content
cicora.ai

RUB / 1M tokens

Public model pricing in rubles

Prices are shown per 1M tokens in RUB. Cache columns are shown only when a published rate exists.

A meter separates input, cached input, and output tokens before public RUB prices are displayed.INPUTCACHEOUTPUT
Rates describe metered completed usage; the table does not promise future availability.
Public RUB prices per 1M tokens
ModelInput / 1MOutput / 1MCache read / 1MCache write / 1MCache write 5m / 1MCache write 1h / 1M
claude-fable-5——————
claude-fable-5.1——————
claude-haiku-4.5——————
claude-opus-4.6——————
claude-opus-4.7——————
claude-opus-4.8——————
claude-opus-5——————
claude-opus-5.5——————
claude-sonnet-4.6——————
claude-sonnet-5——————
deepseek-v4.1-flash——————
deepseek-v4-flash——————
deepseek-v4-flash-0731——————
deepseek-v4-pro——————
deepseek-v4-pro-0813——————
gemini-2.5-flash——————
gemini-2.5-flash-lite——————
gemini-2.5-pro——————
gemini-3.1-flash-lite——————
gemini-3.1-pro-preview——————
gemini-3.5-flash——————
gemini-3.5-flash-lite——————
gemini-3.6-flash——————
gemini-3.7-flash——————
gemini-3.8-flash——————
gemini-3-flash-preview——————
glm-4.5——————
glm-4.5-air——————
glm-4.6——————
glm-4.7——————
glm-5——————
glm-5.1——————
glm-5.2——————
glm-5.3——————
glm-5.3-flash——————
glm-5-turbo——————
gpt-4.1——————
gpt-4.1-mini——————
gpt-4.1-nano——————
gpt-4o-mini——————
gpt-5.4——————
gpt-5.4-mini——————
gpt-5.4-nano——————
gpt-5.5——————
gpt-5.6-luna——————
gpt-5.6-sol——————
gpt-5.6-terra——————
gpt-6-astra——————
gpt-6-luna——————
gpt-6-sol——————
grok-4.3——————
grok-4.5——————
grok-4.6——————
grok-4.7——————
kimi-k2.6——————
kimi-k2.7-code——————
kimi-k3——————
mimo-v2.5——————
mimo-v2.6-flash——————
mimo-v2.6-pro——————
minimax-m2.7——————
minimax-m3——————
nemotron-3-ultra-550b-a55b——————
qwen3.7-max——————
qwen3.8-flash——————
qwen3.8-max-0902——————
Data source
Live public catalog
Catalog updated

Questions about metered pricing

Current catalog rates and request usage are the source for a charge.

An agent can make several requests, each with history and tool output. Check request history rather than only the final visible context.

In-flight requests can hold an estimated amount. The available balance reflects active reservations until the request is settled.

A failure before confirmed output or usage releases its hold. A stream that already delivered output can be charged for confirmed usage.

Check the operation status and refresh the balance. If a confirmed payment is missing, send support its payment ID, time, and receipt before paying again.

Read the full FAQ