Agents cost money each time they call a model, and for the time their sandbox runs. Eido Build records every one of those costs, and lets you cap them at four levels.
All amounts are in US dollars. The budget fields accept no other currency, so enter £20 a day as $20 a day.
Seeing what things cost#
Every cost on screen is a chip. Click it to see what it is made of: tokens by model, and compute by hours.
Costs appear on a stage, on a work item, on an agent’s runs and on conversations with Odie. Every cost comes from one ledger, with one row for each model call and each sandbox hour.
Who can see costs#
Only people with See costings on a project see its costs. That includes admins. See Users and permissions.
The caps#
| Cap | Set on | What happens at the cap |
|---|---|---|
| Per stage | The stage, in the workflow | The stage’s session stops. |
| Per agent run | The agent | The run stops. |
| Per agent day | The agent | Further runs that day do not start, and are recorded as skipped. |
| Per month | Admin → Workbenches | No new agent stage starts, in any project, until the cap is raised or the month ends. |
A session is always held to the tightest cap in force: its own, the agent’s day, or what is left of the month.
Raising a cap on one work item#
The workflow sets the cap for every work item that follows it. Sometimes one piece of work needs more.
On the work item, the cap for the current stage sits beside what that stage has spent. An admin or project admin can change it there.
- Raising it reaches the session that is already running, so a stage that stopped at its cap carries on from where it stopped.
- A cap below what has already been spent is refused.
- The change is recorded with who made it and what it was before.
Prices#
Costs are worked out from a price for each model, per million tokens.
- For models in your Foundry project, prices come from Azure’s published price list, refreshed daily.
- Claude’s prices ship with Eido Build.
- You can correct or override a price on Admin → Foundry. A change applies to costs from then on.
A model with no price is counted and shown as unpriced. It is never shown as free.
Keeping costs down#
- Start work manually. On a project set to start work manually, opening a release fills a queue, and you choose how many agent sessions run at once. See Projects.
- Write a good project description. Agents that are told what the product is spend less time finding out.
- Choose the model per stage. A code review may not need the model a design does.
- Keep documents short. Each stage starts fresh from the approved documents, so a tight plan is cheaper for every stage after it.