# Set up Ekos from your AI agent

> Ekos finds people who show a live buying signal for what your user sells, explains in plain words why each one is a fit, and runs LinkedIn outreach from the user's own account. The user starts with 10 free credits, no card. You can do the whole setup from this chat.

Updated 2026-11-21 · https://www.ekoslabs.com/agent-signup

Everything happens with your user's say-so, in this chat. Nothing runs in the background.

## 1. Sign the user up

Ask the user once: "Want me to set up Ekos for you? I just need your work email." Then send the email. Use your own name for agent: claude-code, codex, cursor, openclaw or similar.

```sh
curl -s -X POST https://app.ekoslabs.com/api/agent/signup/start \
  -H 'content-type: application/json' \
  -d '{"email":"USER_EMAIL","agent":"claude-code"}'
```

The answer is JSON with ok: true. Ekos emails the user a 6-digit code that works for 10 minutes. Ask the user for it.

Then verify the code. This run saves the key to ~/.config/ekos/key (only the user can read it) and prints the answer with the key hidden:

```sh
umask 077 && mkdir -p ~/.config/ekos
curl -s -X POST https://app.ekoslabs.com/api/agent/signup/verify \
  -H 'content-type: application/json' \
  -d '{"email":"USER_EMAIL","code":"123456","agent":"claude-code"}' > ~/.config/ekos/signup.json
sed -n 's/.*"key":"\(ekos_[A-Za-z0-9_-]*\)".*/\1/p' ~/.config/ekos/signup.json > ~/.config/ekos/key
chmod 600 ~/.config/ekos/key
sed 's/"key":"[^"]*"/"key":"(saved to ~\/.config\/ekos\/key)"/' ~/.config/ekos/signup.json
rm ~/.config/ekos/signup.json
[ -s ~/.config/ekos/key ] || echo "No key saved. Read the error above."
```

- Never show the key in the chat and never write it into the project or a repository.
- A wrong code answers 401 with triesLeft. After 5 wrong tries, or after 10 minutes, start again with a new code.
- new_account in the answer tells you if this email just joined. A new account already has its free credits.

## 2. Connect the Ekos tools

Claude Code, in a terminal:

```sh
claude mcp add --transport http -s user ekos https://app.ekoslabs.com/mcp --header "Authorization: Bearer $(cat ~/.config/ekos/key)"
```

Codex:

```sh
printf '\n[mcp_servers.ekos]\nurl = "https://app.ekoslabs.com/mcp"\nhttp_headers = { Authorization = "Bearer %s" }\n' "$(cat ~/.config/ekos/key)" >> ~/.codex/config.toml
```

Cursor: add this server to ~/.cursor/mcp.json (your home folder, not the project), with the real key in place:

```sh
{ "mcpServers": { "ekos": { "url": "https://app.ekoslabs.com/mcp", "headers": { "Authorization": "Bearer <the key from ~/.config/ekos/key>" } } } }
```

New tools show up after the client restarts. You do not have to wait: call the same tools right now over HTTP. List them:

```sh
curl -s https://app.ekoslabs.com/mcp \
  -H "Authorization: Bearer $(cat ~/.config/ekos/key)" \
  -H 'content-type: application/json' \
  -H 'accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
```

Call one, starting with get_setup_status:

```sh
curl -s https://app.ekoslabs.com/mcp \
  -H "Authorization: Bearer $(cat ~/.config/ekos/key)" \
  -H 'content-type: application/json' \
  -H 'accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_setup_status","arguments":{}}}'
```

The answer is JSON-RPC. The tool's reply is the text in result.content.

## 3. Get the user to their first leads

- Call get_setup_status first. It says where the account stands and the one next step (recommended_next_action).
- Ask one question: "What is your website, and who do you sell to?" Save the answer with update_settings (website, what they sell, who to, roles, area).
- Start the first leads with find_more_leads. They are paid from the free credits. Say what it does before you call it.
- Show the leads with list_leads: who they are, their company, and the buying signal in plain words.
- Ask before anything that spends credits or sends on LinkedIn. Agents cannot pay: for a top-up, give the user the link from top_up_link.

update_settings takes the changes under patch, for example:

```sh
curl -s https://app.ekoslabs.com/mcp \
  -H "Authorization: Bearer $(cat ~/.config/ekos/key)" \
  -H 'content-type: application/json' \
  -H 'accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"update_settings","arguments":{"patch":{"website_url":"acme.com","offer":"What the user sells","sells_to":"Who they sell to"}}}}'
```

## No shell? (claude.ai, the Claude app, ChatGPT)

- Claude: Settings, Connectors, Add custom connector. URL: https://app.ekoslabs.com/mcp. Then Connect, sign in with the work email and press Allow.
- ChatGPT: Settings, Connectors (developer mode), Create. URL: https://app.ekoslabs.com/mcp, authentication OAuth. Then sign in and press Allow.
- Or the user signs up in the browser first: https://app.ekoslabs.com/app/start

Then come back to the chat and call get_setup_status.

## Links

- Human page: https://www.ekoslabs.com/agent-signup
- MCP server: https://app.ekoslabs.com/mcp (Streamable HTTP, Bearer key or OAuth sign-in)
- Ekos Leads for agents: https://www.ekoslabs.com/leads.md
- Site guide for agents: https://www.ekoslabs.com/llms.txt
