Vapi Assistant Creation

Create a valid Vapi assistant payload first. Call the Vapi API only when the user clearly asks to create the assistant in Vapi and VAPI_API_KEY is available.

Reliability Rules

• Do not invent model names, voice IDs, tool IDs, credential IDs, assistant IDs, phone numbers, or server URLs.
• Use the known-good defaults below when the user does not specify provider choices.
• Verify any user-requested specific or latest model, voice, transcriber, hook, or provider shape in official Vapi docs, Vapi API responses, or the user's Vapi dashboard/API value before using it.
• Treat Vapi API validation errors as the source of truth. Correct the payload and retry rather than guessing.
• Do not enable HIPAA or other paid/compliance behavior unless the user explicitly asks for HIPAA, compliance mode, no recording, or no transcript storage.

Creation Workflow

1. Determine the output mode.
   • If the user asks for a payload, JSON, config, draft, or says not to call the API, return assistant JSON only.
   • If the user asks to create in Vapi, add it to their Vapi account, make it live, or call the API, use POST https://api.vapi.ai/assistant with VAPI_API_KEY.
   • If the user only says to create, build, or make an assistant and does not specify payload-only or live creation, ask: "Do you want the assistant JSON only, or should I create it in your Vapi account if VAPI_API_KEY is available?"
   • Completion: the mode is clear before any live API request is sent.