Since you only provide "API Request" which is not compatible with an existing "tool/function" declaration, it would force all your existing clients to have to completly redevelop their implementations, which is a major pain.

I understand your concern about the compatibility of the "API Request" with existing "tool/function" declarations. Vapi is designed to integrate seamlessly with various platforms and applications, and while transitioning to the new API Request may require some adjustments, we aim to provide support to ease this process. Here are a few key points regarding compatibility and transition: 1. **Modular Design**: Vapi's architecture allows for flexibility, enabling developers to adapt their existing implementations to accommodate the new API features. 2. **Support for Custom Tools**: You can set up custom tools using the payload for “function” type tools, which can help in aligning with your current setup. 3. **Transition Resources**: We provide documentation and support channels to assist developers in transitioning their implementations smoothly. If you have specific concerns or need assistance with your implementation, feel free to reach out! 😊 Sources: - [Vapi Voice AI Platform API Compatibility Features](https://docs.vapi.ai/) - [Transitioning to Vapi Voice AI Platform's API Request](https://docs.vapi.ai/) - [Vapi Support for API Request Compatibility Challenges](https://docs.vapi.ai/support)

Hey @Frédéric Giudicelli thanks for sharing the feedback. I will share this with the team.