API Pricing Model (How to Price per 1k Calls)
A step-by-step model for costs, margins, and tier design for API products.
Quick checklist
- Define the billing unit (per call or per 1,000 calls).
- Separate infra cost from vendor pass-through cost.
- Model at least two scenarios (p50 vs p90 calls).
- Use a platform fee if fixed overhead is meaningful.
- Publish example bills to reduce bill shock.
Step-by-step
- Estimate blended infra cost per 1,000 calls.
- Add vendor pass-through cost per 1,000 calls.
- Add fixed overhead you need to recover.
- Pick a target gross margin range.
- Choose tiers and included usage based on typical and heavy customers.
- Validate outputs with CSV exports and shareable links.
Example scenarios
- Starter API: low volume with a base fee to cover overhead.
- Growth API: tiered overages with declining per-unit rates.
- Enterprise API: committed spend with volume discounts.
Common mistakes
- Pricing per call without a minimum fee.
- Ignoring vendor costs until after launch.
- Using a single churn assumption across all segments.