AI credits
Every AI feature costs credits. Your balance, usage and top-up settings are on the Billing tab of org settings; current pack prices are on sloose.com/pricing.
Nothing else in Sloose consumes credits — importing rows does not.
Two pools
Section titled “Two pools”| Included | Come with your plan. Reset at the start of each billing period. |
| Purchased | Bought in packs. Carry over rather than expiring at period end. |
Included credits are spent first, so a pack you bought does not evaporate at renewal while your monthly allowance goes unused.
What each feature costs
Section titled “What each feature costs”| Feature | Credits |
|---|---|
| Auto-map | 10 |
| Explain and fix | 3 |
| Value mapping | 3 |
| Formula assist | 2 |
| Chat message | 1 |
Auto-map costs the most because it does the most: a proposal for every column, validated against your real schema before you see it. It is also the one that saves the most time, and it runs once per file rather than once per field.
Prices are catalogue data rather than constants baked into the app, so they can change; the billing page shows what you actually spent.
Reserve, then settle
Section titled “Reserve, then settle”A credit is not taken when you press the button. It is reserved, and settled when the call finishes — for what the call actually used.
If a call fails, the reservation is released. You are not charged for a request the model never answered. An unsettled reservation expires on its own, so a lost connection cannot leave credits stranded.
Reading your usage
Section titled “Reading your usage”The Billing tab shows credits used this period alongside rows written, and GET /ai/usage breaks
it down by feature with token counts over any date range. Two ways to read it:
- By feature, to see where the credits go. Usually auto-map, and usually worth it.
- Over time, to spot a change — a new person using chat heavily, or a monthly file that has started needing explain-and-fix every time, which is a hint that the mapping wants fixing rather than re-explaining.
Running out
Section titled “Running out”A call with no credits left is refused with CREDITS_EXHAUSTED and a 402, carrying your balance
so the app can tell you exactly where you stand.
Nothing else stops. Imports run, projects save, the CRM is written. Only the AI features pause.
Buying a pack
Section titled “Buying a pack”An administrator buys one from the Billing tab. It opens Stripe Checkout in a new tab and returns to a page confirming what was bought. Purchased credits carry over rather than expiring at period end.
Automatic top-up
Section titled “Automatic top-up”Buy a pack automatically when the balance falls below a threshold. Configured on the Billing tab.
| Setting | What it does |
|---|---|
| Threshold | Top up when available credits fall below this. |
| Monthly cap | Never spend more than this in a calendar month. |
| Pack | Which pack to buy. |
Set the cap. It is the difference between a convenience and an unbounded standing order — an automatic top-up with no ceiling is a way to be surprised by an invoice.
Why it pauses
Section titled “Why it pauses”Automatic top-up stops in two situations, and says which:
- A charge failed — usually an expired card.
- The monthly cap was reached.
It stays paused until you change the settings, which is how you say you have dealt with it. Saving them clears the pause; there is no separate “resume” to forget about.
The tab can also attempt a top-up immediately, which is what you want after fixing a card rather than waiting for the next balance check.
Sandbox orgs
Section titled “Sandbox orgs”A sandbox spends its production org’s credits, and its usage is recorded against the sandbox. One balance, visible per org. See Sandbox orgs.
Turning it off entirely
Section titled “Turning it off entirely”A plan with no included credits and no packs bought cannot make AI calls at all. If you would rather no data ever reached a model, the org sample policy handles that directly — see Your data and the model.