API Pricing Calculator for Paid APIs
Set a paid API price from delivery cost, selling price, payment fees, refunds, bad debt, and volume. Calculate margin, net profit, and break-even usage.
Editable usage, rate, and operating assumptions
Scenario totals and unit economics
Price paid API access
API Pricing Calculator for Paid APIs
Calculate paid API pricing, margin, fees, refunds, bad debt, and net profit.
| Item | Basis | Value |
|---|---|---|
| Monthly revenue | 5,000 users or units | $5,000 |
| Monthly gross profit | Revenue minus provider cost | $2,750 |
| Fees, refunds, bad debt | 6% of revenue | $300 |
| Fixed server cost | Monthly infrastructure | $120 |
| Actual markup multiple | Selling price divided by delivery cost | 2.22x |
| Price required for selected margin | 30% target net margin | $0.74 |
| Break-even volume | Users or units needed to cover server cost | 245 |
Frequently asked questions
Practical answers for applying this calculator to a production API billing or usage plan.
Which delivery cost should I enter?
Use the direct cost for the same unit you plan to sell: one request, token bundle, credit, customer, or other billable unit. Include the upstream provider and unit-level infrastructure cost there, while keeping monthly server cost, payment fees, refunds, and bad debt in their separate fields.
What is a good margin for a paid API?
A good margin for a paid API depends on volatility, support load, infrastructure risk, and competition. Simple data APIs with stable costs may survive on lower gross margins, while AI, scraping, enrichment, or gateway products often need more room because upstream prices, retries, abuse, and refunds can change quickly. Many teams model at least 40% to 70% gross margin for scalable paid APIs, then test sensitivity. The key is contribution profit: revenue minus direct usage cost, payment fees, refunds, and bad debt. If heavy users create negative contribution, the headline margin is not real.
How are free-tier costs handled in this calculator?
Convert expected free-tier consumption into an additional delivery-cost amount before setting the cost per paid unit, or add it to monthly server and operating cost. Then compare the result at realistic paid-customer volumes so unpaid usage is not silently excluded from the profit result.
Can I model requests, tokens, credits, or customers?
Yes. Treat the chosen request, token bundle, credit, customer, or operation as one consistent unit. Enter its delivery cost, proposed selling price, and expected monthly unit volume. Do not mix units in one calculation; compare separate scenarios when endpoints or models have materially different costs.
How do you calculate API profit?
API profit is calculated by subtracting all delivery and operating costs from revenue. A compact formula is: net profit = API revenue - provider cost - hosting - payment fees - refunds - bad debt - support and operations. Gross profit usually subtracts only direct delivery costs, while net profit includes more business overhead. For example, if monthly API revenue is $5,000, provider usage is $1,600, hosting is $300, fees and refunds are $350, and support allocation is $600, estimated net profit is $2,150. Calculate profit by customer segment too, because heavy users can be less profitable than average users.
Related API billing guides
Read the concepts behind the calculator and adapt the examples to your own API pricing model.
How to Price an API: Cost, Margin and Billing Models
Follow a step-by-step method to choose a billable unit, calculate delivery cost, set margin, design free tiers, and publish sustainable paid API plans.
Read guidePaid API Pricing Examples: Requests, Tokens, Credits and Tiers
Compare paid API pricing examples for per-request, token, credit, subscription, and tiered-overage models, with sample monthly bills and customer-facing invoice math.
Read guideAPI Billing Models: Usage-Based, Subscription, Credits and BYOK
Compare API billing models for developer products, including usage-based billing, subscriptions, credits, prepaid wallets, and bring-your-own-key.
Read guide