AI Settings
Read where the team's AI budget stands this month, set the cap and the warning line, read the statement per feature and model and the latest calls, and see which model each job runs on.
By the end of this page you will know where to read what the team's AI features have cost this month, how to set the cap that stops them and the line that warns before it, and how to tell which model answers each kind of request.
Every Heimdall turn, and later every assist, is costed at the model's list price and summed against the team's AI budget for the month. At the cap, every AI feature refuses until the cap is raised or the month ends. This page is where the month is read and the cap is set.
Before you begin
| You want to | You need |
|---|---|
| Read the month, the statement and the models | To belong to the team. Every member sees the page. |
| Change the cap or the warning line | To own the team, or a role that carries Manage AI budgets (ai:manage-budgets). |
Where it lives
Open Account Settings → AI. The page acts within the team marked as current; switch teams from the account menu to read another team's month.
Read the month
The Monthly budget card opens the page with a badge and two figures:
| Badge | Meaning |
|---|---|
| Within budget | A cap is set and the spend is below the warning line. |
| Nearing the cap | The spend has passed the warning line; the owner and the budget managers were told. |
| Spent | The cap is reached; every AI feature refuses until it is raised or the month ends. |
| No cap | The cap is zero: the spend is shown for the record and nothing ever refuses. |
Under the badge, $12.40 of $100.00 says what the month has cost against its cap, and a line below it reads "12% of the cap spent; the warning goes out at 80%".
Set the cap and the warning line
The form sits beside the figures for a person who may change them; everyone else reads a note saying that only the team owner or a member whose role carries Manage AI budgets can change the cap.
- Type the Cap for this month (USD). Zero means no cap.
- Type Warn at (% of the cap): the percentage at which the owner and the budget managers are told once.
- Press Save budget.
The new cap applies at once. Saving clears the month's warning and exhaustion marks, so the next crossing is announced again; lowering the cap below what is already spent stops Heimdall on its next request.
This month only
The cap you set applies to the current calendar month. The next month opens from the workspace default on its first call, so a cap raised for a heavy month does not stay raised.
Read the statement
This month lists every call of the month summed per feature and model, the dearest first:
| Column | What it shows |
|---|---|
| Feature | What the calls were for: Heimdall turns, Heimdall routing, and each assist as it lands. |
| Model | The model that answered. |
| Calls | How many calls the line sums. |
| In | The input tokens, the cached part included. |
| Out | The output tokens, the model's thinking included where it thinks. |
| Cost | What the line cost, at list price. |
A month with no call yet reads "No AI feature has been used this month."
Recent calls lists the latest calls the team made, newest first, with When in your timezone, the Feature, the Model, the Person the call was made for (a scheduled run with no person reads Scheduled), and the Cost of that one call.
Read the models
Models lists which model each job runs on, as a table of Job, Provider and Model. Heimdall picks between the simple and the involved model for each request unless a tier is pinned in its composer; the other jobs name the model their assist runs on once it lands. The table is read-only here: the models are part of the workspace's configuration.
All the fields
What happens next
- Crossing the warning line sends the AI budget alert to the owner and the budget managers in
the Notifications Center, by email, and on Telegram where they route the class there, and raises
ai.budget_warningto every endpoint subscribed to it. - Reaching the cap sends the same people "AI budget spent", raises
ai.budget_exhausted, and from the next request on Heimdall answers "This month's AI budget is spent" with a Raise it link for a person who may; the REST API and the MCP server answerAI_BUDGET_EXHAUSTED. - A change to the cap is written to the activity log on the budget, with the old and the new figure.
Heimdall on this page
Heimdall reads the month's standing with every message, so it can answer without a tool:
It cannot change the cap for you: the form on this page is the only way, so that a budget is never raised by the thing it bounds.
From the API and MCP
The budget and the statement have no endpoint or tool yet. The two events,
ai.budget_warning and
ai.budget_exhausted, carry the team, the month,
the cap, the spend and the percentage to any endpoint subscribed to them.
Permissions
| Action | Permission |
|---|---|
| Open the page | Belonging to the team |
| Change the cap or the warning | Owning the team, or ai:manage-budgets on your role |
| Use Heimdall | Owning the team, or ai:use on your role |
Frequently asked
Related
- Usage & Budgets — the meter behind the page
- The panel — what the budget line under the composer reads
- Roles — where Use AI and Manage AI budgets are granted
- Notifications — where the AI budget class is delivered
How is this guide?
Last updated on
Activity Log
Read every change recorded in your team, see who made it and whether it came from a person, a token, an agent, an integration or the system, and open an item's full history with its field-by-field changes.
API Tokens
Mint a personal access token for the REST API, the MCP server or a pipeline, scope it to a team and optionally one project, tick its abilities, and revoke it.