Janvia

Guides

Billing and refunds

When you are charged, how much, what a failover changes and how refunds work.

  • Dollars: your balance is in US dollars and never expires.
  • You pay the route that serves you: at submit, a task is charged the price of the first route it will try.
  • Failovers adjust the charge: before a task moves to the next route, its charge changes to that route's price. A pricier route takes only the difference; a cheaper one refunds the difference at once. If your balance can't cover the difference, that route is skipped and the next one is tried.
  • Failures are refunded in full: if the task finally fails (timeouts included), the charge is refunded completely.
  • One task, one entry: failovers and settlements edit the same charge, so your balance history shows one line per task.

Routes priced per token

Some routes' upstreams bill by the token (GPT Image on the official, Azure and Codex routes, for example), and so do we: the price is three rates, for text input, image input and output, in dollars per million tokens. The model page's price table lists them.

  • Charged an estimate at submit: from your parameters (quality, resolution, image count, reference images, prompt length) and the model's token estimate. The model page's price calculator uses the same rules.
  • Settled on the actual tokens: when the task completes, the tokens the upstream reports are priced at the route's rates, and the difference is refunded or charged. On the task object, quote_usd is the estimate, cost_usd the settled cost and usage the tokens.
  • Limits: a settlement never passes your maximum price (max_price_usd in the request, or the key's setting), and uses the rates from when you submitted. Without reported usage, the estimate stands.
  • A difference your balance can't cover is owed: it is charged anyway and your balance goes negative; the Balance page shows what you owe. While you owe, new tasks are refused and queued per-token tasks fail with their estimate refunded; a top-up pays the debt first.
  • Every other route is priced per call, image or second, and the price at submit is final.

cost_usd on the task object is what the task cost in the end, or 0 when it failed. The Balance page of the console lists every charge and refund, with a link to each task.

Key spending limits

A key with a spending limit can't charge more than the limit across all its tasks, failover differences included. A per-token settlement counts too and can take the key slightly past its limit. Past the limit, submits return 402 key_quota_exceeded; refunds of failed tasks give the allowance back.

Playground

Tasks run from a model page's playground are billed exactly like API calls.