AI and infrastructure
API Endpoint Pricing: Different Actions Can Have Different Economics
By the Orvlin team · · 1 min read
Api endpoint pricing design: what to decide
A health check and a complex search each count as one request. If the same rate applies, heavy search users can consume much more cost for the same billable quantity. The simplicity trade-off should be deliberate.
Avoid turning every internal route into a separate commercial SKU. Use understandable action groups and stable definitions. Track method, endpoint category and outcome when needed for attribution, while minimizing sensitive request content.
A concrete scenario
A hypothetical basic lookup costs $0.001 to serve and a complex analysis costs $0.05. A common $0.01 selling rate has very different margin effects across those actions, even before overhead.
A detail teams often miss
Endpoint names change during refactoring. Price contracts should reference stable commercial actions rather than code paths that engineers may rename without realizing the billing impact.
Before you put this into production
- Measure costs by meaningful action group.
- Choose stable customer-facing categories.
- Define retries and unsuccessful actions.
- Simulate mixed workloads before setting rates.
Frequently asked questions
- Should every endpoint have its own rate?
- Usually not. Use enough differentiation to support the economics without making the offer unnecessarily difficult to understand.