Properties
| Name | Type | Description |
|---|---|---|
| type | string | This is the type of the judge plan. Use 'regex' for a regex match on the content and tool calls - without using LLM-as-a-judge. @default 'regex' |
| content | string | This is what that will be used to evaluate the model's message content. The content will be evaluated against the regex pattern provided in the Judge Plan content field. Evaluation is considered succe |
| toolCalls | array | This is the tool calls that will be used to evaluate the model's message content. The tool name must be a valid tool that the assistant is allowed to call. The values to the arguments for the tool cal |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "#/components/schemas/AssistantMessageJudgePlanRegex",
"title": "AssistantMessageJudgePlanRegex",
"type": "object",
"properties": {
"type": {
"type": "string",
"enum": [
"regex"
],
"description": "This is the type of the judge plan.\nUse 'regex' for a regex match on the content and tool calls - without using LLM-as-a-judge.\n@default 'regex'"
},
"content": {
"type": "string",
"description": "This is what that will be used to evaluate the model's message content.\nThe content will be evaluated against the regex pattern provided in the Judge Plan content field.\nEvaluation is considered successful if the regex pattern matches any part of the assistant message content.",
"example": "/sunny/i",
"maxLength": 1000
},
"toolCalls": {
"description": "This is the tool calls that will be used to evaluate the model's message content.\nThe tool name must be a valid tool that the assistant is allowed to call.\nThe values to the arguments for the tool call should be a Regular Expression.\nEvaluation is considered successful if the regex pattern matches any part of each tool call argument.\n\nFor the Query tool, the arguments for the tool call are in the format - {knowledgeBaseNames: ['kb_name', 'kb_name_2']}\n\nFor the DTMF tool, the arguments for the tool call are in the format - {dtmf: \"1234*\"}\n\nFor the Handoff tool, the arguments for the tool call are in the format - {destination: \"assistant_id\"}\n\nFor the Transfer Call tool, the arguments for the tool call are in the format - {destination: \"phone_number_or_assistant_id\"}\n\nFor all other tools, they are called without arguments or with user-defined arguments",
"example": "[{ name: \"get_weather\", arguments: { city: \"/San Francisco/i\" } }]",
"type": "array",
"items": {
"$ref": "#/components/schemas/ChatEvalAssistantMessageMockToolCall"
}
}
},
"required": [
"type",
"content"
]
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/vapi-assistantmessagejudgeplanregex"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.