What the organisation consumes
Governed runs, tokens and their estimated cost, over a period; the caps in force; what the levers avoided; and, if an owner decides so, each member's usage.
What you see
- Over a period — this month, last month, 3 or 6 months —: governed runs, input and output tokens, and the estimated cost, each token at its model's price. Exportable as CSV.
- The breakdown per release and per team.
- The caps in force, each with what its own scope consumed today: the organisation for an organisation cap, each agent for an agent's cap.
- What the efficiency levers avoided, measured apart from estimated.
Credits
A credit is worth a thousandth of a euro of what the provider bills for a run's tokens, at each model's price. Cache counts at its real price, and a costlier model uses more credits.
previewToday, your tokens are billed by your provider: nothing is deducted. Credits show the same consumption in another unit.
Usage per member
- Off by default. A cost per named person is personal data: only an owner can turn it on, and the decision is logged in Governance with their name and the date.
- Once on, every member is told in Work.
- Each member always sees their own usage, whatever the owner decides.
- It counts the runs a member started — a question, a draft, a proposed action. Not what they approved, nor a schedule.