Metered billing is a pricing model where customers receive an included amount of usage with their plan and pay for anything beyond that threshold at the end of the billing period. The system tracks consumption throughout the cycle, and when the period closes, any overage is calculated and added to the next invoice.
How metered billing works
A metered plan has three components: a base price charged in advance, an included usage quota, and an overage rate for consumption beyond the quota.
At the start of each billing period, the customer pays the base price and receives their included usage. Throughout the period, the system tracks every unit of consumption. When the period ends, the system compares actual usage against the included amount. If the customer stayed within the quota, they pay nothing extra. If they exceeded it, the overage is multiplied by the per-unit rate and charged on the closing invoice.
For example, a plan at $49/month includes 100,000 API calls with an overage rate of $0.001 per call. A customer who makes 130,000 calls in a month pays $49 plus $30 for the 30,000 extra calls, totaling $79 for that period.
Difference from credits and balance models
Metered billing is one of three usage-based billing models, and understanding the differences matters when choosing the right one for your product.
With metered billing, the customer is never blocked from using the product. If they exceed their included quota, they keep using the service and pay the overage later. This makes metered billing feel seamless to the end user but can create surprise charges if usage spikes unexpectedly.
Credits work differently. The customer receives a fixed number of credits, and each action consumes credits. When credits run out, the customer must purchase more or wait for the next cycle. Credits create a hard limit that prevents surprise bills but introduces friction when the customer hits the wall.
Balance billing converts the plan price into a monetary balance. Each action deducts a real dollar amount. Like metered billing, overage is charged at period end, but the customer thinks in dollars rather than abstract units. Balance is common in infrastructure products where customers need precise cost visibility.
Real-world examples
Metered billing dominates industries where usage is variable but the service should never be interrupted. Email delivery platforms give you 50,000 sends per month and charge $0.001 per additional send. Cloud storage providers include 100 GB and charge per additional gigabyte. Communication APIs include a base number of messages or minutes and charge per extra unit.
The pattern is consistent: the base plan covers the common case, and overage pricing handles growth. This structure lets customers start with a predictable bill and scale without renegotiating their contract.
When to use metered billing
Metered billing is the right choice when your product has measurable units of consumption that correlate with value delivered. API calls, data processed, messages sent, storage used, and compute minutes are all natural candidates.
It works best when you want a low barrier to entry combined with revenue that scales with the customer's growth. The included quota de-risks the purchase for the customer, and the overage model ensures you capture value as they grow.
Metered billing is less suitable when usage is difficult to predict or when surprise charges would damage the customer relationship. Products where users cannot control their consumption, like a monitoring tool that processes all incoming data automatically, may create friction with metered pricing because the customer has limited ability to manage their spend.
Implementation considerations
Accurate usage tracking is the foundation of metered billing. Every event must be captured, deduplicated, and attributed to the correct customer and billing period. Late-arriving events, duplicate submissions, and timezone boundaries at period close are common edge cases that need careful handling.
Transparent reporting is equally important. Customers need to see their current usage relative to their included quota at any point during the billing period. If a customer cannot see that they are approaching their limit, overage charges feel punitive rather than fair.
How Commet handles metered billing
Commet supports metered billing as one of its three consumption models. Plans define included quantities and overage rates per feature. Usage events are ingested through the SDK in real time, and Commet handles deduplication, period attribution, and overage calculation automatically. At the end of each billing cycle, Commet generates an invoice that itemizes the base charge and any overage lines, giving customers full transparency into what they consumed and what they owe. For a step-by-step implementation example, see the guide on usage-based billing for AI products.