How Vamo connects to your AI tool

Your AI tool does not contain Vamo. It sends your question to Vamo and writes up what comes back. Your Vamo account decides what the tool is allowed to do, and you can disconnect it at any time.

The three parts

Your AI tool. This is the assistant you already talk to. It reads your question, decides when Vamo can help, and writes the answer you see.

Vamo. This is where the developer search runs. Your tool reaches it in one of two ways. The first is the Vamo MCP server, a connection made for AI tools. The second is the Vamo API, which skills and coding agents call. MCP, skills and the API explains the difference.

Your Vamo account. Every request arrives with proof of which account it belongs to. That proof is a sign-in you approved in your browser, or an API key you created. That sign-in or key carries its permissions, and Vamo checks them on every request.

When this matters

You do not need this picture to run a search. It helps in three situations:

• You are choosing a way to connect and want to know what each one involves.
• Someone on your team asks what the AI tool can see and do.
• Something stops working and you want to know which part to look at.

One question, from start to finish

Say you ask your tool for backend engineers in a city who have worked at <company>.

1. You type the question in plain language. You do not need special words.
2. Your tool sees that Vamo can answer it. It turns your question into a request.
3. The tool sends the request to Vamo, with your sign-in or your API key attached.
4. Vamo works out which account the request belongs to.
5. Vamo checks the permissions on that sign-in or key. If the request is allowed, Vamo runs the search.
6. Vamo sends the results back to your tool.
7. Your tool reads the results and writes the answer in the conversation.

A follow-up question repeats the same steps. Narrowing the search, saving people to a list and asking for email addresses all travel the same path.

Some steps need a person. Connecting GitHub is one example. In that case Vamo sends back a link, and your tool passes it to you to open.

What your account controls

Your account is the part that says yes or no. The tool cannot give itself more access.

• What a tool may do. Each API key has permissions. You choose them from presets or pick them one by one.
• What no tool may do. A key or signed-in tool can hold search, deep search, deep research, fit rank, lists and contacts. It can never reach projects, outreach, members, billing or key management.
• Who is connected. Set up > API keys shows your keys and when each was last used. Connected tools on the same page lists tools that signed in, with who approved each one.
• How to stop it. Revoke a key or remove a connected tool. Owners and admins see every connected tool on the account.

What Vamo can access covers this from a security point of view.

What to do next

• Not connected yet? Read Choose how to connect, then open Set up > Get started for the current steps for your tool.
• Unsure which kind of proof to use? Read Sign in or API key.