As far as I've seen, for APIs that don't "consume" any resources, the usual schema is to charge a fixed fee.
Either that or it's just included part of a higher pricing tier. Of course, there can be a quota restricting how many API calls are allowed per period.
Charging per call feels weird when the cost of a call is essentially zero. You only really see that in things that are computationally expensive like LLMs, image optimization, etc.
Agreed. If this is a service I'm already paying for and if it's basically just doing 'CRUD' actions that are (hopefully) low in resource usage I'd be really uncomfortable with a pay-per-use model. Rate limiting sure, but I don't want another thing I need to price in my head as I'm writing code.
Comments
As far as I've seen, for APIs that don't "consume" any resources, the usual schema is to charge a fixed fee.
Either that or it's just included part of a higher pricing tier. Of course, there can be a quota restricting how many API calls are allowed per period.
Charging per call feels weird when the cost of a call is essentially zero. You only really see that in things that are computationally expensive like LLMs, image optimization, etc.
Agreed. If this is a service I'm already paying for and if it's basically just doing 'CRUD' actions that are (hopefully) low in resource usage I'd be really uncomfortable with a pay-per-use model. Rate limiting sure, but I don't want another thing I need to price in my head as I'm writing code.