What problem does it solve?
Billing state in Autumn often does not match a plain reading of a plan: trials change when billing starts, entity-scoped subscriptions differ from customer-level ones, and caps, overage, and top-ups interact in non-obvious ways. This Skill provides the mental model and reference definitions needed to reason correctly about Autumn billing before writing config or calling the API.
Core Features & Use Cases
- Object graph mental model: Maps organizations, features, plans, plan items, customers, entities, subscriptions, purchases, balances, and flags, and how attach turns plan configuration into runtime customer state.
- Definition references: Loads focused references for features, plans, plan items, customize diffs, trials, customer vs entity scoping, and billing controls when reasoning about a specific object.
- Edge-case guidance: Clarifies when included usage is already a hard cap, how overage and spend limits actually behave, how trial end modes affect Stripe billing anchors, and how entity-level state overrides customer-level state.
- Use Case: A customer's usage stopped at zero even though no spend limit was set. Load this Skill to learn that
included is the cap when no overage price or overage_allowed control exists, avoiding a useless spend_limit change.
Quick Start
Ask the assistant to explain why a customer's balance stopped at zero on their current Autumn plan and what change would allow paid overage.
