Concerns Over API Cost Impact on Clay Pricing Strategy

Re: the above change. While I understand everyone is running a business here I think this is a really bad precedent to set. I can't think of a single example where running an outside API costs platform credits for any other SaaS I've ever used. The issue comes down to not being able to trust that my Clay usage can scale economically in the future, and if I'm building my whole outbound and GTM data system on top of clay it becomes very concerning. I don't OFTEN use credits so in the short term I'll probably be fine but what if the cost is raised to .2, or .5, or anything else? At the end of the day I'm already paying ~10k/yr for clay and god knows how much for the openAI API, it seems a bit trite to now be charging me for the use of an API key I'm already paying for AND to use a standard feature in a platform I'm already paying (a lot) for.