---
ref: tool:looot/find-work-email
name: Find a work email
company: company:looot
workflows: []
access: [mcp, api]
tags: [capability:find-work-emails, category:data-provider, has:api, has:mcp]
docs: https://docs.looot.ai/mcp-tools/run
updated: 2026-10-16
---

# Find a work email

Returns a work email for one person from a name and a company domain, using the first provider looot can run.

Note: Set `endpointId` to `job:people.email.find` and `input` to first_name, last_name and domain, plus an `idempotencyKey`. About $0.0036 per call at the cheapest provider; a miss is a normal answer.

## Set up

Use the first option your agent supports.

### MCP (official, remote)

Add this server to your agent's MCP settings, then sign in when asked.

```json
{ "mcpServers": { "looot": { "url": "https://api.looot.ai/mcp" } } }
```

Call the MCP tool `run` with `POST /v1/runs`.

Server URL: https://api.looot.ai/mcp

Note: Your client signs you in with the browser (OAuth 2.1 with dynamic client registration). A header token, Authorization Bearer, also works for CI.

### API (official)

- Base URL: https://api.looot.ai
- Endpoint: `POST /v1/runs`
- Auth: send the header `Authorization: Bearer $LOOOT_TOKEN`
- Get a key: https://looot.ai/settings
- Docs: https://docs.looot.ai/reference

Note: Send the token as Authorization Bearer. Every run needs an idempotencyKey. A workspace starts at $0, so top up before the first run.

Before anything else, confirm access with the cheapest read-only call, like a list or a search. Never send or change anything to test access.

## Rules

- Ask the user before anything that sends messages, costs money, or changes data, and say how many records it touches. One approval covers a batch the user has seen.
- Never print API keys.