Which hosts to allow for Vamo on a company network

Vamo uses three hosts: app.vamotalent.ai, api.vamotalent.ai and mcp.vamotalent.ai. Allowing all three covers every way a tool can connect. If your network blocks them, an IT contact can allow them, and Vamo can work with that person directly.

What each host is for

app.vamotalent.ai is the Vamo app. People sign in to Vamo here in a browser. Keys are created here, at Set up > API keys. The same screen lists the tools connected to the account.

api.vamotalent.ai is the Vamo API. Vamo skills call it with an API key. So does a tool set up with a setup code, and any code your developers write. Browser sign-in also starts here before it sends the person to the app.

mcp.vamotalent.ai is the Vamo MCP server. An AI tool that adds Vamo as a connector talks to this host. The tool connects by browser sign-in or with an API key.

Which hosts a tool needs

It depends on the way the tool connects. Choose how to connect compares the ways.

• A connector, by browser sign-in. All three hosts. The tool talks to the MCP host. Sign-in passes through the API host and the person approves on the app host.
• A connector, with an API key. The tool needs the MCP host. The person needs the app host to create the key.
• Skills, a setup code or the direct API. The tool needs the API host. The person needs the app host to create a key or get a setup code.

Some AI tools run skills in a sandbox with its own network rules. There, the API host must be allowed in the tool's own settings too. On a team or enterprise workspace only an owner of that workspace can do it. Connectors are not subject to that setting. Claude Team and Enterprise admins covers it.

If your company does not allow command-line tools

Vamo does not require one. An AI tool that runs in a browser can connect by browser sign-in. The tool opens a Vamo page, the person approves, and the tool is connected.

Nothing is installed on the computer. No API key is handled. Sign in or API key explains the difference.

What a connected tool can do

Your security team will ask this first. A key or signed-in tool can hold only these permissions:

• Search, deep search and deep research
• Fit rank
• Lists
• Contacts

It can never reach projects, outreach, members, billing or key management. A tool that signs in gets the search and enrich permissions by default. A key gets the permissions chosen when it was created.

The MCP server cannot read account, usage or billing information.

Who controls access

Access is controlled in Vamo at Set up > API keys.

• Owners and admins see every connected tool on the account.
• Each signed-in tool shows who approved it.
• Removing a tool disconnects it.
• A key can be revoked. There is no rotate: make a new key and revoke the old one.
• A read-only member cannot create keys.

Connected tools and keys describes that screen.

If your company has not approved Vamo yet

Wait for the approval. Do not connect from a personal AI tool account to get around your company's controls.

Send this article to the person who decides. It lists the hosts and the limits on what a connected tool can do. It does not describe how Vamo handles data. Ask Vamo for that directly.

Working with your IT team

Vamo can work with an authorized IT contact at your company. Tell Vamo who that person is and how your tools connect. Use the "Tell us" link at the bottom of this page to start.

Your IT contact can check the network path without a key. The API host serves its specification to anyone who can reach it. If that request fails from inside your network, the host is not reachable from it. The API reference has the details.