Vapi

Communication

Vapi for AI agents. Managed auth, ready-made tools.

Start outbound voice calls, read call transcripts and manage voice assistants in Vapi on behalf of each of your users.

About Vapi

With the Vapi connector, your agent works in each user’s own Vapi account. It can list and update voice assistants, start an outbound phone call, list past calls and read a call’s details and transcript, using only the tools your project allows.

Vapi is a platform for building voice AI agents that make and answer phone calls.

Tools

What your agent can do in Vapi.

Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Vapi connection.

  • List assistants

    Read
    vapi_list_assistants

    List the voice assistants in the account.

  • Get an assistant

    Read
    vapi_get_assistant

    Read an assistant's settings.

  • Update an assistant

    Write
    vapi_update_assistant

    Change an assistant's settings, such as its first message.

  • Create a call

    Write
    vapi_create_call

    Start an outbound phone call with an assistant.

  • List calls

    Read
    vapi_list_calls

    List past and active calls.

  • Get a call

    Read
    vapi_get_call

    Read a call's status, transcript and summary.

  • List phone numbers

    Read
    vapi_list_phone_numbers

    List the phone numbers in the account.

Control

Limits you can set.

You decide what your agent may do in Vapi, and Agent200 runs every call within those limits.

  • Turn single tools on or off

    Let the agent read calls and transcripts, and switch off vapi_create_call so it can never start a phone call.

  • Restrict what the agent reaches

    Choose the endpoints a project may use, for example calls but not assistants. A call outside them is refused.

Get started

Connect Vapi
in three steps.

  1. 1

    Set up the SDK

    Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.

    agent.js
    Conceptual example
    Set up the SDK with the Agent200 API key
    // One Agent200 API key covers every connector enabled for the project.
    const agent200 = new Agent200({
      apiKey: process.env.AGENT200_API_KEY,
    });
  2. 2

    Let your user connect Vapi

    Each end user authorizes their own Vapi account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.

    connect.js
    Conceptual example
    Let an end user connect their account (managed OAuth)
    // Each end user authorizes their own Vapi account, once.
    const connection = await agent200
      .user("user_123")
      .connect("vapi");
    
    if (connection.authorizationUrl) {
      // Show this link to your user; Agent200 handles the rest.
      console.log(connection.authorizationUrl);
    }
  3. 3

    Run with the Vapi tools

    Name the user, the model and the tools. The model decides which Vapi tools to call, and Agent200 executes them with that user's connection.

    run.js
    Conceptual example
    Run a request with the connector's tools
    const result = await agent200
      .user("user_123")
      .run({
        model: "openai/gpt-5.6-sol",
        input: "Call +1 415 555 0134 with my booking assistant",
        tools: ["vapi"],
      });
    
    console.log(result.output);

Access

Sign-in and permissions.

  • Who signs in

    Each of your users, once, connecting their own Vapi account. Each connection belongs to that user.

  • What access is requested

    Access to the parts of their Vapi account the connection needs, such as assistants, calls and phone numbers. Users can revoke it later from their Vapi account settings.

For agents

Instructions for AI agents.

Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Vapi connector and how to use it.

Agent brief
Connector: Vapi, through Agent200. In code: "vapi".
What it does: Start outbound voice calls, read call transcripts and manage voice assistants in Vapi on behalf of each of your users.
Page: https://www.agent200.com/connectors/vapi/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Sign-in is managed OAuth. Each end user approves access once, on Vapi's own page, through the authorization link Agent200 returns. Never ask a user for a Vapi password or token in chat.
3. Give every request a stable id for the end user. Agent200 uses only that user's own connection.
4. Read tools: vapi_list_assistants, vapi_get_assistant, vapi_list_calls, vapi_get_call, vapi_list_phone_numbers. Write tools: vapi_update_assistant, vapi_create_call. Name "vapi" in the tools of a request; the model decides which tool to call.
5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it.
6. Before a write, confirm with the user, unless they asked for that exact change.
7. For setup with a specific framework, follow its guide:
   https://www.agent200.com/connectors/vapi/framework/claude/
   https://www.agent200.com/connectors/vapi/framework/chatgpt/
   https://www.agent200.com/connectors/vapi/framework/claude-code/
   https://www.agent200.com/connectors/vapi/framework/muse/
   https://www.agent200.com/connectors/vapi/framework/grok-bot/
   https://www.agent200.com/connectors/vapi/framework/openai-dots/
   https://www.agent200.com/connectors/vapi/framework/claude-duet/
   https://www.agent200.com/connectors/vapi/framework/hermes-agent/
   https://www.agent200.com/connectors/vapi/framework/openclaw/

The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

This page is also available as Markdown, for agents and LLMs: /connectors/vapi.md

Guides

Use Vapi with the AI you build on.

Step-by-step setup for Vapi with a specific model, assistant or agent framework.

FAQ

Vapi and Agent200, answered.

Who handles the Vapi OAuth flow and the tokens?

Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Vapi.

Does my agent act as the end user?

Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Vapi connection, never another user's. It cannot reach anything the user or Vapi has not authorized.

Can I limit what my agent can do in Vapi?

Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.

  • Slack

    Slack

    Search conversations and post messages in the workspaces your users connect.

    Managed OAuth Communication
  • Microsoft Teams

    Microsoft Teams

    Read channels and chats, post messages and set up meetings in Microsoft Teams on behalf of each of your users.

    Managed OAuth Communication
  • Discord

    Discord

    Read channels, post messages and start threads in the Discord servers your users connect.

    Managed OAuth Communication
  • Zoom

    Zoom

    Schedule, update and review Zoom meetings and their cloud recordings on behalf of each of your users.

    Managed OAuth Communication
200 OK

Start with Vapi.
Your agent does the rest.

Your users connect their own Vapi accounts. Agent200 handles the OAuth, the tokens and every tool call.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)