Skip to main content
Org-level spend caps let agents deploy autonomously without runaway costs. Set a monthly limit, get alerts at 75%, and enforce a hard stop at 100%.

​
Why this matters for agents

Agents deploy apps. Agents scale apps. Without budget controls, an agent could spin up resources that cost more than expected. Spend caps let you give agents autonomy with guardrails.

​
Set a spend cap

Set a monthly spend cap in dollars: 
floo billing spend-cap set 50

Spend cap set to $50.00/month.

​
How it works

ThresholdAction
75% of capAlert notification sent
100% of capDeploys are blocked — no further compute charges

​
Check usage

floo billing usage

Plan: Pro ($20/mo)
Current spend: $12.40
Spend cap: $50.00/month
Usage: 25% of cap

​
Remove cap

floo billing spend-cap set 0

​
Compute rates

ResourceRateMonthly equivalent
vCPU$0.00000772/sec~$20/mo per vCPU
Memory$0.00000386/GB-sec~$10/mo per GB

​
For agents

# Set spend cap
floo billing spend-cap set 50 --json

# Check current usage
floo billing usage --json 2>/dev/null | jq '.data'

# Check spend cap
floo billing spend-cap get --json 2>/dev/null | jq '.data'
Agents should set a spend cap after creating their first app: 
floo deploy --app my-agent-app --json
floo billing spend-cap set 20 --json
See the full billing CLI reference for all commands.