Billing
Usage credits
How credits are granted, spent, topped up and when they expire.
3 minute read
Some actions in the app cost credits, such as generating with AI or exporting a PDF. Your workspace has one balance that every member draws from. The Credits card on the billing page shows the balance, where the credits came from, and every change to it.
Where credits come from
- Your plan. Every plan adds credits each month. On a paid plan the month starts on your billing date, and a yearly plan still gets its credits monthly. On Free and Lifetime the month is the calendar month.
- Credit packs. Anyone who manages billing can buy a pack from the billing page. Its credits arrive as soon as the payment clears, and you can buy another pack whenever you need more.
- Our team. Support can add credits as a goodwill gesture or to make up for an action that failed.
What an action costs
The billing page lists the price of each action. The workspace is charged when the action starts. If it fails on our side, the credits go back to the balance.
Some work only knows its cost when it ends, such as a long AI generation. For those we set an estimate aside first; the balance shows it as held for work in progress, and whatever the work did not use comes back as soon as it finishes.
Which credits are used first
The credits that expire first are used first, so your monthly allowance runs down before the pack you bought. Credits that never expire are used last.
When credits expire
- Monthly credits last until the end of that month, unless your plan lets them carry over (Lifetime keeps them for 90 days).
- Credit packs last a year from purchase.
We send a reminder a week before bought credits expire. Expired credits leave the balance straight away and show in the history as expired.
Automatic top-up
If your workspace pays by card through Stripe, you can have a pack bought for you whenever the balance falls to a level you choose. Open Billing → Credits → Automatic top-up, pick the pack, the balance that triggers it, and how many times a month it may happen at most. The card used is the one saved when you bought a pack or subscribed, and the card is shown before you turn this on.
If a charge is refused (an expired card, or a bank that wants you to confirm the payment), top-up pauses and everyone who manages billing gets an email. Update the card, then save the settings again to resume. You can also buy a pack by hand at any time.
Running out
On Free, an action the balance cannot cover is refused. Paid plans have a small overdraft, so the last action can finish even if it takes the balance below zero. The next credits you get pay that back first. Anyone who manages billing gets a notice when the balance runs low.
Refunds
If a credit pack is refunded in full, the credits left from it are taken back. After a partial refund you keep the credits.
For developers
GET /api/v1/credits returns the balance and each batch of credits, with what is left and when it expires. An action the balance cannot cover answers 402. Your endpoints can subscribe to credits.granted and credits.low under Settings → Webhooks.
Did this miss something? Tell us.