Skip to content

Billing

Billing is prepaid. Each workspace holds a wallet in AUD, funded in advance, and inference is drawn down against it.

One wallet per workspace. Every API key in that workspace spends from it, and usage is debited per request as described in Usage and costs.

When the balance is exhausted, inference stops with 422 INSUFFICIENT_BALANCE — checked before the model runs, so exhausted balance costs you nothing but availability. Requests resume as soon as the wallet is funded; nothing needs to be re-enabled.

From Billing:

  • Manually, by card, between $10 and $10,000 AUD per transaction.
  • Automatically, by setting a threshold and an amount — when the balance falls below the threshold, we charge your default card and credit the wallet.

Auto top-up is the difference between a wallet that runs dry at 3am and one that doesn’t. If you rely on it, keep a valid default card on file — a failed charge is retried, but a card that has expired cannot succeed.

Credits may also reach your wallet as vouchers you redeem, or as credit grants issued by us. Both land in the same balance and are spent the same way.

Invoices are generated and emailed with the PDF attached, and are also available at Invoices.

Invoices show the amount excluding GST, the GST component, and the total including GST.

Everyone in the workspace holding the owner, admin or billing admin role, plus the workspace’s configured billing email if it differs. Set the billing email to a monitored finance address rather than an individual, so invoices survive that person changing roles.

Viewing invoices requires the billing:invoices permission, and changing payment details requires billing:update — see Team members and roles. A member or viewer cannot see invoices at all.

If a card charge fails we retry it, and email you when it fails and again if it fails finally. If you see one of those, fix the card in the app — a failed top-up does not stop existing balance from being spent, but it does mean the wallet will not be replenished.