Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Manage Vapi voice assistants, calls, phone numbers, tools, and webhooks via Vapi REST API or CLI commands within OpenClaw.
Manage Vapi voice assistants, calls, phone numbers, tools, and webhooks via Vapi REST API or CLI commands within OpenClaw.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Use this skill when you need to manage Vapi voice agents (assistants), calls, phone numbers, tools, and webhooks from an OpenClaw agent. This skill is API-first (Vapi REST) and optionally integrates with the Vapi CLI for MCP docs / local workflows.
Create/update/list assistants Start/inspect/end calls Manage phone numbers Create/manage tools (function calling) Configure webhooks and inspect events
Set one of: VAPI_API_KEY (recommended) β Vapi dashboard API key.
Store as a Gateway secret/env var (preferred), or Export in your shell before running helper scripts. Never paste the key into public logs.
Base URL: https://api.vapi.ai Auth: Authorization: Bearer $VAPI_API_KEY API reference: https://api.vapi.ai/api (Swagger)
This skill supports both approaches; you can decide later per deployment. Set VAPI_MODE=api to prefer REST (default) Set VAPI_MODE=cli to prefer the Vapi CLI (interactive)
This repo includes a tiny Node helper: skills/vapi/bin/vapi-api.mjs Examples: # list assistants VAPI_API_KEY=... node skills/vapi/bin/vapi-api.mjs assistants:list # create assistant VAPI_API_KEY=... node skills/vapi/bin/vapi-api.mjs assistants:create \ --name "Claw Con Concierge" \ --modelProvider openai --model gpt-4o-mini \ --voiceProvider 11labs --voiceId rachel # start an outbound call (example shape; see swagger for required fields) VAPI_API_KEY=... node skills/vapi/bin/vapi-api.mjs calls:create \ --assistantId asst_xxx \ --to "+14155551234" \ --from "+14155559876"
If VAPI_MODE=cli, prefer using the CLI for management tasks and fall back to REST if the CLI isnβt installed. Docs: https://docs.vapi.ai/cli https://github.com/VapiAI/cli Install: curl -sSL https://vapi.ai/install.sh | bash vapi login
This improves IDE assistance (Cursor/Windsurf/VSCode): https://docs.vapi.ai/cli/mcp vapi mcp setup
When the user asks for Vapi changes: Clarify scope: assistants vs phone numbers vs webhooks vs tool calls. Prefer read-only queries first (list/get) before destructive changes. When creating an assistant, ask for: assistant name model provider/model voice provider/voice id tools/function calling needs webhook URL (if using server events) When initiating calls, confirm: to/from numbers assistantId compliance constraints (recording, consent)
skills/vapi/SKILL.md β this file skills/vapi/bin/vapi-api.mjs β minimal REST helper
Vapi docs intro: https://docs.vapi.ai/quickstart/introduction Vapi CLI: https://github.com/VapiAI/cli Vapi MCP: https://docs.vapi.ai/cli/mcp Vapi API (Swagger): https://api.vapi.ai/api Example server (Node): https://github.com/VapiAI/example-server-javascript-node OpenClaw: https://github.com/openclaw/openclaw
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.