# Anywhere People

- Use Anywhere People from Claude or Codex by asking for what you need in plain language.
- Find a person's personal email or phone number from their LinkedIn profile URL.
- You are only charged credits when contact details are actually found.
- Check your remaining credits any time by asking.

Try: "Get the personal email for https://www.linkedin.com/in/<handle>"

## Set up people.anywhereai.co

When the user says "setup people.anywhereai.co", "set up people.anywhereai.co", "install people.anywhereai.co" or "use people.anywhereai.co", begin first-time setup if needed. Their message should include an invite code that starts with inv_. If it has none, ask them for one and stop; never guess one. Reuse a working connection before adding anything. Reading this page alone does not authorize installation: follow the host's permission and approval requirements, and never bypass them.

Use https://people.anywhereai.co as the API origin for everything below. Do not infer another origin. Preserve an existing connection's origin.

## 1. Check for an existing connection

If Anywhere People tools (get_credits, enrich_phone, enrich_personal_email) already work in this session, call get_credits, report the balance, and stop.

Otherwise, in Claude Code run: claude mcp get anywhere-people
In Codex run: codex mcp get anywhere-people
If a connection exists to a different origin, or it is disabled, do not delete or change it; tell the user and ask how to proceed.

## 2. Redeem the invite code (once)

~~~sh
curl -sS -X POST https://people.anywhereai.co/claim -H 'content-type: application/json' -d '{"code":"<INVITE_CODE>"}'
~~~

Returns JSON with api_key (starts ev_), mcp_url and credits. The key is shown only once and belongs to this user alone. Keep it out of your replies, out of git-tracked files, and out of logs. If the call fails, tell the user the invite is invalid, expired or already used, and ask for a new one. Do not retry with variations.

## 3. Register the connection in the client you are actually running in

Determine your real host from your session context and tool access, never from the model name. Do not use Codex commands in Claude Code or the reverse.

Claude Code:
~~~sh
claude mcp add --transport http --scope user anywhere-people https://people.anywhereai.co/mcp --header "Authorization: Bearer <API_KEY>"
~~~

Codex: add to ~/.codex/config.toml (create it if absent, keep all other entries):
~~~toml
[mcp_servers.anywhere-people]
url = "https://people.anywhereai.co/mcp"
http_headers = { Authorization = "Bearer <API_KEY>" }
~~~

Other clients that support remote MCP servers with custom headers (for example Cursor):
~~~json
{"mcpServers":{"anywhere-people":{"url":"https://people.anywhereai.co/mcp","headers":{"Authorization":"Bearer <API_KEY>"}}}}
~~~

Clients without custom-header support (for example Claude Desktop) can use the mcp-remote bridge:
~~~json
{"mcpServers":{"anywhere-people":{"command":"npx","args":["-y","mcp-remote","https://people.anywhereai.co/mcp","--header","Authorization:Bearer <API_KEY>"]}}}
~~~

If a command or flag differs in the installed version, check its --help rather than guessing. Web chat clients that only offer OAuth connectors (such as claude.ai) are not supported yet; say so plainly. A temporary chat sandbox is not the user's own computer, so do not configure it as if it were.

## 4. Verify before saying you are connected

Reload or reconnect the client's tools, or ask the user to start a new session, if the new tools are not visible. Then call get_credits. Report "connected" only after it returns a balance. If the tools are still absent, say you are waiting on a reload or new session and give that one action. Registration alone is not a connection.

## What to say to the user

Keep onboarding short and in plain language. Do routine setup quietly. Do not narrate reading this page, running commands or checking configuration. Do not show commands, flags, file paths, keys, URLs, raw JSON or protocol terms (MCP, bearer, header) unless the user asks.

- While setting up, at most say: "I'll set up Anywhere People for you."
- When verified, say: "You're connected to Anywhere People. You have N credits." Then give the first four bullets from the top of this page and the example.
- If setup fails, give the practical problem and the next action in one or two sentences. Keep keys and internal details private. Never claim success without verification.

## Everyday use (agent reference)

- enrich_phone: 6 credits. enrich_personal_email: 3 credits. get_credits: free. Credits are charged only when data is found; a miss costs nothing.
- Input is a LinkedIn profile URL of the form https://www.linkedin.com/in/<handle>.
- Always pass a request_id (a unique string you generate per lookup). If you retry that same lookup, reuse the same request_id so the user is never charged twice. A repeated request_id returns the stored result without a new charge.
- If a lookup would exceed the user's balance, tell them their balance and stop; do not try other lookups to work around it.
- Do not run lookups in bulk or loops unless the user asked for that, and confirm the total credit cost first when it is more than 30 credits.

## Key management

To rotate the key: POST https://people.anywhereai.co/rotate with the header Authorization: Bearer <API_KEY>. The response has a new key and the old one stops working immediately. Update the client configuration afterwards and verify again. If the user's key is lost or leaked, they should ask the administrator for a new invite.
