Better OpenAI and Assistants API integration

Hello 👋

OpenAI and Assistants API integration is one of our most used features. We recently received feedback from many users to improve these features, especially after our new interface update. Based on this feedback, we implemented some changes, and now OpenAI and Mevo syncing is more powerful and accessible than ever.

The best part about binding your OpenAI key to Mevo is the freedom to use the latest language models without being stuck with token limits. However, this integration process could have been confusing in many cases. Let's quickly summarize what we did to improve things.

The organization-level OpenAI key binding feature is no longer available

The only way to bind your OpenAI API keys is to bind a private key to the chatbot. Suppose your organization already has an OpenAI API key bound. In that case, our system will automatically add it to all your existing AI chatbots that do not have a dedicated OpenAI API key.

If your current Mevo plan cannot bind a chatbot-specific OpenAI key, don't worry; the chatbot-level key binding feature is now included in every package with an organization-level key binding feature. So, there is no loss of rights for anyone.

Better Assistants API synchronization

Another change relates to Assistants API; previously, if you connected the assistant you created in OpenAI to Mevo, your training data in Mevo did not affect your assistant; chats bypassed Mevo and interacted directly with your assistant. Any training data you added after connecting your assistant will be synced with your OpenAI assistant.

If you need help with these changes, you can reach us at hi@usemevo.com.

Thanks for reading.