Replies: 3 comments 1 reply
-
|
Hey @thorsmann, While we have plans to add what should be properly called an OpenAICompatibleService, we need to specify it and understand how it would work. With Parlant, since it's not only a matter of "connecting" to a service but, much more than that, how to reliably use it at scale with high SLAs, this means that simply changing the base URL or choosing a model won't be enough for more than mere prototyping. And production reliability is what we're all about. With that said, Parlant places very few hard limitations on you as a developer — as a strict design goal. In fact, there's a documentation page I want to refer you to — on custom LLMs — which takes you step by step into implementing your own If you run into any issues or have any questions, please don't hesitate at all to bring them up either here or on Discord! |
Beta Was this translation helpful? Give feedback.
-
|
custom_service.py In addition,I want to express some thoughts!I am a tech newbie.This project is very powerful, and it also makes me feel that it is very complex.o(╥﹏╥)o |
Beta Was this translation helpful? Give feedback.
-
Yes, and it will make you more powerful too :D But yeah the team is made up of some pretty experienced software developers and we've definitely put our whole experience into Parlant's design. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, I am playing around with the healthcare demo (https://www.parlant.io/docs/quickstart/examples/).
How can I override the base URL of the OpenAI endpoint wrapper? We use a variety of models which are all wrapped behind the OpenAI chat protocol. I would need some way to override the base URL of the OpenAI server object.
I try to set OPENAI_PROVIDER_BASE_URL accordingly and used a valid and working api key for our own endpoint but I get this error message: {'error': {'message': 'Incorrect API key provided:
It seems like there is some hard-wired authentication against the actual OpenAI service (which obviously does not know our API key). Did I miss something obvious?
Beta Was this translation helpful? Give feedback.
All reactions