Request Pricing Model

Price per request or per 1,000 requests with margin-safe assumptions.

Quick checklist

  • Define what counts as a billable request.
  • Use per-1,000 units for pricing clarity.
  • Model request costs with real infra data.
  • Add a platform fee if fixed costs are high.
  • Use tiers to avoid bill shock.

Step-by-step

  1. Estimate cost per 1,000 requests.
  2. Set a target gross margin.
  3. Convert to a price per 1,000 requests.
  4. Add tiers for higher usage bands.
  5. Validate with ARR and ARPA targets.

What to watch

  • Bursty traffic can distort costs.
  • Request-heavy endpoints need separate pricing.
  • Underpriced requests create margin erosion.

Common mistakes

  • Pricing per request without rounding.
  • Ignoring caching and batching effects.
  • Mixing read and write requests in one unit.

Tools to use