5 ms·

I wish we could authenticate API access we pay ChatGPT (or anther AIs) for with peoples projects so they can avoid just immediately running out of API tokens (w

I wish we could authenticate API access we pay ChatGPT (or anther AIs) for with peoples projects so they can avoid just immediately running out of API tokens (we’d be using our tokens not theirs). I don’t think you can expect every product that uses AI APIs to make rolling the API costs onto the consumer practical but some individuals might find it useful to throw a few of their API tokens at services for their particular use cases.

jeffy90 4y ago
That's an interesting idea. It'd be cool if ChatGPT gave a portion of the income to whatever 3rd party app we authenticated with as well So the workflow would be this: * pay 20$ a month for access to ChatGPT and receive API token * use my API token w/ 3rd party app * ChatGPT awards 3rd party app some portion of the 20$
- throwaway4837 4y ago
  How does ChatGPT know to award the app? Could be a shitty idea, but I was thinking of a different way: 1. Pay $20/month for ChatGPT access, get personal API token 2. Sign up to 3rd party app a) Enter your API token into app b) Pay $3/month as a subscription You are then paying ChatGPT for using its engine, and paying the 3rd party apps only for their value-add, which they determine in their pricing. In theory, you should be able to view all activity associated with your API token (across all apps) in OpenAI's dashboard. So, we're one step closer to "one profile, many apps", and OpenAI can be the profile distributor. I like the idea of the user having their own AI profile, like an email, that other services can utilize. Just like it's up to the user to manage their email quota with Google, they would manage their AI quota with OpenAI.
  - andy_ppp 4y ago
    You can do all this with OpenId I think…
redeux 4y ago
I think you could do this if your app handles everything on the frontend, right? Just use local storage to hold the user’s API key. The Star History[1] does this for its GitHub star graphs. [1] https://star-history.com/ https://star-history.com/

jeffy90 4y ago

That's an interesting idea. It'd be cool if ChatGPT gave a portion of the income to whatever 3rd party app we authenticated with as well So the workflow would be this: * pay 20$ a month for access to ChatGPT and receive API token * use my API token w/ 3rd party app * ChatGPT awards 3rd party app some portion of the 20$

throwaway4837 4y ago
How does ChatGPT know to award the app? Could be a shitty idea, but I was thinking of a different way: 1. Pay $20/month for ChatGPT access, get personal API token 2. Sign up to 3rd party app a) Enter your API token into app b) Pay $3/month as a subscription You are then paying ChatGPT for using its engine, and paying the 3rd party apps only for their value-add, which they determine in their pricing. In theory, you should be able to view all activity associated with your API token (across all apps) in OpenAI's dashboard. So, we're one step closer to "one profile, many apps", and OpenAI can be the profile distributor. I like the idea of the user having their own AI profile, like an email, that other services can utilize. Just like it's up to the user to manage their email quota with Google, they would manage their AI quota with OpenAI.
- andy_ppp 4y ago
  You can do all this with OpenId I think…

redeux 4y ago

I think you could do this if your app handles everything on the frontend, right? Just use local storage to hold the user’s API key. The Star History[1] does this for its GitHub star graphs. [1] https://star-history.com/ https://star-history.com/