https://vapi.ai/ logo
Join Discord
Powered by
Pipeline failed with Google or Anthropic models
# support
a
When running my assistant with Anthropic or Google models I get an error, 
An error occurred in this call: pipeline-error-anthropic-400-bad-request-validation-failed
it works perfectly fine with OpenAI models though. What is the reason for that behavior? Do I have to use one of OpenAI's models or is there another way to solve that?
s
@Armando Could you share the call ID so I can take a look?
a
@Shubham Bajaj for example d54d6f8e-0a62-4321-a635-7fe561844e69, df9432a7-fa3f-4756-b2de-4d99ecca84e2, af759e01-a91d-4624-9e38-1df91b996890, or 1f3f6db1-2eb7-4c7a-9cc7-7d5792ee868b
s
- 1f3f6db1-2eb7-4c7a-9cc7-7d5792ee868b
Copy code
"error": {
    "message": "deepseek-reasoner does not support Function Calling",
    "type": "invalid_request_error",
    "param": null,
    "code": "invalid_request_error"
  },
  "code": "invalid_request_error",
  "param": null,
  "type": "invalid_request_error",
  "message": "400 deepseek-reasoner does not support Function Calling","
- af759e01-a91d-4624-9e38-1df91b996890
Copy code
"message": "422 Failed to deserialize the JSON body into the target type: tools[9].function: missing field `parameters` at line 799 column 7",
- df9432a7-fa3f-4756-b2de-4d99ecca84e2
Copy code
"error": {
    "type": "error",
    "error": {
      "type": "invalid_request_error",
      "message": "tools.0.input_schema.properties: Property keys should match pattern '^[a-zA-Z0-9_-]{1,64}$'"
    }
  },
  "message": "400 {\"type\":\"error\",\"error\":{\"type\":\"invalid_request_error\",\"message\":\"tools.0.input_schema.properties: Property keys should match pattern '^[a-zA-Z0-9_-]{1,64}$'\"}}",
- d54d6f8e-0a62-4321-a635-7fe561844e69
Copy code
"message": "[GoogleGenerativeAI Error]: Error fetching from https://generativelanguage.googleapis.com/v1beta/models/gemini-2.0-flash-exp:streamGenerateContent?alt=sse: [400 Bad Request] * GenerateContentRequest.tools[0].function_declarations[0].parameters.properties[insuredEmail].format: only 'enum' is supported for STRING type\n* GenerateContentRequest.tools[0].function_declarations[1].parameters.properties[insuredEmail].format: only 'enum' is supported for STRING type\n",
@Armando either your using wrong json schema for few of the properties or using invalid properties name because of this your getting these error messages.
Do let me know, if you require further help!!
a
@Shubham Bajaj is it possible to use tool calling with other any of these models (obviously not with deepseek as we see)
s
@Armando Yes you can use other fix the tools schema according to their requirements, and then you will be good to use them for more you can refer the share error response. Do let me know if further help is required.
@Armando This is a gentle reminder to continue this discussion.
@Armando because of no response closing this thread.
a
@Shubham Bajaj how are tools in the format that Anthropic expects compatible with Vapi's format for tools? I don't get it from what I see Vapi expects tools to be defined in OpenAI's format
s
We have developed our own schema and format for the tools, as Anthropic has different chat completion models that operate according to their specifications, and similarly for OpenAI. We have established a uniform schema for external visibility and compatibility with different models, along with the underlying code that accepts inputs in one format but processes them according to the required model schema/API. The tools function in the same manner; when OpenAI is utilized, they are converted to meet the specified requirements, and the same applies to Anthropic. It is important to note that Anthropic requires keys to be alphanumeric only, which prevents us from enforcing these schema constraints on a uniform single interface, thereby not limiting other models. This may explain the differences you have observed. Please feel free to reach out if you have any further questions or concerns.
4 Views
PreviousNext
Powered by