Credits & Billing

You buy prepaid credits. Requests debit them exactly. When the balance reaches zero, requests stop. There is no overage and no end-of-month invoice. Every charge can be recomputed from the rate card and each response's usage object.

Where billing lives#

Team admins use the billing page to add credits and change payment details. Members see the shared balance on the usage page. Only admins can buy credits or change the card on file.

Request receipts#

Open any row in the request log for a receipt: route, model, attempts, cached tokens, reasoning tokens, answer tokens, time to first token, throughput, and the charge priced term by term against the rate card. Uncharged requests say why instead.

The receipt carries the request's Inference-Id, the same value your client logged. Quote it to support if a receipt disagrees with your records.

Topping up#

Pick an amount on the billing page, pay by card on Stripe, and you are back on the billing page with the credits on your Team as soon as the payment clears.

Auto top-off#

With a card on file, an admin can set an amount and a threshold. When the balance drops below the threshold, the card is charged and credits are added. A fast burn can still reach zero between checks.

When credits run out#

Requests return 429 budget_exceeded. Nothing is charged past your balance. The console warns as the balance runs low. Team admins get an email before the stop and another at it.

Key budgets#

Every key can carry its own budget: a ceiling on what that one key may spend. A buggy key with a $20 budget can spend at most $20 of your balance.

The budget is a cap within the team's credits. The key still spends from the team balance; the budget limits how much of it that key can use.

Setting one#

On the API Keys page, enter an amount beside the key name when creating it. Leave it blank for full team-balance access. The Budget column shows what each key has left. Click it to change or clear the budget.

Budgets range from $0.01 to $100,000.