Hi Team,
I am from Gnani.AI, we want to integrate our STT as part of the LiveKit Agents. We have made the necessary changes as per the code review done by CodeRabbit.
Please help us take this forward.
Hi Team,
I am from Gnani.AI, we want to integrate our STT as part of the LiveKit Agents. We have made the necessary changes as per the code review done by CodeRabbit.
Please help us take this forward.
Hi, I see no comments from our side since the PR was raised.
How do your users currently integrate your STT with LiveKit? I mean, some providers will maintain a separate LiveKit plugin hosted outside of our repo, along with a separate integration guide, so users can use your STT before it is integrated into the LiveKit project.
If I Google “GnaniAI LiveKit” I see no results, so want to make sure I’m not missing anything.
So far, we’ve been using our STT model primarily within our own voice bot deployments (200+ so far, primarily India-focused). We’re now in the process of making it available externally.
We’re seeing strong interest from large enterprises in India, many of whom already use LiveKit for their voice AI infrastructure. That’s why we’re keen to have a native integration within LiveKit - it would significantly simplify testing and adoption for these customers, rather than requiring them to manage a separate plugin or integration layer.
Hope that answers your question.
hi @darryncampbell , do you want us to create an external pypi package which integrates with livekit externally, before we can integrate it as part of LiveKit ?
It’s not my decision eventually which plugins are integrated, as I’m sure you can appreciate we get a lot of pull requests for different providers.
I wanted to make the suggestion to host it externally to unblock you and any developer wishing to use it.
Then, assuming you saw very strong adoption, it would be easy for the engineering team to assess that the PR should be merged. Adding new models is obviously a trade-off between adding great new functionality to the product and the additional maintenance / documentation overhead.
I see you tagged a couple of folks on the PR, they are the decision makers at the end of the day, so I’ll defer to any conversation on that PR.
Sure, thank you very much. I truly appreciate the prompt responses.