-
Notifications
You must be signed in to change notification settings - Fork 500
New issue
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
[Provider] Predibase #126
Comments
In predibase, they allow using adapters for each request. The structure of adapter is simple key value pair that is sent in the body: I was thinking that would it make sense to have adapter as a
Just wanted to have some feedback on this. This might also cause friction for someone switching from Predibase APIs to Portkey Gateway APIs. But this looks like a more suitable option as it aligns with the idea of unified interface and can also be extended in future. The other easy way is to simply allow a new field called adapter_id which will be forwarded to Predibase as it is. |
Hello, with LoRAX / Predibase's OpenAI comptible API, it should hopefully be fairly straightforward to integrate: https://predibase.github.io/lorax/guides/openai_api/ The For measuring token consumption, LoRAX / Predibase returns the following information in the response headers:
Predibase's per-token pricing for serverless LLMs can be found here: https://predibase.com/pricing |
I'm exploring Predibase for my adapters, I might swing by this too. |
Add Predibase as an AI provider integration.
They allow easy use of adapters
The text was updated successfully, but these errors were encountered: