Open source project how to regulate API costs?

Hi,

For an open source project that uses an API (in this case the OpenAI API), what is the best way to handle authentication?

Don't get me wrong, this isn't about how login and so on should work, but rather how I should handle access to the API.

One possibility would be to set up a subscription model with Stripe, for example.

Another option would be for everyone to have to store their own API key. However, in my opinion, this wouldn't be a particularly secure solution, since the user would have to trust me not to misuse the key.

However, subscription payments don't really fit with open source, or am I mistaken?

would like to know your opinion

(1 votes)
Loading...

Similar Posts

Subscribe
Notify of
1 Answer
Oldest
Newest Most Voted
Inline Feedbacks
View all comments
FaTech
1 year ago

It is an open source project. Everyone sees what happens to his keys. If you’re doing your own subscription model, you’ll have to put your key behind, make sure that it won’t be released, and you’re taking responsibility. Besides, this would then be over your server and just then comes the suspicion that you misuse data because it is no longer completely open source