← Help

AI spend and budgets

See what llamas' cloud work costs by project, key, llama and person, and set monthly budgets.

  1. In an organization, owners and admins see what llamas’ work on the company’s keys costs: Settings → AI spend.
  2. Each project shows which key pays for it (Paid with) and what it spent this month.
  3. Budget / month (Business): at 80% owners and admins get an email; at 100% llamas stop starting new work on the company’s keys for that project.
  4. Cap per task: the most one llama may spend on a single piece of work, so a runaway task can’t use up a budget.
  5. See the spend by key, by llama and by person, and the costliest tasks. Export is a spreadsheet of every run.
  6. The numbers are estimates at Claude’s list prices; your Anthropic Console has the real bill.

AI spend and budgets

In an organization, owners and admins see what llamas’ work on the company’s keys costs in Settings → AI spend (Team, Business and Enterprise).

What it shows, for the month you pick (the arrows go back and forth):

  • the total, and how many runs on the company’s keys;
  • each project: which company key pays for it (Paid with), and what it spent;
  • the spend by key and by llama, and the month’s costliest tasks;
  • with Business and Enterprise: who asked for the work, and Export, a spreadsheet of every run for billing clients or teams.

A task’s page also shows what its work on the company’s keys has cost (AI cost), for owners and admins.

The numbers are estimates from each run’s tokens at Claude’s list prices; your Anthropic Console has the real bill. Months are calendar months in UTC.

Llamas on Macs count here when the company rule has them think with the company’s keys (Settings → AI keys → Llamas on Macs). On their owner’s own Claude Code or Codex sign-in, the company doesn’t pay for them, so they aren’t counted.

Monthly budgets (Business and Enterprise): type an amount in US dollars in a project’s Budget / month box and press Enter.

  • At 80%, owners and admins get an email.
  • At 100%, they get another, and llamas stop starting new work on the company’s keys for that project: in the cloud, and on Macs under the company rule. The llama says why in the chat. Work already running finishes.
  • It starts again next month, or as soon as you raise the budget. Clear the box for no budget.
  • A llama on its owner’s own sign-in, on a sleeping Mac, waits for its Mac instead of working in the cloud.

Cap per task (Business and Enterprise): the most one llama may spend on a single piece of work, in the cloud or on a Mac under the company rule. When it gets there, it stops and says so, so a runaway task can’t use up a budget. Leave it empty for no cap.

Who sees costs: owners and admins. Members and guests see what llamas did, not what it cost.

Tip: Anthropic’s Console can hold a separate workspace per team, each with its own spend limit and keys. One Console workspace per project key gives you a hard limit at Anthropic as well as in Llamabyt.

More in Your Mac and the cloud

Didn’t find it?

Ask Yarvi at the bottom right of the app, or write to us.

Write to us