budget-set

# Budget Set Help the user define a spend budget and turn it into a live cost guardrail on the Agent Monitor dashboard. ## Input The user provides: **$ARGUMENTS** This is the budget to set — e.g. `"$50/month"`, `"$10/week"`, or `"200000 tokens"`. If a period is omitted, treat it as a monthly budget and say so. If no number is given, read current spend first and propose a target. ## Data Sources | Endpoint | Returns | |----------|---------| | `GET /api/pricing/cost` | `{ total_cost, breakdown: [{ model, input_tokens, output_tokens, cache_read_tokens, cache_write_tokens, cost, matched_rule }] }` — current spend, used to size the budget and compute the blended $/token rate | | `GET /api/alerts/rules` | `{ rules: [{ id, name, rule_type, config, enabled, cooldown_seconds }] }` — existing rules, so you don't create a duplicate guardrail | | `POST /api/alerts/rules` | Create a rule. Body: `{ name, rule_type, config, enabled?, cooldown_seconds? }`. Returns `{ rule }` | ## How a budget becomes a rule The dashboard's alerting engine fires on **tokens**, not dollars. The spend-relevant rule type is **`token_threshold`**, whose config is `{ total_tokens }` — it fires when a session's cumulative tokens (input + output + cache_read + cache_write) cross the threshold. To turn a **dollar** budget into a token ceiling: ``` blended_rate_per_token = total_cost / total_tokens # from /api/pricing/cost token_ceiling = budget_dollars / blended_rate_per_token ``` Compute ...