Usage-based billing, metered API, pay-per-call, per-seat vs. per-call model, overage charges, API invoice, prepaid credits, and API pricing calculator vocabulary.
Key vocabulary
Usage-based billing (UBB) — customers pay in proportion to how much they use the API, rather than a flat subscription fee.
Metered API — an API where each call (or unit of consumption) is measured and billed; the meter runs as usage occurs.
Pay-per-call — the simplest UBB model: each API call has a fixed price (e.g., $0.002 per call).
Overage charge — an additional fee charged when usage exceeds the included allocation in a subscription plan.
Prepaid credits — a balance purchased in advance and consumed as API calls are made; when credits run out, the API stops responding or charges begin.
0 / 5 completed
1 / 5
Stripe charges $0.029 + $0.30 per successful card charge through its API. This is an example of:
Usage-based billing charges customers proportionally to what they consume. Stripe’s per-transaction fee is a classic example: if you process no payments, you pay nothing; if you process millions, you pay millions × the unit price. This aligns the API provider’s revenue with the value delivered to the customer, and lowers the barrier to adoption (no upfront cost).
2 / 5
An API plan includes 10,000 calls/month. A customer makes 12,000 calls. The additional 2,000 calls are billed as:
Overage charges apply when a customer exceeds their plan’s included units. They are typically priced higher per-unit than the base plan rate (e.g., plan costs $50/month for 10,000 calls = $0.005/call, but overages are $0.008/call). This incentivises customers to upgrade to the next tier rather than relying on costly overages — a deliberate monetization lever.
3 / 5
When should an API provider consider a per-seat model instead of a per-call model?
The per-seat model charges by the number of users (developers, team members) with access to the API, regardless of call volume. It is predictable for customers and simple to understand. The per-call model is better when value scales with usage volume. Many APIs offer both: per-seat for base access, plus volume tiers for call quotas. Choosing the right model is a critical API product management decision.
4 / 5
A company purchases prepaid credits for an AI API. How does this differ from a subscription?
Prepaid credits (used by OpenAI, Anthropic, and many other AI APIs) give customers control over spend: you buy a block of credits and consume them at your pace. This suits variable, project-based workloads. Subscriptions provide predictable monthly costs. Many API providers offer both: subscriptions with included credits, plus top-up prepaid credit packs for overages — giving customers flexibility while smoothing the provider’s revenue.
5 / 5
A startup builds an API pricing calculator into their documentation. What is the purpose of this tool?
An API pricing calculator is a developer experience and sales conversion tool. Pricing uncertainty ("how much will this actually cost us?") is a major friction point in API adoption. An interactive calculator where developers enter expected call volumes and see estimated monthly costs directly addresses this. Companies like Twilio, AWS, and Cloudflare invest heavily in pricing transparency because it accelerates the decision to commit to a paid plan.