How pricing works
Kyma charges per token. Every request has:- input tokens for your prompt and context
- output tokens for the model’s response
GET /v1/models or GET /v1/credits/pricing.
Very long prompts
A few models cost more per token once a single prompt passes a threshold, because the infrastructure serving them charges more there. The rates below are the standard ones, which is what almost every request pays.
The threshold is on the prompt, not the conversation, so you know which rate
applies before you send. Every other model on Kyma is a single flat rate at any
length, and
usage.cost on the response is always the exact amount charged.
Pricing per model
Cheapest useful models
Use these for bulk automation, extraction, and simple workloads.Balanced value
Use these when you want strong quality without flagship pricing.Flagship / premium
Use these when quality or capability matters more than cost. Rows showing· cached print the cached input price inline (10% of normal input — applies to repeated system prompts and tool definitions on caching-enabled models; see prompt caching).
Long-context & multimodal
Use these when context length or image input is the bottleneck.Embeddings
Embedding models turn text into vectors for retrieval. Billed on input tokens only — the response is a vector, so there is no completion side to charge for.Reranking
Scores how well each document answers a query, so a retriever’s top 50 becomes the 5 worth sending to a model. Billed on input tokens — the query plus every document you send.
For comparison, OpenAI’s
text-embedding-3-small lists at $0.02 / 1M. See the embeddings API reference.
Web search
Perplexity’s Sonar models run a live web search on every request and return cited answers. They bill two components on the same request: normal token pricing plus a flat web-search fee for the live search.
The web-search fee is flat per request — it does not scale with tokens — so a short
sonar question is dominated by the search fee, not the tokens. Every response’s usage.cost already includes it. (The GET /v1/pricing catalog lists the per-token prices above; the flat search fee is applied per request at billing time, not as a catalog field.) Standard models have no per-request fee; use Sonar only when you actually need fresh web data.
Image generation
Image models bill per image, not per token. The cost shown is exactly what you pay per image. See the Image Generation guide and the API reference.
A request with
n: 4 is billed as 4 images. gpt-image-2 requests can opt into quality: low/medium/high per call; the hold books the right tier amount up front so high-quality requests reserve $0.297 (no refund-and-rebill drift). Holds refund in full if generation fails.
What does a typical request cost?
With the $0.50 signup credit, you can make hundreds or thousands of requests depending on model choice.
How billing works
- Before each request, Kyma holds an estimate from your balance
- After the response completes, Kyma calculates the real token cost
- If the real cost is lower, the difference is refunded automatically
Credits
Credits never expire. Auto top-up is supported in the dashboard.
Video generation
Per-second models scale with theduration parameter (default 5s, max 10–15s by model). Hailuo bills flat per call.
See Video Generation. Live source:
GET /v1/pricing (video rows).
Audio
Audio splits by capability — transcription, understanding, realtime, TTS, music, voice, SFX. Speech-to-text (per minute, 1-min minimum billable)
Audio understanding (per minute)
Realtime translation (per minute)
TTS (per 1k characters)
Music
Voice services & SFX (flat per call)
Live source:
GET /v1/pricing (audio rows).
Prompt caching
Cached input tokens are charged at that model’s own cached-input rate, published beside its input rate above. There is no catalogue-wide discount: measured across the models that publish one, the cached rate runs from a tenth of the input rate up to the input rate itself. Models with no published cached rate sendpricing.cached: null.
That means:
- repeated system prompts get much cheaper
- tool definitions become cheaper over repeated runs
- long agent sessions benefit the most
Rate limits
Kyma uses a tier-based system similar to xAI and Anthropic-style paid access: your tier increases based on total credits purchased, not lifetime usage.
RPM = requests per minute
Per-model RPM = how many requests per minute a single model can take
TPM = tokens per minute across your account
There are no daily or monthly caps. Your balance and tier are the real limits.
What happens when you hit a limit?
Out of creditsRetry-After header tells you when to retry.
How to spend less
- Use cheaper models for extraction, routing, and repetitive automation
- Use
qwen-3-32binstead of a flagship if you mainly need fast coding help - Use
gemini-2.5-flashonly when long context is the real need - Use
deepseek-r1only when the task truly needs deeper reasoning - Purchase credits if you need higher rate limits, not just more balance