Creates or updates the budget configuration for an agent
Upserts the budget in place — the same call creates a budget if none exists or replaces the existing one. Once a cap is set, the execution engine rejects new runs that would push the period's accumulated cost above it, and alert thresholds fire notifications as usage crosses them. Changing the period boundary does not retroactively rebucket prior usage; the new period begins on the next billing window. Remove enforcement entirely with `DELETE /v1/tenants/{tenant}/agents/{agent}/budget`.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The agent ID.
The tenant identifier
The budget configuration.
Budget amount in USD.
doubleThreshold rules defining at which percentages notifications are sent. If null, existing thresholds are preserved on update.
When true, execution is blocked when spend reaches 100% of the budget. When false (default), only notifications are sent.
Response Body
curl -X PUT "https://api.fruxon.com/v1/tenants/string/agents/string/budget" \ -H "Content-Type: application/json" \ -d '{}'{
"agentId": "string",
"amount": 0,
"thresholdRules": [
{
"percent": 0
}
],
"enforceLimit": false,
"currentMonthlyCost": 0,
"usagePercent": 0,
"periodStart": 0,
"periodEnd": 0,
"createdAt": 0,
"modifiedAt": 0
}Removes the budget configuration for an agent
Drops all spend enforcement and alert thresholds for the agent; subsequent executions run without a cost cap. Historical cost data is unaffected and remains queryable through the revision cost endpoints. Idempotent — returns 204 whether or not a budget was configured beforehand.
Lists all collaborators for a specific agent.
Returns every user with an explicit grant on this agent along with their role (Viewer, Editor, or Admin) and joined user profile data (display name, email). Pending access requests created via `POST /v1/tenants/{tenant}/agents/{agent}/collaborators:requestAccess` are included with a pending status so admins can act on them. Tenant admins are not listed here — they have implicit access to all agents regardless of explicit grants.