switchboard-100.pages.dev

propose_budget_change

Ask the operator to change a monthly spend cap — either the total across all providers (scope 'total') or one provider's cap (scope 'provider'). Like routing, this is not applied directly: a budget is a spending authorisation, so only the human can grant it. WHAT A CAP DOES: it is advisory in the sense that nothing here proxies traffic, but it is enforced as a compliance blocker — check_compliance and simulate_policy both report TOTAL_BUDGET and PROVIDER_BUDGET blockers when projected spend exceeds a cap, so a routing proposal that busts a cap will not come back clean. If the operator states a spending target in conversation, propose it as the total cap so it becomes an auditable constraint rather than something you have to remember. Returns a proposal id to poll with get_proposal_status.

Input schema

{
  "type": "object",
  "properties": {
    "scope": {
      "type": "string",
      "enum": [
        "total",
        "provider"
      ],
      "description": "'total' changes the cap across all providers; 'provider' changes one provider's cap and requires providerId."
    },
    "providerId": {
      "type": "string",
      "description": "Required when scope is 'provider'. Call list_providers for valid ids."
    },
    "monthlyBudgetUsd": {
      "type": "number",
      "description": "Proposed new monthly cap in USD."
    },
    "rationale": {
      "type": "string",
      "description": "Why this cap, tied to projected spend."
    }
  },
  "required": [
    "scope",
    "monthlyBudgetUsd",
    "rationale"
  ]
}