As I said in the comment, I’m not sure about the “bring-your-own-key” model, and you might want to reach out to official support.
ETA: Mentions bring-your-own-key…
@bakztfuture seems to be saying they do NOT support bring-your-own-key, but this was 2021, so things might have changed. I don’t see anything official in the docs, and I know some people are doing it, but it might not be the best model long term?
Most “bring-your-own-key” models are opensource software that people would install themselves. I don’t think OpenAI wants you storing keys (even encrypted) for other users… so that’s something to think about too…
Okay… seems it is NOT allowed… I’m not sure if they’re enforcing it, though…
Thanks, Paul for your continued help in this matter. Yes, it appears bring-your-API-key is not a good idea, and I researched that for pay-as-you-go customers, the API limit is 3000 requests per min after the first 48 hours. Also, if we send a session nonce unique to each user and repeat the last prompt, we should be able to maintain context per user as well. Thanks again!
Are you talking about user id? This cannot chain API calls together. Each prompt->completion call is separate unto itself. The user id is to tag which users are sending what prompts for risk/safety issues.