Choose between a recurring plan, usage, credits, balance, seats, quota, and one-time payments.
Start with the value your customer buys, not with an API method. Commet can combine a recurring base price with features, seats, or consumption, but each plan has one consumption model.
| You sell | Start with | Example |
|---|---|---|
| Access to a product or tier | Recurring plan | $49 per month for Pro |
| A measurable unit with possible overage | Metered | API calls, storage, messages |
| Product-specific units | Credits | Generations, exports, analyses |
| Monetary prepaid spend | Balance | Compute or infrastructure spend |
| Licensed users or roles | Seats | Editors, agents, workspaces |
| A hard operational allowance | Quota | Concurrent jobs or provisioned capacity |
| A single purchase without recurring access | One-time payment | Report, license, setup fee |
Seats and quota are feature behaviors, not separate plan consumption models. A plan can use Metered, Credits, or Balance and still include seat or quota features.
Start with one plan and one canonical flow. Create it in sandbox, connect one test customer, and verify checkout, access, renewal, and failure recovery before adding variants.
Use the complete examples for fixed subscriptions, metered billing, credits, balance, seats, and quota.
Next, configure the chosen model in Consumption Models and review its business rules in How Billing Works.
How is this guide?