# Email Finder & Verifier API — Find Verified B2B Emails (`qualifyops/email-finder-verified`) Actor

Email finder + verifier: give a name and company domain, get their verified, deliverable work email — live SMTP check, catch-all excluded, no bounces. Find and verify anyone's business email before you send. Pay only per verified email found. B2B leads, cold email, sales prospecting.

- **URL**: https://apify.com/qualifyops/email-finder-verified.md
- **Developed by:** [QualifyOps](https://apify.com/qualifyops) (community)
- **Categories:** Lead generation, Business
- **Stats:** 24 total users, 21 monthly users, 99.2% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $8.00 / 1,000 verified email founds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

### Email Finder + Verifier — Name & Domain → Deliverable Email

**You give:** a person's name and their company domain — e.g. `Patrick Collison` + `stripe.com`.
**You get:** their **verified, deliverable email address** — one confirmed mailbox, with a confidence score, marked **FOUND** or **NOT\_FOUND**.
**You pay:** **only per verified email found — $0.008.** Not-found is **free**.

No LinkedIn, no scraping of protected sources. This is a deterministic **pattern engine** plus **live deliverability verification** — the two things that actually turn a name into an address you can send to.

***

#### Why "verified" is the whole point

Most email finders hand you `first.last@company.com` and call it a day. You send, it bounces, and your domain reputation takes the hit. Here, every `FOUND` address has been through:

> pattern generation → syntax → MX record → **live SMTP mailbox check** → catch-all detection → confidence score

Only an address that a real mail server **accepts**, that is **not catch-all**, at **confidence ≥ 0.80**, is returned as `FOUND`. Everything else is `NOT_FOUND` with a reason and a clearly-labelled `best_guess` — never a silent, billed guess.

#### How it works

1. **Normalize** the name (lowercase, strip accents/punctuation) and the domain (strip `https://`, `www.`, paths — full URLs are fine).
2. **Generate candidates** in priority order: `first.last`, `first`, `flast`, `firstlast`, `first_last`, `f.last`, `last.first`, `lastf`, `first-last`, `last` — each `@domain`.
3. **Optional site scan** (`siteScan`, on by default): fetch the company's homepage, `/contact` and `/about` and promote any **published** address that matches a candidate to the front — those are real, not guesses.
4. **Local pre-filter (free):** drop bad-syntax candidates and, if the domain has **no MX record at all**, return `NOT_FOUND` immediately — with **no charge**.
5. **One batched deliverability check:** survivors go to a proven Apify Store validator with real SMTP egress, in a single call per run.
6. **Pick the winner:** the first deliverable, non-catch-all, confident address becomes `FOUND`. **You are charged only for FOUND.**

#### What each row gives you

| Column | Meaning |
|---|---|
| `action` | **FOUND** (verified deliverable) or **NOT\_FOUND** (with reason) |
| `firstName` / `lastName` | The person you asked about |
| `domain` | The normalized company domain |
| `verified_email` | The deliverable address — **only on FOUND** |
| `pattern` | Which pattern won (`first.last`, `flast`, `published`, …) |
| `confidence` | 0–1 deliverability confidence |
| `source` | `pattern` (generated) or `published` (found on the company site) |
| `candidates_checked` | How many addresses were tested |
| `reason` | On NOT\_FOUND: `catch_all_domain` / `all_rejected` / `no_mx` / `verifier_unavailable` |
| `best_guess` / `best_guess_confidence` | On NOT\_FOUND: the most-likely address, **clearly not verified** |

#### Honest by design

- We **never invent** an address and label it verified. `FOUND` means a live mail server accepted that specific mailbox.
- **Catch-all domains** — which accept everything and confirm nothing — are returned as `NOT_FOUND` (`catch_all_domain`) and **are not charged**. We will not bill you for a domain that cannot actually confirm the person.
- If the verifier is unavailable, we degrade to `NOT_FOUND` (`verifier_unavailable`) — never a fabricated "deliverable" result, never a charge.
- A `best_guess` is always presented as a guess, never as a verified address.

#### For agents & automation

Call it via the Apify **API** or **MCP**. Pass an array of `{firstName, lastName, domain}` (or `{fullName, domain}`) and get back deduped, verified rows — ideal as a step in an enrichment pipeline. **Schedule** it for recurring enrichment of a lead list into your CRM or sequencer. You pay only for the addresses that are actually deliverable.

***

*Input: `people` (array of name + domain). Optional: `maxCandidatesPerPerson` (cost cap), `siteScan`, `verifierActorId`, `requestTimeoutSecs`.*

# Actor input Schema

## `people` (type: `array`):

Each item: {"firstName":"...","lastName":"...","domain":"..."}. You may pass "fullName" instead of first/last, and a full URL instead of a bare domain — both are normalized.

## `maxCandidatesPerPerson` (type: `integer`):

Upper bound on how many candidate addresses are sent to the verifier per person (caps cost).

## `siteScan` (type: `boolean`):

Fetch homepage, /contact and /about and promote any published address that matches a candidate (real, not a guess).

## `verifierActorId` (type: `string`):

Apify Store validator used for the live SMTP deliverability check. Default is a proven high-volume validator.

## `requestTimeoutSecs` (type: `integer`):

How long to wait for each company web page during the optional site scan.

## Actor input object example

```json
{
  "people": [
    {
      "firstName": "Patrick",
      "lastName": "Collison",
      "domain": "stripe.com"
    },
    {
      "firstName": "Tobi",
      "lastName": "Lutke",
      "domain": "shopify.com"
    }
  ],
  "maxCandidatesPerPerson": 6,
  "siteScan": true,
  "verifierActorId": "michael.g/email-verifier-validator",
  "requestTimeoutSecs": 20
}
```

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "people": [
        {
            "firstName": "Patrick",
            "lastName": "Collison",
            "domain": "stripe.com"
        },
        {
            "firstName": "Tobi",
            "lastName": "Lutke",
            "domain": "shopify.com"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("qualifyops/email-finder-verified").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "people": [
        {
            "firstName": "Patrick",
            "lastName": "Collison",
            "domain": "stripe.com",
        },
        {
            "firstName": "Tobi",
            "lastName": "Lutke",
            "domain": "shopify.com",
        },
    ] }

# Run the Actor and wait for it to finish
run = client.actor("qualifyops/email-finder-verified").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "people": [
    {
      "firstName": "Patrick",
      "lastName": "Collison",
      "domain": "stripe.com"
    },
    {
      "firstName": "Tobi",
      "lastName": "Lutke",
      "domain": "shopify.com"
    }
  ]
}' |
apify call qualifyops/email-finder-verified --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=qualifyops/email-finder-verified",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/acts/Oz438DncDPcCgUUJJ/builds/l3fbMVhbU5KRCfDjn/openapi.json