# Find an email

> Look for the email of a person we do not hold one for, by testing and verifying likely addresses.

Every section below does the same job: in the dashboard (Guide), from your code (API) or through an AI assistant (MCP).

## Guide — In the dashboard

Source: /docs/leads/prospector/find-email

When a search result has no email, we can look for one: likely address patterns are tried and verified. **50 credits** (popular) or **100** (deep), charged even when nothing is found.

1. **Search people** first to get their `profileId`.
2. **Try a reveal first:** it costs 1 credit when we already hold an email.
3. **Then find an email**, popular or deep.


---

## API — From your code

Source: /docs/leads/prospector/find-email/api

Authenticated with `?privateKey=YOUR_KEY` (see [Authentication](/docs/authentication)).

<Endpoints ops={["POST /v3/prospector/people/find-email"]} />

<ApiPlayground
  ops={["POST /v3/prospector/people/find-email"]}
  method="post"
  path="/v3/prospector/people/find-email"
  tool="find_contact_email"
  args={`{
  "websiteId": "64b7f0a1c2d3e4f5a6b7c8d9",
  "profileId": "",
  "depth": "popular"
}`}
/>

### Use case: After a reveal comes back empty [#use-case-after-a-reveal-comes-back-empty]

When `POST /admin/prospector/people/reveal` returns `no-contact-details`, call `POST /v3/prospector/people/find-email` with the same `profileId`.


---

## MCP — AI agents

Source: /docs/leads/prospector/find-email/mcp

Connect the [MCP server](/docs/mcp#quickstart), then just ask.

<Tools names={["find_contact_email"]} />

### Use case [#use-case]

> We have no email for Ava Thompson. Can you find one?

<McpToolCall name="find_contact_email">

```json
{
  "websiteId": "64b7f0a1c2d3e4f5a6b7c8d9",
  "profileId": "3cbd7f0d47879822dd5f722ab6dfac85",
  "depth": "popular"
}
```

</McpToolCall>