Forecast API Gateway spending as request volume compounds over time, including request charges, fixed platform cost, cumulative requests, and the ending monthly run rate.
The main result is total API Gateway spend over the forecast period. Ending monthly cost helps translate compounding request growth into a future budget run rate.
Pricing is modeled with one effective rate and one fixed monthly cost. Add downstream compute, data transfer, caching, and support only when included in the entered fixed cost or effective rate.
Starting at 100 million requests, $1.20 per million, $250 fixed monthly cost, 10% monthly growth, and 12 months produces $5,566.11 in cumulative cost. Month 12 costs $592.37, with 2,138.43 million cumulative requests.
No. The entered fixed monthly cost stays constant while request charges grow with volume.
Yes. A value above −100% models declining monthly request volume.
Only indirectly if your effective price already reflects the free allowance.
Only if you include them in the fixed monthly cost or effective request rate.
They are not; the forecast period must be a whole number from 1 to 120 months.
| Variable | Meaning | Unit |
|---|---|---|
| Q₁ | Starting monthly requests | millions |
| r | Effective request price | $/million |
| g | Monthly request growth | % |
| m | Forecast month | month |