----------------------------- **While I generate an answer, here are some sources that might be helpful**: * [Create Assistant]() * [Function Calling]() * [Setting Server URLs]() * [Get Assistant]() -----------------------------

### Answer It seems you've encountered the distinction between how functions and tools are represented in Vapi when using different methods of creation (dashboard vs API). From the information provided, it's clear that there might be a conceptual difference in how functions are organized and represented depending on the method used to set up or retrieve the assistant's configuration. 1. **Via API**: When creating an assistant via the API method, the functions you're referring to are indeed part of the

tools

array in the assistant's configuration. This is indicated in the structure provided for tool calling, where the

type

can be set to "function" and integrated within the tools array as part of the assistant's configuration [(1)]() . 2. **Via Dashboard**: When setting up an assistant through the Vapi Dashboard, it appears you've observed a direct

functions

array instead of incorporating them within a

tools

array. Unfortunately, there isn't direct documentation in the provided sources that explicitly explains the structural differences between using the dashboard and the API for function setup. The variation you're seeing could be attributed to how Vapi abstracts the complexity when using the dashboard, possibly simplifying the setup process for users by directly presenting a

functions

array. Meanwhile, the API method might offer more flexibility or granularity in configuration, thus presenting functions within a broader

tools

construct. Understanding this distinction is crucial, and it's understandable that it might cause some confusion. The key takeaway is that whether functions are nested within a

tools

array or presented directly as a

functions

array, they serve to extend the capabilities of your Vapi assistant by integrating external functionalities. It's also worth mentioni

ng that the documentation and interface might evolve, so keeping an eye on official Vapi documentation for the latest updates and guides on structuring your assistant's configuration would be beneficial. If you're looking to delve deeper into function and tool calling within Vapi, exploring the provided documentation on tools calling and function setup through the API might offer further insights [(1)]() [(2)]() .