Overage cap

​

Setting the cap

• Cap amount — dollars per billing period. Above this, requests are refused.
• Notify at — threshold at which Nora emails the billing contact (default: 80% of cap).

# Cap overage at $50/month
nora billing set-overage-cap --cents 5000

# Clear cap — use plan default
nora billing set-overage-cap --clear

​

What happens at the cap

• New requests to metered surfaces return HTTP 402 Payment Required.
• Scheduled runs pause.
• Foundry pipelines pause.
• Existing in-flight runs finish normally.
• Chat traffic gets a friendly error message (“This workspace has reached its usage cap; please contact your admin”).

• The billing period rolls over (usage counter resets).
• You raise the cap.
• You clear the cap (unlimited).

​

Cap notifications

• Workspace Owners.
• Billing contact.
• Any address in Settings → Billing → Notification recipients.

Trigger: overage_percentage > 80%
Channel: Slack (#nora-billing)

​

Plan default vs. custom cap

• No cap set → uses your plan’s default overage limit.
• Cap set → your custom value wins, even if it’s lower or higher than the plan default.

​

When to set a cap

• Free / Team on a fixed budget — cap at your monthly ceiling.
• Dev / staging workspaces — cap low so a runaway script doesn’t drain budget.
• New workspaces — cap conservatively until you’ve observed usage for a month.
• Enterprise on customer contracts — cap per contract to prevent scope creep.

​

When not to cap

• Production workspaces on unpredictable traffic — a hit cap means outage. Prefer alerts + manual raise over caps that could black-hole real traffic.
• Compliance-critical workloads — where a hit cap becomes an incident. Alert + monitor instead.

​

Cap and per-run cost limits

• Flow global max cost — cap per Flow (see Flow settings).
• Agent max cost — cap per Agent (see nora agents update --set-max-cost).

• Per-Agent cap prevents any single Agent from a runaway loop.
• Flow global cap prevents any single Flow from consuming disproportionate cost.
• Overage cap prevents workspace-wide runaway.

​

Raising the cap

​

Cost forecasting

# Current overage percentage
state=$(nora billing state --json)
used=$(echo "$state" | jq '.overage_cents_used')
cap=$(echo "$state" | jq '.overage_cap_cents')
pct=$(echo "$used $cap" | awk '{ if ($2 > 0) printf "%.1f\n", $1/$2*100; else print 0 }')
echo "Overage: ${pct}%"

​

Related

• Billing overview
• Invoices
• Alerts — alert on threshold crossings.
• nora billing set-overage-cap — CLI reference.