I figured out the actual issue. If I use a fixed p...
# 💻creators-and-apify
s
I figured out the actual issue. If I use a fixed pricing model instead of "Pay per event + usage", I'm the one paying for whatever machine configuration the user chooses. For example, my actor might only need 256 MB of RAM, but a user can run it with 4 GB or another larger configuration, and I still end up covering that cost. For now, I've changed the default settings, but Apify told me I can't update the pricing model until 6/17. After that, I'll switch to "Pay per event + usage" and set a low event price (maybe around $1 per 1,000 events), while users pay for their own actor resources such as memory and compute. Honestly, it feels strange that I would have to pay Apify for the infrastructure used by my API users. Also, in the actor settings, I can't enforce a specific configuration. The "default inputs" option only acts as a recommendation for saved tasks and API runs, not a hard requirement, so users can still change the configuration.