Budgets and balance
Top up the workspace balance and set monthly limits per organisation, team, person and agent.
Your workspace has one balance in euros. Every chat message and agent run is priced and deducted from it. Budgets do not hold money of their own: they are monthly spending ceilings on top of that balance.
The balance
On Billing & plan you see two pots:
- Monthly balance: the usage included in your plan. It resets on the 1st of each month and is spent first. What you do not use expires.
- Extra usage: what you top up. It never expires and is used once the monthly balance is gone.
On Free there is a one-time starter balance instead of a monthly balance.
Agent runs that start by themselves, such as scheduled runs and trigger runs, are paid only from extra usage. With no extra usage left, such a run does not start and the reason is shown.
Top up
Open Billing & plan and choose Top up. Enter an amount (Custom amount) and pay by card through Stripe. The balance is added as soon as the payment clears, and you get an invoice. Save a card to top up in one click.
You can also switch on Auto Top-up. Set Top up below (€), the amount to add, and optionally Maximum per month (€). When the balance drops below your threshold, your saved card is charged; every automatic top-up gets its own invoice, mailed to the workspace admins. At the monthly maximum it stops and tells you. Without it, work stops when the balance runs out until someone tops up.
Admins can always add money. For other people it is a setting under Money rights… on the People page (May add money).
Set budgets
Open Budgets, then the Allocation tab. Budgets are optional: with none set, the workspace can spend its whole balance.
Set a workspace ceiling
Enter a monthly amount under Organisation budget (Workspace ceiling). It limits total spend in the billing period.
Give teams a limit
Under Team & Member Budgets, set a Team limit for each team. The page shows how much of the ceiling is not yet given to a team.
Give people a limit
Set a monthly limit per person. People without a team appear under Users without a team. You can set the same limit for everyone in one step.
A person on more than one team counts toward their first team only. You can set an alert threshold per limit: The limit shows Alerts at …% of limit, and Change adjusts that percentage.
Budgets for individual people are open on every plan; team budgets need Business or Enterprise. Team managers set limits for their own teams. Who may set limits is a per-person setting under Money rights….
Guardrails for agent runs
The Guardrails tab limits agent runs across the workspace: chats with an agent, board agents, scheduled runs and webhooks.
| Guardrail | What it does |
|---|---|
| Ask before an expensive run | A run expected to cost this much or more pauses and waits for approval. |
| Monthly spend ceiling | A run that would push the month past this amount pauses for approval, with a heads-up before. You can always approve and continue. |
| Runs per agent per day | Further runs that day do not start and say why. |
| Models for automations | Agents and workflows may only run on the models you tick. Chats are not affected. |
An individual agent can carry its own limits, which win over the workspace default: Spend limit per run, plus Cap per hour and Cap per day under Spend limits over time on the agent's page.
What happens when a limit is reached
- Chat. The message is not processed and the person sees that their monthly budget, or their team's, is used up, with a Manage budgets link for admins. Raise the limit or add extra usage to continue.
- Agent runs. A spend limit pauses the run and asks for approval; a daily run limit or model limit stops the run before it starts and says why.
- Balance empty. Your balance is the hard stop. You get Balance running low and Balance exhausted notifications.