> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pipecat.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# pipecat cloud spend-limit

> pipecat cloud spend-limit sets, shows, and clears an organization's spending cap, blocking new sessions once the cap is reached.

The `spend-limit` command group caps what an organization can spend in a billing period. Once the cap is reached, new sessions are blocked; sessions already running are not interrupted.

It's the backstop for a misconfiguration — a runaway `min-agents`, a loop that starts sessions — rather than a substitute for [right-sizing your deployment](/pipecat-cloud/fundamentals/scaling).

## show

Show the current spend limit and usage.

**Usage:**

```shell theme={null}
pipecat cloud spend-limit show [OPTIONS]
```

**Options:**

<ParamField path="--organization / -o" type="string">
  Organization to query. If not provided, uses the current organization from
  your configuration.
</ParamField>

<ParamField path="--json" type="boolean" default="false" deprecated>
  Deprecated alias for `--output json`. Use the [global output
  mode](/api-reference/cli/cloud/output) instead.
</ParamField>

Reports the limit, current spend, the billing period it covers, and whether the
organization is currently blocked. An organization with no limit set shows
`no limit set` rather than an error.

## set

Set or update the spend limit.

**Usage:**

```shell theme={null}
pipecat cloud spend-limit set [ARGS] [OPTIONS]
```

**Arguments:**

<ParamField path="amount" type="string" required>
  Limit in dollars, as a non-negative number with at most two decimal places —
  `50` or `12.34`. More precision than that is rejected.
</ParamField>

**Options:**

<ParamField path="--organization / -o" type="string">
  Organization to update. If not provided, uses the current organization from
  your configuration.
</ParamField>

<ParamField path="--yes / -y" type="boolean" default="false">
  Skip the confirmation prompt.
</ParamField>

```shell theme={null}
pipecat cloud spend-limit set 250
```

### When it asks for confirmation

Raising a limit, or setting one for the first time, applies without a prompt.
Two cases prompt because they block new sessions immediately:

* **Setting the limit to `0`**, which blocks everything until you raise it.
* **Setting a limit below current spend**, which blocks new sessions for the
  rest of the period.

<Tip>
  Only those two cases need `--yes` in CI. A script that raises a limit works
  non-interactively without it.
</Tip>

## clear

Remove the spend limit.

**Usage:**

```shell theme={null}
pipecat cloud spend-limit clear [OPTIONS]
```

**Options:**

<ParamField path="--organization / -o" type="string">
  Organization to update. If not provided, uses the current organization from
  your configuration.
</ParamField>

<ParamField path="--yes / -y" type="boolean" default="false">
  Skip the confirmation prompt.
</ParamField>

New sessions stop being capped. This always prompts, so `--yes` is required to
run it non-interactively.

## More Information

<CardGroup cols={2}>
  <Card title="Scaling and capacity" icon="chart-line" href="/pipecat-cloud/fundamentals/scaling">
    Right-size `min-agents` and `max-agents` so the cap stays a backstop
  </Card>

  <Card title="Output modes and exit codes" icon="terminal" href="/api-reference/cli/cloud/output">
    Read the limit programmatically with `--output json`
  </Card>
</CardGroup>