Explains how Autumn balances, caps, overage, and billing controls govern feature usage.
npx skills add https://github.com/useautumn/autumn --skill balances
Please help me install this Agent Skill. Skill: balances Source: https://github.com/useautumn/autumn/tree/main/packages/agent-docs/generated/skills/balances Command: npx skills add https://github.com/useautumn/autumn --skill balances
Billing logic around usage limits is confusing: developers often add redundant spend limits, misunderstand when usage can pass zero, or misconfigure overage behavior. This Skill clarifies exactly how Autumn balances behave at zero and what each billing control actually does, preventing misconfigured caps and unexpected charges.
overage_allowed control permits usage past zero.overage_allowed, spend_limits, usage_limits, usage_alerts, and auto_topups, including scope (customer vs entity) and interaction rules.overage_behavior options (cap vs overflow) when tracking usage deductions that exceed the remaining balance.spend_limit is needed because the balance already stops at zero, avoiding redundant configuration.Ask how to enforce a hard usage cap on a feature in Autumn and whether a spend limit is needed.
High-intent search queries and answers about installing and using this skill.
The included allowance is already a hard cap: usage stops at zero and check returns allowed: false. You only need to avoid setting a usage-based price or the overage_allowed control; no spend_limit is required.
Only two things permit usage past zero: a usage-based price on the plan item, which bills for overage, or the overage_allowed billing control. Nothing else overrides the zero cap.
Spend limits cap overage in feature units (not dollars) and only apply when overage is permitted. Usage limits are independent hard caps on total usage over a time window, applying whether or not overage exists.
No, usage alerts only notify when usage crosses a threshold and never block usage. Blocking requires usage limits, spend limits, or simply not enabling overage.
Yes, entity-level controls can override customer-level controls for that specific entity. The exception is auto top-ups, which are customer-level only.
On track, overage_behavior controls deductions that exceed the balance: cap (default) deducts only what fits and stops at zero, while overflow deducts the full value and lets the balance go negative.
EpicenterHQConfigure Autumn usage-based billing with credit checks, plan gates, and metered AI usage.
flowgladRecord usage events for usage-based billing with idempotent transactionIds.
Kyon147Integrate Shopify billing into Laravel apps with subscriptions and route protection.
elizaOSManage Eliza Cloud apps, containers, billing, monetization, and payouts through Cloud APIs.