← VapiCONTENT HISTORY

Update to Vapi

Snapshot Nov 12, 2026 · 18:39 UTC · version 1.3.1

Collection source: downloaded plugin package. These snapshots do not have a confirmed matching collection source. Differences in file lists alone do not establish changes to the package.

WHAT CHANGED

Instructions updated for setup-api-key

Skill instructions — Now says: Use the [Vapi documentation](https://docs.vapi.ai) for current configuration, troubleshooting, and SDK guidance.

Observed in instructions or declared skills. Runtime behavior has not been tested.

Save Vapi and check future changes in Following.

Up to 3 plugins free · no card required.

All fields and original values.

Skill instructions

Before

Sep 30, 2026 · 23:15 UTC

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

After

Nov 12, 2026 · 18:39 UTC

Use the [Vapi documentation](https://docs.vapi.ai) for current configuration, troubleshooting, and SDK guidance.

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -79,7 +79,4 @@
 
 ## 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](https://docs.vapi.ai/cli/mcp) for setup instructions across supported agents.
+Use the [Vapi documentation](https://docs.vapi.ai) for current configuration, troubleshooting, and SDK guidance.
Full technical diff · 1 changed fields

changed /skill_md_contents

BEFORE
"---\nname: setup-api-key\ndescription: 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.\nlicense: MIT\n---\n\n# Vapi API Key Setup\n\nGuide the user through obtaining and configuring a Vapi API key for the voice AI platform.\n\n## Workflow\n\n### Step 1: Request the API key\n\nTell the user:\n\n> To set up Vapi, open the API keys page in the Vapi Dashboard: https://dashboard.vapi.ai/org/api-keys\n>\n> (Need an account? Create one at https://dashboard.vapi.ai/signup first)\n>\n> If you don't have an API key yet:\n> 1. Click **\"Create Key\"**\n> 2. Name your key (e.g., \"development\")\n> 3. Copy the key immediately — it is only shown once\n>\n> 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.\n\nThen wait for the user to confirm that the local environment file is ready. Do not ask them to send or display the key.\n\n### Step 2: Validate and configure\n\nOnce the user confirms the key is stored locally:\n\n1. **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.\n\n2. **Validate the key** by making a request from the environment where it is loaded:\n   ```bash\n    curl -s -o /dev/null -w \"%{http_code}\" https://api.vapi.ai/assistant \\\n      -H \"Authorization: Bearer $VAPI_API_KEY\"\n   ```\n\n3. **If validation fails** (non-200 response):\n   - Tell the user the API key appears to be invalid\n   - Ask them to double-check and try again\n   - Remind them of the URL: https://dashboard.vapi.ai/org/api-keys\n\n4. **If validation succeeds**, confirm that the local environment file contains this variable without showing its value:\n   ```\n   VAPI_API_KEY=<the-api-key>\n   ```\n\n5. **Confirm success:**\n   > Your Vapi API key is configured locally as `VAPI_API_KEY`.\n   >\n   > You can now use Vapi's API to create assistants, make calls, and build voice AI agents.\n   >\n   > Keep this key safe — do not commit it to version control.\n\n### Step 3: Verify .gitignore\n\nCheck whether `.gitignore` protects local environment files. If not, add:\n```\n.env*\n!.env.example\n```\n\n## Environment Variable\n\nAll Vapi skills expect the API key in the `VAPI_API_KEY` environment variable. The base URL for all API requests is:\n\n```\nhttps://api.vapi.ai\n```\n\nAuthentication is via Bearer token:\n```\nAuthorization: Bearer $VAPI_API_KEY\n```\n\n## Additional Resources\n\nVapi 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.\n\n\nSee the [Vapi MCP integration guide](https://docs.vapi.ai/cli/mcp) for setup instructions across supported agents.\n"
AFTER
"---\nname: setup-api-key\ndescription: 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.\nlicense: MIT\n---\n\n# Vapi API Key Setup\n\nGuide the user through obtaining and configuring a Vapi API key for the voice AI platform.\n\n## Workflow\n\n### Step 1: Request the API key\n\nTell the user:\n\n> To set up Vapi, open the API keys page in the Vapi Dashboard: https://dashboard.vapi.ai/org/api-keys\n>\n> (Need an account? Create one at https://dashboard.vapi.ai/signup first)\n>\n> If you don't have an API key yet:\n> 1. Click **\"Create Key\"**\n> 2. Name your key (e.g., \"development\")\n> 3. Copy the key immediately — it is only shown once\n>\n> 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.\n\nThen wait for the user to confirm that the local environment file is ready. Do not ask them to send or display the key.\n\n### Step 2: Validate and configure\n\nOnce the user confirms the key is stored locally:\n\n1. **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.\n\n2. **Validate the key** by making a request from the environment where it is loaded:\n   ```bash\n    curl -s -o /dev/null -w \"%{http_code}\" https://api.vapi.ai/assistant \\\n      -H \"Authorization: Bearer $VAPI_API_KEY\"\n   ```\n\n3. **If validation fails** (non-200 response):\n   - Tell the user the API key appears to be invalid\n   - Ask them to double-check and try again\n   - Remind them of the URL: https://dashboard.vapi.ai/org/api-keys\n\n4. **If validation succeeds**, confirm that the local environment file contains this variable without showing its value:\n   ```\n   VAPI_API_KEY=<the-api-key>\n   ```\n\n5. **Confirm success:**\n   > Your Vapi API key is configured locally as `VAPI_API_KEY`.\n   >\n   > You can now use Vapi's API to create assistants, make calls, and build voice AI agents.\n   >\n   > Keep this key safe — do not commit it to version control.\n\n### Step 3: Verify .gitignore\n\nCheck whether `.gitignore` protects local environment files. If not, add:\n```\n.env*\n!.env.example\n```\n\n## Environment Variable\n\nAll Vapi skills expect the API key in the `VAPI_API_KEY` environment variable. The base URL for all API requests is:\n\n```\nhttps://api.vapi.ai\n```\n\nAuthentication is via Bearer token:\n```\nAuthorization: Bearer $VAPI_API_KEY\n```\n\n## Additional Resources\n\nUse the [Vapi documentation](https://docs.vapi.ai) for current configuration, troubleshooting, and SDK guidance.\n"
Full snapshot data
{
  "description": "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.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 196
    }
  ],
  "name": "setup-api-key",
  "skill_md_contents": "---\nname: setup-api-key\ndescription: 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.\nlicense: MIT\n---\n\n# Vapi API Key Setup\n\nGuide the user through obtaining and configuring a Vapi API key for the voice AI platform.\n\n## Workflow\n\n### Step 1: Request the API key\n\nTell the user:\n\n> To set up Vapi, open the API keys page in the Vapi Dashboard: https://dashboard.vapi.ai/org/api-keys\n>\n> (Need an account? Create one at https://dashboard.vapi.ai/signup first)\n>\n> If you don't have an API key yet:\n> 1. Click **\"Create Key\"**\n> 2. Name your key (e.g., \"development\")\n> 3. Copy the key immediately — it is only shown once\n>\n> 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.\n\nThen wait for the user to confirm that the local environment file is ready. Do not ask them to send or display the key.\n\n### Step 2: Validate and configure\n\nOnce the user confirms the key is stored locally:\n\n1. **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.\n\n2. **Validate the key** by making a request from the environment where it is loaded:\n   ```bash\n    curl -s -o /dev/null -w \"%{http_code}\" https://api.vapi.ai/assistant \\\n      -H \"Authorization: Bearer $VAPI_API_KEY\"\n   ```\n\n3. **If validation fails** (non-200 response):\n   - Tell the user the API key appears to be invalid\n   - Ask them to double-check and try again\n   - Remind them of the URL: https://dashboard.vapi.ai/org/api-keys\n\n4. **If validation succeeds**, confirm that the local environment file contains this variable without showing its value:\n   ```\n   VAPI_API_KEY=<the-api-key>\n   ```\n\n5. **Confirm success:**\n   > Your Vapi API key is configured locally as `VAPI_API_KEY`.\n   >\n   > You can now use Vapi's API to create assistants, make calls, and build voice AI agents.\n   >\n   > Keep this key safe — do not commit it to version control.\n\n### Step 3: Verify .gitignore\n\nCheck whether `.gitignore` protects local environment files. If not, add:\n```\n.env*\n!.env.example\n```\n\n## Environment Variable\n\nAll Vapi skills expect the API key in the `VAPI_API_KEY` environment variable. The base URL for all API requests is:\n\n```\nhttps://api.vapi.ai\n```\n\nAuthentication is via Bearer token:\n```\nAuthorization: Bearer $VAPI_API_KEY\n```\n\n## Additional Resources\n\nUse the [Vapi documentation](https://docs.vapi.ai) for current configuration, troubleshooting, and SDK guidance.\n"
}

SHA-256 of public snapshot: 28e3fffa50b759b1970602fde9cfe7dab17c240fc8d464f86342f017f4da5869