Agent Skills

setup-api-key

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.

Install

npx skills add https://github.com/vapiai/skills --skill setup-api-key
SKILL.md

Vapi API Key Setup

Guide the user through obtaining and configuring a Vapi API key for the voice AI platform.

Workflow

Step 1: Request the API key

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:

  1. Click "Create Key"
  2. Name your key (e.g., "development")
  3. 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.

Step 2: Validate and configure

Once the user confirms the key is stored locally:

  1. 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.

  2. 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"
    
  3. If validation fails (non-200 response):

  4. If validation succeeds, confirm that the local environment file contains this variable without showing its value:

    VAPI_API_KEY=<the-api-key>
    
  5. 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.

Step 3: Verify .gitignore

Check whether .gitignore protects local environment files. If not, add:

.env*
!.env.example

Environment Variable

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

Additional Resources

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.

See the Vapi MCP integration guide for setup instructions across supported agents.

Related skills

entra-app-registrationmicrosoft606KGuides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API permissions, generate service principal, MSAL example, console app auth, Entra ID setup, Azure AD authentication. DO NOT USE FOR: Key Vault secrets (use azure-keyvault-expiration-audit), general Azure resource security guidance.azure-messagingmicrosoft595KTroubleshoot and resolve issues with Azure Messaging SDKs for Event Hubs and Service Bus. Covers connection failures, authentication errors, message processing issues, and SDK configuration problems. WHEN: event hub SDK error, service bus SDK issue, messaging connection failure, AMQP error, event processor host issue, message lock lost, message lock expired, lock renewal, lock renewal batch, send timeout, receiver disconnected, SDK troubleshooting, azure messaging SDK, event hub consumer, servicentra-agent-idmicrosoft328KProvision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmi_path, OBO, cross-tenant) including the Microsoft Entra SDK for AgentID sidecar. USE FOR: Agent Identity Blueprint, BlueprintPrincipal, agent OAuth, fmi_path token exchange, agent OBO, Workload Identity Federation for agents, polyglot agent auth, Microsoft.Identity.Web.AgentIdentities. DO NOT USE FOR: standard Entra app registsupabasesupabase298KUse when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies, getSession, getUser, getClaims, RLS); Supabase CLI or MCP server; schema changes, migrations, declarative schemas, security audits, Postgres extensions (pg_graphql, pg_cron, pg_vector); deb

Search skills and MCP servers

Fuzzy search across 23,137 skills and servers