Each API Product Plan may have its own Revenue Model. Apiable supports the following models:
No Monetization / Free
Contract
Flat Fee
Usage Based:
Graduated
Volume
Flat Fee with overage
No Monetization / Free
As the name indicates, this Product Plan is free to use. Free plans are common alongside paid plans.
Contract
Use Contract if you plan to handle API Monetization as part of a new or existing contract in your own backend. String overrides are provided for this Monetization Model.
It's also possible to change the behavior of the Call to Action (CTA) and redirect your customer to finalize the contract processing.
Flat Fee
Charge your customers a Monthly Flat Fee for accessing your APIs. This works well with usage limits set on the API Product Plan.
Usage Based
In arrears
Charge your customers once at the end of the billing period based on the amount they consumed in this period.
Apiable offers two different models for in-arrears billing:
Volume
With volume-based pricing, the subscription item is billed at the tier corresponding to the amount of usage at the end of the period.
This model rewards the customer if they can get to the next tier before the end of the month, as their overall bill will be cheaper.
Graduated
Charges for usage in each tier instead of applying a single price to all usage. This model may result in a better deal for the customer, as they benefit from a discount on each tier within the plan.
Up-front
Charge your customers for their usage up front and the rest at the end of the billing period.
Flat Fee with Overage model
In this model, you establish a fixed monthly fee for your service at the start of each billing cycle. This fee includes a certain level of usage entitlement, and any usage exceeding this limit (overage) will be billed at the end of the period. For example, if you have a product listed at 400 USD per month that includes 200,000 API calls, any API calls over that amount will be charged extra based on the amount you stipulate.
Use up-front billing if your API products are open to potential abuse, e.g., developers making many API calls they do not intend to pay for.