I don’t intend to be demeaning or place myself above you. Nor am I looking for you to be proud.
It seems like you have set yourself on one path and won’t move unless shoved. I hope everything works out for you.
N2U
37
It’s okay mate, these things are not mutually exclusive
Small question: do you plan on commercializing the app itself or the stories you make with it?
You’re going to end up with zero users when OpenAI terminates all of the accounts with APIs used through your service, see: janitor.ai.
What have I done that makes you think I need to be shoved? Or that I’m on a path I shouldn’t be on? I’ve refactored my app to use my own API key. No one needs to shove me. WtF?
I think there’s genuine people with genuine advice. I am not speaking to you to make myself feel important. I want to see your project grow and succeed - as does others here. Saying sue me is just a weird reaction.
You’re going to end up with zero users when OpenAI terminates all of the accounts with APIs used through your service, see: janitor.ai.
Why? What am I doing that would lead to that action? Again, DAYS ago, I refactored to use my own API key. No more BYOK.
I think there’s genuine people with genuine advice.
So this is genuine advice?
¯\_(ツ)_/¯
You just want OpenAI to handle your billing for you.
It can seem aggressive at face-value but it’s with genuine intention. It’s s really good idea and I think any member here has seen way too many people suffer the zero-tolerance policy OpenAI has with BYOK services.
N2U
44
Let’s all calm down here,
@seaofarrows, you’ve rewritten your app several times over the past few days, I can understand why they’re confused, @elmstedt is not trying to make fun of you, there has, unfortunately, been a few instances where a BYOK application has led to a lot of people getting banned.
Now let’s keep the decorum on the forum
2 Likes
N2U
45
For everyone who may be looking for answers:
There are several ways to access OpenAI’s models. One method is through the API, tailored for developers to integrate into their own software. Note that sharing of API keys is not allowed, and that includes inputting your key on sites like website.com.
If you’re a developer and want users to shoulder their own usage fees, then I’d suggest creating a ChatGPT plugin.
3 Likes
spa
47
Alright guys, why don’t we all just build an open-source billing system for single API key applications! Who’s with me!?
2 Likes
N2U
48
Nah mate but somehow you interpreted the following as being directed on at you
It was not:
I’ll suggest that you calm down a bit and realized that I’m not against you, or anyone else here.
You have voiced your displeasure, could you stop the name-calling now?
1 Like
Why do you insist on attacking people who give you genuine advice? You learned something and adapted. That’s pretty sweet. Roll with the punches and be humble next time.
Gosh, I feel like it’s like going to a boxing gym and working out, going into the ring with your colleagues, getting bopped and then crying out the door.
1 Like
Again, Ruckus, you didn’t give advice, you gave aspersions.
If you feel that way. Sure, maybe you’re right.
What about everybody else?
As someone who has been on both sides, seeking assistance and feeling a bit overwhelmed and trying to assist someone with something I’m very familiar with, this sort of thing just happens sometimes. You’ve got to step back and take a deep breath and look at it as logically as you can. Looking at this conversation as a 3rd party, and having interfaced with, and received helpful advice from, many of the names here, I’m pretty sure none of this is personal.
I disagree with this decision from OpenAI, and @seaofarrows has articulated my reasons even better than I have. The last thing I want to do is have to build a token billing system on top of a regular subscriber system. But, if I’m being honest, I can also see OpenAI’s position also.
I like this idea, but don’t we end up with the same exact problem – people STILL aren’t allowed to use their keys in someone else’s system?
1 Like
This is, genuinely, a great idea.
At the risk of going off-topic , I have a very broad-strokes idea as to how this might work
- Set usage limits for each user.
- Set a standard billing cycle for users (say weekly, daily, monthly, etc) and have a minimum billing amount per cycle where the user has usage (say $0.50).
- Bill based on tokens used at 120%–200% of token cost to cover costs and income for the developer.
Or, alternately, just have them pre-pay whatever amount they want and deduct as they go. That’s obviously the safest and easiest for the developer to implement and just involves tracking tokens used and some simple multiplication and subtraction.
Honestly, the biggest impediment to moving away from the BYOK service is likely going to be hitting the usage cap for OpenAI’s API.
Regardless, I think an open-source billing system would be great.
4 Likes
I love this idea (hence the heart tick), and works perfectly for gpt-3.5-turbo. But when you get to gpt-4, 120%-200% of token cost seems to get fairly expensive fairly quickly. And, for me, that’s why I liked the BYOK idea – the customer can only grumble at OpenAI, who set the price in the first place.
1 Like
Then just open-source it and let the user run it locally.
If your point is to, at some point, make money off of it, you will inevitably need to charge a premium over your own usage costs.
If your point is to, at some point, make money off of it, you will inevitably need to charge a premium over your own usage costs.
That is only the case if your business model is the obvious “mark up tokens by X%” approach.
Another way to think of it is: “OpenAI fees are a cost of doing business. Elsewhere in my business, I make income from the things I do with OpenAI.”
