Feature · Settings
Usage & spend
See worker time, tokens, tools and model costs. Set spend limits.
How it works
The limits
- Organization daily budget: what every worker together can spend in one UTC day. Set it in the Defaults card on Settings. $0 stops all model spend.
- Worker daily budget and per-item budget: on the worker's Governance settings. 0 blocks all spend for that worker.
- Item budget: a work item can carry its own cap.
- Model account budgets: daily and monthly limits per account. See Model accounts and API keys.
- Ask above: one spend above this amount asks you first. See The Always ask list.
A worker's limits are also bounded by every manager above it, unless limits.inherit is "Own limits only".
Defaults
- A new organization from sign-up starts with the sign-up daily budget that your Crewshal server sets. By default it is $2 a day.
- Other organizations use the platform default, $5 a day by default.
- The recommended setup can suggest another value. See Recommended setup.
How it works
Crewshal reserves the spend before each call. When a limit cannot hold the call, Crewshal refuses it. When Crewshal cannot read the budget records, it refuses the spend, to be safe.
See where the money went
Budgets & Spend shows spend per day, by provider and model, top spenders, by purpose and per task, over 7, 30 or 90 days. The meters say Within budget, Near the limit or Limit reached: new spend is refused.
When a limit is reached
See Out of budget.
From the help article Budgets and spend limits, checked against the product on .
What you can do
The operations this feature's screens call. Each one is POST /api/<name>, and the badge says who may call it.
ViewergetSpendSummaryGets the spend summary.
Types:
GetSpendSummaryRequestreturnsSpendSummaryResponse
ViewergetTaskMetricsGets task metrics.
Types:
GetTaskMetricsRequestreturnsTaskMetricsResponse
ViewergetWorkerInsightsGets worker insights.
Types:
GetWorkerInsightsRequestreturnsWorkerInsightsResponse
ViewergetSpendSavingsGets spend savings.
Types:
GetSpendSavingsRequestreturnsSpendSavingsResponse
ViewergetOrgSettingsGets org settings.
Types:
{ includePanels?: true }returnsOrgSettingsDto
AdminsetEffortBaselineSets the effort baseline.
Types:
SetEffortBaselineRequestreturnsEffortBaselinesResponse
ViewerlistEffortBaselinesLists effort baselines.
Types:
EmptyRequestreturnsEffortBaselinesResponse
ViewerNo API tokensrecordMyMeasuredEffortRecords a my measured effort.
Types:
RecordMyMeasuredEffortRequestreturnsRecordMyMeasuredEffortResponse
ViewerNo API tokensdeleteMyMeasuredEffortDeletes the my measured effort.
Types:
EmptyRequestreturnsEffortBaselinesResponse
ViewergetLiveSpendGets live spend.
Types:
GetLiveSpendRequestreturnsLiveSpendResponse
ViewerlistWorkItemDelegatesLists work item delegates.
Types:
ListWorkItemDelegatesRequestreturnsWorkItemDelegatesDto
ViewerlistRolesLists roles.
Types:
EmptyRequestreturnsListResponse<RoleDto>
AdminNo API tokensupdateOrgSettingsUpdates org settings.
Types:
UpdateOrgSettingsRequestreturnsOrgSettingsDto
ViewergetOrgConfigGets org config.
Types:
GetOrgConfigRequestreturnsOrgConfigView
AdminsetOrgConfigSets org config.
Types:
SetOrgConfigRequestreturnsOrgConfigView
ViewerlistEventsLists events.
Types:
ListEventsRequestreturnsPageResponse<AuditEvent>
ViewerlistMembersLists members.
Types:
EmptyRequestreturnsListMembersResponse
Screens
What it records
The feature writes these events to the audit log, the permanent record of what happened.
- Policy changed
- Action denied
- Approval expired
- Approval received
- Audit chain verified
- Budget reserved
- Checkpoint saved
- Context retrieved
- Decision made
- Delegate ended
- Effort baseline changed
- Evaluation recorded