Feature Requests

Solution for building in video conferencing environment like google meet

When issuing an auth token for a user to chat with EVI2, it would be nice to specify a limit of how many seconds that auth token can chat. It would also be good to have a way of tagging these auth tokens and getting reliable reports of how many seconds of billing were associated with each auth token tag. The end goal is to be able to track and limit Hume billing in a reliable way that can be tracked and enforced for each of my users, even when those users are accessing the same chat configuration. The only thing different for each user is the Hume auth token and the language_model_api_key. In this situation the browser itself is not trusted and so reporting chat id or chat group id from the browser does not solve the problem.

I am currently building a react app with @humeai/voice-react The problem is that everything is on the "client side" This makes it difficult to build secure apps. For example, I want that when the user clicks on the call button, a modal appears if they don't have enough credits. Since everything is on the "client side", I am not sure it is possible to build this feature securely. Another example, I want to decrease the credits by 1 for every minute in the call. Same problem, everything that gives me information about the length of the call can be manipulated on the client side. Is there a work around?

Send real-time notifications or trigger actions in other systems based on EVI events. For example, you could update a database or send an alert when a specific event occurs during the conversation.

Heygen, Tavus, etc

When using the Hume API, you can view an audio-visual timeline to track the latency between the request and response in real-time. Additionally, a detailed timeline is available in the logs or a list format, providing precise timestamps for each step in the process. For example: Message Received: The exact time when Hume receives the message from the client. CLM Handoff: The time when Hume forwards the message to the CLM First Response: The time when Hume receives the first response from the CLM and begins streaming it back to the client. Assistance Completion: The time when the interaction concludes, marked by the assistance end message.

Introduce organizations/teams support to enable collaborative management of projects, resources, and permissions within the Hume platform.

Dedicated API endpoint to generate EVI-like voice from text

The EVI API currently has a maximum conversation duration of 1800 seconds (30 minutes). This feature request proposes the ability to extend this time limit. Two potential implementation options are: Increase the global time limit for all users Allow customizable time limits on a per-user basis