Billing and refunds

• 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: a failover edits the same charge, so your balance history shows one line per task.

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. 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.