Connect Claude Code to Vamo

Claude Code can connect to Vamo five ways. They are browser sign-in, a setup code, an API key, the Vamo skills plugin, and the API called directly. All five work. Most people should sign in or use a setup code, and add the skills for work they repeat.

The ways Claude Code can connect

Sign in with your browser. Claude Code opens a Vamo page. You approve, and Claude Code is connected. No key is handled.

A setup code. The Vamo app shows one line with a single-use code in it. You paste the line into Claude Code. Claude Code trades the code for a key and configures itself.

A connection with an API key. Claude Code sends a Vamo API key with each request. You create the key and choose its permissions.

The Vamo skills plugin. Skills are instructions Claude Code reads. They call the Vamo API with your key. They do not use the connection above.

The API, called directly. Claude Code is a coding agent. It can call the Vamo API itself with a key. This suits scripts and code you are building.

Which one we recommend

Sign in, or use a setup code. Either suits most people, and neither asks you to copy a key by hand. A signed-in tool gets the search and enrich permissions by default.

Choose a key when you want to pick the permissions yourself. Sign in or API key compares the two.

Add the skills plugin for work you repeat. A skill is written instructions, so Claude Code works the same way each time you ask. Skills and a connection can sit side by side.

Use the API directly when Claude Code is writing software that calls Vamo. Give a coding agent the Vamo API covers that route.

What you need

• A Vamo account on a Pro or Enterprise plan. Approving a sign-in and creating a key both need one.
• A role that can create keys: owner, admin or user. A read-only member cannot.
• For the key, skills and direct API routes, a key from Set up > API keys. It is shown once.
• For skills, somewhere Claude Code can find the key. Skills look in your environment first, then in a private file on your computer.

Where to get the current steps

The steps change as Claude Code changes. They live in places that are kept current.

Open the Set up > Get started at Set up > Get started and choose Claude Code. It offers sign-in first and writes the current command for you. Choose the setup code instead if you want that route. The same card is on Set up > API keys.

To have Claude Code set itself up, hand it the agent setup page.

For the plugin, follow the skills install page. You can browse every skill in the skills catalog, or in the app at Set up > Skills.

For the direct route, the API reference lists every operation.

What a first good result looks like

Start a new session and ask for people. For example:

Use Vamo to find the strongest engineers at <company>.

A good answer names real developers, says what each has built, and says why they fit.

Then open Set up > API keys. A signed-in Claude Code appears under Connected tools, with who approved it. A key shows when it was last used.

What commonly goes wrong

• The Vamo page will not let you approve. Your plan or role may not include it. See Sign-in fails.
• The setup code is refused. A setup code works once and lasts ten minutes. Get a fresh line from that section. See Setup code didn't work.
• A skill asks for your key every session. Claude Code has nowhere to find it. The API access skill walks through where to keep it.
• Claude Code asks you to sign in again. A signed-in tool must sign in again after 90 days unused.
• A signed-in Claude Code cannot do something a key can. Sign-in gives the search and enrich permissions. Create a key to choose others.

If something is not working