# SPEND_CAP_REACHED

**What it means.** This would cost more than the account's spending limit allows this month, so it was not started.

**What to do.** Nothing was charged and nothing was started. No code change will help. Use above a plan is paid from the account's Uarpie credit, up to the spending limit the owner sets for the month: the owner can raise the limit or top up the credit in the dashboard, under Billing. Tell the person it was refused, and why.

- HTTP status: 403
- Retryable after applying the fix: no

Every failure from the CLI or an MCP tool has this shape:

```json
{
  "ok": false,
  "code": "SPEND_CAP_REACHED",
  "message": "This would cost more than the account's spending limit allows this month, so it was not started.",
  "fix": "Nothing was charged and nothing was started. No code change will help. Use above a plan is paid from the account's Uarpie credit, up to the spending limit the owner sets for the month: the owner can raise the limit or top up the credit in the dashboard, under Billing. Tell the person it was refused, and why.",
  "file": "<where to edit, when known>",
  "retryable": false,
  "docs": "https://docs.uarpie.app/errors/SPEND_CAP_REACHED"
}
```

Apply `fix` (edit `file` when it is given), then run the same command again.