How does the RAG API's API key follow the user-provided in .env under custom endpoint conditions? #2874
Unanswered
sunsky89757
asked this question in
Q&A
How does the RAG API's API key follow the user-provided in .env under custom endpoint conditions?
#2874
Replies: 2 comments 1 reply
-
|
STT_API_KEY and TTS_API_KEY are the same issue as RAG, I only take effect when I input a specific key like sk-xxx, and inputting user_provided is invalid |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
|
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Does this continue to be the case? |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
What is your question?
How does the RAG API's API key follow the user-provided in .env under custom endpoint conditions?
More Details
I tried to use RAG_OPENAI_API_KEY=user_provided in .env, but it didn't work.
Can this be designed to follow the RAG API with the user-provided API key?
What is the main subject of your question?
Endpoints
Screenshots
No response
Code of Conduct
Beta Was this translation helpful? Give feedback.
All reactions