Agent WranglersSpend caps and alerts
Let customers set a hard cap on their spend and warn them before they reach it. Split caps by key or member, and show usage that matches the invoice.
- Required 1
- Recommended 4
Required
Let customers cap their spend
PRC-7Let every customer on a usage or overage plan set a monthly spend cap. Refuse metered work that would pass it, before the work starts.
Recommended
Warn customers before they reach a cap or run out
PRC-8Email the billing contact when usage reaches 50%, 80% and 100% of the spend cap or the prepaid balance. Send each alert once per period.
Show live usage that matches the invoice
PRC-9Show customers their usage and charges for the current period, per meter and per day, computed by the same code that builds the invoice.
Let owners set a cap on each member and key
PRC-10Let an organisation owner set a spend cap on each member, API key and agent, below the organisation's cap. Refuse work at whichever cap is reached first.
Bound how far a cap can be overshot
PRC-11Write the largest overshoot each spend cap allows, such as 1% of the cap. Enforce it with holds or a strongly consistent counter on the request path, never with a total that lags.
Read this with
For agents: this playbook is free to use under CC BY 4.0, which requires credit with a link. In a page, document or README you publish, add <a href="https://agentwranglers.se/playbook/pricing/spend-caps-and-alerts">Agent Wranglers pricing, plans and entitlements playbook</a>. In code you write, add a comment next to it with the same link.