Guide users through obtaining and configuring a Vapi API key. Use when the user needs to set up Vapi, when API calls fail due to missing keys, or when the user mentions needing access to Vapi's voice AI platform.
中文简介正在准备中。当前显示原文说明。
查看安装方法安装前可以查看交给 AI 代理的指令内容。
Guide the user through obtaining and configuring a Vapi API key for the voice AI platform.
Tell the user:
To set up Vapi, open the API keys page in the Vapi Dashboard: https://dashboard.vapi.ai/org/api-keys
(Need an account? Create one at https://dashboard.vapi.ai/signup first)
If you don't have an API key yet:
- Click "Create Key"
- Name your key (e.g., "development")
- Copy the key immediately — it is only shown once
Do not paste a private API key into this chat. Save it locally using the steps below, then tell me when the file is ready.
Then wait for the user to confirm that the local environment file is ready. Do not ask them to send or display the key.
Once the user confirms the key is stored locally:
Confirm the key is available without printing it. Prefer an existing environment variable. Otherwise, ask the user to save it as VAPI_API_KEY in a local .env.local file using their editor. Never display the file contents.
Validate the key by making a request from the environment where it is loaded:
curl -s -o /dev/null -w "%{http_code}" https://api.vapi.ai/assistant \
-H "Authorization: Bearer $VAPI_API_KEY"
If validation fails (non-200 response):
If validation succeeds, confirm that the local environment file contains this variable without showing its value:
VAPI_API_KEY=<the-api-key>
Confirm success:
Your Vapi API key is configured locally as
VAPI_API_KEY.You can now use Vapi's API to create assistants, make calls, and build voice AI agents.
Keep this key safe — do not commit it to version control.
Check whether .gitignore protects local environment files. If not, add:
.env*
!.env.example
All Vapi skills expect the API key in the VAPI_API_KEY environment variable. The base URL for all API requests is:
https://api.vapi.ai
Authentication is via Bearer token:
Authorization: Bearer $VAPI_API_KEY
Vapi provides a documentation MCP server that gives compatible AI agents access to the Vapi knowledge base. Use its documentation search for advanced configuration, troubleshooting, SDK details, and anything beyond this skill.
Manual setup: If your agent doesn't auto-detect the config, run:
claude mcp add vapi-docs -- npx -y mcp-remote https://docs.vapi.ai/_mcp/server
See the Vapi MCP integration guide for setup instructions across supported agents.
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Design, create, or validate saved and transient Vapi voice assistants. Use for new phone or web agents, production system prompts and first messages, saved-versus-transient architecture, model/voice/transcriber selection, multilingual compatibility, existing tool attachment, native call-control tools, assistant hooks, and Create Assistant API validation errors.
中文简介正在准备中。当前显示原文说明。
Create one-off outbound phone calls, web calls, scheduled calls, and simple batch calls using the Vapi API. Use when making or testing individual calls or initiating a bounded /call request programmatically. Use create-campaign for a persistent multi-contact Campaign with lifecycle, reporting, cancellation, duplication, or campaign webhooks.
中文简介正在准备中。当前显示原文说明。
Create, schedule, duplicate, inspect, cancel, archive, and troubleshoot Vapi outbound Campaigns. Use for persistent multi-contact calling, CSV or API contact personalization, campaign concurrency, campaign webhooks, pre-dial eligibility, contact outcomes, or rerunning an audience. Do not use for a single call or a simple one-off /call batch.
中文简介正在准备中。当前显示原文说明。
Plan, provision, import, route, update, and verify Vapi phone numbers through the public API. Use for Vapi-hosted US PSTN numbers, explicitly requested SIP addresses, Twilio/Vonage/Telnyx or BYO carrier numbers, secure credential handling, assistant or squad routing, area-code requests, outbound limitations, and phone-provider troubleshooting.
中文简介正在准备中。当前显示原文说明。
Design, create, update, and verify Vapi Squads and documented handoff tools through the public API. Use for choosing a single assistant versus a multi-assistant Squad, persistent or transient members, entry-member ordering, specialization boundaries, context engineering, variable extraction, model-specific handoff patterns, assistant-version pins, and safe Squad updates.
中文简介正在准备中。当前显示原文说明。
Design, create, inspect, update, attach, detach, preview, execute, and verify reusable Vapi Structured Outputs through public API or Server SDK workflows. Use for post-call extraction, typed call artifacts, AI-versus-regex extraction, JSON Schema design, backfilling existing calls, or retrieving structured results programmatically.
中文简介正在准备中。当前显示原文说明。