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

  1. Estimate blended infra cost per 1,000 calls.
  2. Add vendor pass-through cost per 1,000 calls.
  3. Add fixed overhead you need to recover.
  4. Pick a target gross margin range.
  5. Choose tiers and included usage based on typical and heavy customers.
  6. 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.

Tools to use