We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Today, there is no explicit way to pass the openapi client.
It would be very cool to be able to define gateway data - to be able to use tools like Helicone, that give explicit details about API usage. Here is how Helicone integrates: https://docs.helicone.ai/quickstart/integrate-in-one-minute
Unfortunately, there is no consistent way to overide headers everywhere: openai/openai-python#209
The text was updated successfully, but these errors were encountered:
For now you can do this:
import helicone import guidance # patch guidance from guidance.llms import _openai _openai.openai = helicone.openai
Sorry, something went wrong.
@bhy Thanks, that should solve the API key, but what about custom properties, which still require custom headers?
No branches or pull requests
Today, there is no explicit way to pass the openapi client.
It would be very cool to be able to define gateway data - to be able to use tools like Helicone, that give explicit details about API usage.
Here is how Helicone integrates: https://docs.helicone.ai/quickstart/integrate-in-one-minute
Unfortunately, there is no consistent way to overide headers everywhere: openai/openai-python#209
The text was updated successfully, but these errors were encountered: