Vapi Assistant Creation

Design the assistant's behavior before assembling its configuration. Treat persistence and execution as separate decisions: a returned configuration can still describe a saved assistant, and creating a saved assistant does not deploy it, attach a phone number, or prove it is production-ready.

Source and Safety Rules

• Use the configured Vapi documentation MCP when available for current product guidance. Otherwise use the bundled references and their public Vapi links. Validate the final payload against the current Create Assistant API schema.
• Never print, request in chat, or embed API keys, provider secrets, credential values, private URLs, or real customer data.
• Never invent IDs, destinations, integrations, server URLs, model names, voices, transcribers, schemas, or business policy.
• Keep a saved assistant's name at 40 characters or fewer.
• Do not enable paid, HIPAA, PCI, recording, retention, or other compliance behavior unless the user requests it and the current docs support the exact configuration.
• Treat prompts as behavioral instructions, not capabilities or security boundaries. Scheduling, lookup, transfer, messaging, authentication, and other actions require real tools or server-side support.

Procedure