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

# Billing and Spend Caps

> Inspect plan usage, set a hard spend cap, and know when deploys will be blocked.

Use this guide when you need to control spend for yourself, your team, or an automated workflow.

## Prerequisites

* you are authenticated with `floo auth login`
* you want to inspect current plan usage or change the monthly cap

## 1. Check Current Usage

```bash theme={null}
floo billing usage
```

The shipped CLI shows:

* current plan
* included compute for that plan
* current period spend
* current spend cap

In `--json` mode it also returns `max_spend_cap_cents`, which is useful for tooling and dashboards.

## 2. Set a Spend Cap

```bash theme={null}
floo billing spend-cap set 50
floo billing spend-cap get
```

Set the cap in dollars. Use `0` to remove the cap (no spending limit).

When the org exceeds its spend cap, deploys are blocked until the cap is raised or the next billing period begins.

## 3. Upgrade the Plan

```bash theme={null}
floo billing upgrade
floo billing upgrade --plan pro
```

The shipped plan names in the CLI are:

* `hobby`
* `pro`
* `team`

## 4. Use JSON for Automation

```bash theme={null}
floo billing usage --json 2>/dev/null | jq '.data'
floo billing spend-cap get --json 2>/dev/null | jq '.data'
floo billing spend-cap set 100 --json 2>/dev/null | jq '.data'
```

## Dashboard Surface

The shipped Billing page adds the visual view:

* current plan details
* usage charts and limits
* spend-cap UI
* upgrade and billing portal flows

The CLI is still the best surface for scripts and agent guardrails.

## Recommended Policy for Teams and Agents

1. Inspect usage after the first live deploy.
2. Set a spend cap that matches the project budget.
3. Re-check usage before increasing the cap.
4. Treat `SPEND_CAP_EXCEEDED` as an operational signal, not a transient error.