Setup Api Key
ListedHelps with setup and configuration, API as part of agent workflows workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add vapiai/skills --skill setup-api-key -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
vapiai
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.
No undeclared network calls: failed
Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: api.vapi.ai.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
Hosts contacted
api.vapi.aiundeclaredWhat it found
- plugins/vapi-voice-ai/skills/setup-api-key/SKILL.md:38contacts api.vapi.ai
curl -s -o /dev/null -w "%{http_code}" https://api.vapi.ai/assistant \ - setup-api-key/SKILL.md:42contacts api.vapi.ai
curl -s -o /dev/null -w "%{http_code}" https://api.vapi.ai/assistant \
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned vapiai/skills at d91f18561f.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- d91f18561f
- Manifest
- setup-api-key/SKILL.md
- Scanned
- 3 files, 163 lines
- Copies in repo
- 2 — all of them scanned
About this skill
What it does
This skill provides the foundational configuration required to authenticate AI agents with the Vapiai platform. It enables secure communication between your agent and external services by managing API key generation and storage within the Vapiai ecosystem.
When to use it
- You are building an AI agent that needs to interact with third-party APIs on behalf of users.
- Your workflow requires storing sensitive credentials securely rather than hardcoding them into prompts or scripts.
- You need to initialize a new project environment before deploying complex automation tasks.
- You want to ensure your agent has the necessary permissions to access specific Vapiai features.
Key capabilities
- Generates unique API keys for individual AI agents.
- Stores credentials securely within the Vapiai infrastructure.
- Validates authentication tokens during runtime operations.
- Supports integration with various external tools and services via standard API protocols.
Example prompts
- "Set up an API key for my new customer support agent to access our CRM."
- "Configure secure authentication for this data analysis bot using the setup-api-key skill."
- "Initialize credentials so my automation script can connect to the payment gateway securely."
Tips & gotchas
Ensure you have a valid Vapiai account before attempting to generate keys, as the skill requires active platform access. Rotate your API keys periodically and never share them publicly; always store them in secure environment variables or vaults if exporting is necessary.