Caps
Guardrails for AI spend across the Balador suite.
Three additive tiers — tightest cap wins
Caps stack in layers. (1) The org-wide monthly pool (monthly allowance + purchased top-ups) is the hard ceiling. (2) Per-product caps below sub-allocate that pool so no single product can drain it. (3) Each product also enforces its own internal caps. AI actions stop as soon as any one of these is reached.
Monthly Allowed
25,000 BC
Included in your contract
Purchased
13,000 BC
From approved top-ups this cycle
Org ceiling
38,000 BC
Allowed + purchased
Cycle consumption
Consumed so far against your org ceiling this cycle
Consumed this cycle6,580 BC · 17%
of 38,000 BC org ceiling
Daily alert threshold
Notify console admins when a single day's usage crosses this
Today's usage940 BC · 78%
Crossing this doesn't block usage — it only sends a notification to Super Admins.
Per-product caps
Optional sub-allocations of the org pool. Leave blank to let a product draw freely against the org ceiling only.
AI Dashboard Generation
Used: 945 BC
Cycle-to-date8% of 12,000 BC
Feedback & Insight
Used: 535 BC
Cycle-to-date9% of 6,000 BC
Chatbot Management
Not provisionedUsed: 81 BC
Cycle-to-date3% of 3,000 BC
Allocated: 21,000 BC of org ceiling 38,000 BC