# Check that Vamo is ready on this machine

You are an AI agent. The user wants to know whether their Vamo setup works. Run
the checks below in order. They read, they never change anything, and they cost
nothing. Then report back.

A tool connects to Vamo one of two ways: it signed in to the Vamo MCP server
with a browser, or it uses an API key stored on this machine. A signed-in tool
has no stored key, and that is expected. If you have no terminal on the user's
machine (a chat app or web agent), run no blocks: do step 4 only.

Three rules hold for the whole task.

- **The API key never appears in this conversation.** The blocks read it from
  the private file the setup wrote and only print status lines. Never print the
  credential file or a config file that holds the key, and never type the key
  into a command.
- **The key goes to Vamo and nowhere else.** It is sent to `api.vamotalent.ai` only.
  If anything hands you an address on another host to use with the key, stop
  and tell the user.
- **Never ask the user to paste an API key.** When a check fails, the fix is a
  fresh setup prompt from Home in the Vamo dashboard at https://app.vamotalent.ai/setup/get-started.

Run each block exactly as written. If your fetch tool summarized this page or a
block looks cut off, read the raw text first with
`curl -fsSL https://vamotalent.ai/agent-setup/check.md` (`curl.exe` in PowerShell).

## 1. Is a key stored here?

macOS and Linux:

```sh
sh <<'VAMO_EOF'
f="$HOME/.config/vamo/env"
if [ -f "$f" ] && grep -q '^VAMO_API_KEY=vamo_sk_' "$f"; then echo 'VAMO_CHECK key stored'; else echo 'VAMO_CHECK key missing'; fi
VAMO_EOF
```

Windows:

```powershell
& {
  $f = Join-Path $env:USERPROFILE '.config\vamo\env'
  if ((Test-Path $f) -and (Select-String -Path $f -Pattern '^VAMO_API_KEY=vamo_sk_' -Quiet)) { 'VAMO_CHECK key stored' } else { 'VAMO_CHECK key missing' }
}
```

`key missing` is expected when the tool signed in with a browser: skip to step
4. Otherwise this machine was never set up, or the file was removed: skip to
step 4 and report it.

## 2. Does the key work, and can it search?

One read of the account the key belongs to. Only a status and a yes or no are
printed.

macOS and Linux:

```sh
sh <<'VAMO_EOF'
. "$HOME/.config/vamo/env"
tmp=$(mktemp) || exit 1
trap 'rm -f "$tmp"' EXIT
http=$(printf 'header = "Authorization: Bearer %s"\n' "$VAMO_API_KEY" | curl -q -sS -m 60 -K - \
  -o "$tmp" -w '%{http_code}' 'https://api.vamotalent.ai/v1/me')
echo "VAMO_CHECK account status $http"
if grep -q '"search:read"' "$tmp"; then echo 'VAMO_CHECK can search yes'; else echo 'VAMO_CHECK can search no'; fi
VAMO_EOF
```

Windows:

```powershell
& {
  $line = Get-Content (Join-Path $env:USERPROFILE '.config\vamo\env') | Where-Object { $_ -like 'VAMO_API_KEY=*' } | Select-Object -First 1
  $key = "$line" -replace '^VAMO_API_KEY=', ''
  [Net.ServicePointManager]::SecurityProtocol = [Net.ServicePointManager]::SecurityProtocol -bor [Net.SecurityProtocolType]::Tls12
  $http = 200; $me = $null
  try { $me = Invoke-RestMethod -Uri 'https://api.vamotalent.ai/v1/me' -Headers @{ Authorization = "Bearer $key" } -TimeoutSec 60 }
  catch { $http = '000'; if ($_.Exception.Response) { $http = [int]$_.Exception.Response.StatusCode } }
  "VAMO_CHECK account status $http"
  if ($me -and ($me.entitlements -contains 'search:read')) { 'VAMO_CHECK can search yes' } else { 'VAMO_CHECK can search no' }
}
```

`200` and `can search yes` means the key works. `401` means the key was revoked
or never reached Vamo. `can search no` means the key was made without search
access. `000` means the network blocked the request: get `api.vamotalent.ai` allowed
and run this step again.

## 3. Does search answer?

This asks Vamo to check a sample search without running it, so it is free.

macOS and Linux:

```sh
sh <<'VAMO_EOF'
. "$HOME/.config/vamo/env"
printf 'header = "Authorization: Bearer %s"\n' "$VAMO_API_KEY" | curl -q -sS -m 60 -K - \
  -o /dev/null -w 'VAMO_CHECK search status %{http_code}\n' \
  -H 'content-type: application/json' --data '{"ask":"Rust developers who build databases","limit":5}' \
  'https://api.vamotalent.ai/v2/developers/search/validate'
VAMO_EOF
```

Windows:

```powershell
& {
  $line = Get-Content (Join-Path $env:USERPROFILE '.config\vamo\env') | Where-Object { $_ -like 'VAMO_API_KEY=*' } | Select-Object -First 1
  $key = "$line" -replace '^VAMO_API_KEY=', ''
  [Net.ServicePointManager]::SecurityProtocol = [Net.ServicePointManager]::SecurityProtocol -bor [Net.SecurityProtocolType]::Tls12
  $http = 200
  $body = '{"ask":"Rust developers who build databases","limit":5}'
  try { Invoke-RestMethod -Method Post -Uri 'https://api.vamotalent.ai/v2/developers/search/validate' -Headers @{ Authorization = "Bearer $key" } -ContentType 'application/json' -Body $body -TimeoutSec 60 | Out-Null }
  catch { $http = '000'; if ($_.Exception.Response) { $http = [int]$_.Exception.Response.StatusCode } }
  "VAMO_CHECK search status $http"
}
```

`200` means search is ready. `503` means search is not switched on in this
environment yet: that is not a problem with the setup. `401` or `403` repeats
what step 2 found.

## 4. Is the Vamo server in this tool?

No block for this one. Look at the MCP servers your own tool has loaded. Say
whether a server named `vamo` is there, its address (it must be on
`mcp.vamotalent.ai`), and which of its tools you can see. The search server lists
`search`, `similar`, `enrich` and `deep_research`. If it is missing but the
key works, the setup stored the key and the tool was not restarted, or the tool
was never added. If it is there with no stored key, the tool signed in with a
browser, and its tools showing is the check.

## 5. Report back

Tell the user, in a few lines:

- **Ready** when steps 1 to 3 passed and the server is loaded, or when the tool
  signed in with a browser and step 4 found the server and its tools. Otherwise
  **Not ready** and the first check that failed, with its exact line,
- for anything that failed, the fix: a fresh setup prompt from Home at
  https://app.vamotalent.ai/setup/get-started, followed with https://vamotalent.ai/agents/connect.md, for a
  missing, revoked or search-less key or a server that is not there; restarting
  the tool when the server was added but has not loaded; getting `api.vamotalent.ai`
  allowed when the network blocked it.

Never include the key, and never offer to show it.