Hi Team, I am back with same topic I posted last week about calling a tool to my application directly with passing via Make.com, because, I want to element extra cost, extra effort to create Make scenarios and maintain just because the direct call to my endpoint is not creating new leads. Some advised to make my application expect VAPI format, which I did and tested successfully with sample JSON object for from the call logs using postman. I just copied the whole object from the call log after the tool call errors out, call the my endpoint with the same data and it works. I took a step further remove unnecessary properties from the payload to a simpler version and tested successfully again in postman but still when the tool is called by the assistant I get 400 error. Has any body on here called tools directly to backend application like I'm trying to achieve and can you share your thoughts, please. Additionally, I am building my first assistant for client and need advice on pricing. At first I offered $500/month with extra initial cost of development but she said she couldn't afford it. Then I went to $150/month and she subscribed. Is that too cheap with initial development cost? How are managing multiple client from the VAPI dashboard? Do you categorize your clients by organizations in VAPI or just creating agents for each client? Same question for Make account if you are integrating with Make. What happens if your client at some point wants to manage his/her own agent or wants transfer if you are sharing one account for all clients?