# Email Finder & Verifier - B2B Email Lookup API (`haketa/email-finder-verifier`) Actor

Find a person's business email from their name and company domain and verify it in one call: best candidate ranked by format frequency or a learned company pattern, plus MX, syntax, disposable/role/free flags and a 0-100 deliverability score. Keyless, DNS-based, fast at scale.

- **URL**: https://apify.com/haketa/email-finder-verifier.md
- **Developed by:** [Haketa](https://apify.com/haketa) (community)
- **Categories:** Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Email Finder & Verifier — B2B Email Lookup API ✉️

Give a person's **name + company domain** and get their most likely **business email — already verified**. For every lookup you get the best email candidate (ranked by real-world format frequency, or a company's exact pattern learned from a known sample) plus a full verification block.

No API key, no login. DNS-based, fast and cheap at scale.

### What you get (per person)

- **email** — the most likely business email
- **confidence** (0-100) + **confidenceLabel** (low/medium/high) + **status** (likely / uncertain / risky / undeliverable / invalid)
- **deliverabilityScore** (0-100)
- **hasMx** / **mxHost** — does the domain accept mail?
- **isFreeProvider**, **isRoleBased**, **isDisposable**, **syntaxValid**
- **pattern** (first.last, flast…) + **method** (statistical / pattern-learned)
- **alternatives** — other likely formats

### Use cases

- **B2B lead generation** — turn a list of names + companies into verified work emails.
- **Sales / recruiting outreach** — find decision-makers' emails at scale.
- **CRM enrichment** — fill missing emails and flag risky/undeliverable ones.
- **Hunter / RocketReach alternative** — same lookup, no per-lookup API fees.

### Input

| Field | Type | Description |
|-------|------|-------------|
| `people` | array | `Full Name, domain.com` per line, or `{fullName, domain}` objects. |
| `domain` | string | Global company domain for lines without one (many people at one company). |
| `knownEmails` | array | Known `Name, email@company.com` samples → learns the company's exact pattern (high confidence). |
| `includeAllCandidates` | boolean | Also return alternative formats. |
| `maxConcurrency` | integer | Parallel lookups. |

#### Example input

```json
{
  "people": ["Tim Cook, apple.com", "Satya Nadella, microsoft.com"],
  "knownEmails": ["Jeff Williams, jeff.williams@apple.com"]
}
```

### Output (example)

```json
{
  "fullName": "Tim Cook", "firstName": "Tim", "lastName": "Cook",
  "domain": "apple.com", "company": "apple",
  "email": "tim.cook@apple.com",
  "confidence": 92, "confidenceLabel": "high", "status": "likely",
  "deliverabilityScore": 100, "hasMx": true, "mxHost": "…",
  "isFreeProvider": false, "isRoleBased": false, "isDisposable": false, "syntaxValid": true,
  "pattern": "first.last", "method": "pattern-learned",
  "alternatives": ["tcook@apple.com", "timcook@apple.com", "t.cook@apple.com"],
  "scrapedAt": "2026-10-17T12:00:00.000Z"
}
```

### How it works

For each person the actor generates candidate emails from their name using the most common business formats (and, if you supply a known sample, the company's exact learned pattern), then verifies: syntax, MX (does the domain accept mail?), disposable/role/free flags, and a deliverability score. It does **not** probe mailboxes over SMTP (port 25 is blocked on clouds and unreliable) — it verifies everything that can be verified without it and scores each result honestly.

### Legal & ethical use

Generates/verifies business email addresses from public naming conventions. Use responsibly and in compliance with GDPR/CCPA and anti-spam laws (lawful basis, opt-out). You are responsible for how you use the output.

# Actor input Schema

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

One per line: <b>Full Name, domain.com</b> (e.g. <b>Tim Cook, apple.com</b>). Or objects <code>{"fullName":"Tim Cook","domain":"apple.com"}</code>. If a line has no domain, the global <b>Company domain</b> below is used.

## `domain` (type: `string`):

Default company domain applied to any person line that doesn't include one. Handy when looking up many people at one company.

## `knownEmails` (type: `array`):

Optional. One known person+email per line (e.g. <b>Jane Doe, jane.doe@acme.com</b>) — the actor learns that company's exact format and applies it with high confidence.

## `includeAllCandidates` (type: `boolean`):

Also return other likely email formats per person.

## `maxConcurrency` (type: `integer`):

How many lookups to run in parallel.

## Actor input object example

```json
{
  "people": [
    "Tim Cook, apple.com",
    "Satya Nadella, microsoft.com"
  ],
  "knownEmails": [],
  "includeAllCandidates": true,
  "maxConcurrency": 50
}
```

# Actor output Schema

## `emails` (type: `string`):

Found + verified business emails.

# 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": [
        "Tim Cook, apple.com",
        "Satya Nadella, microsoft.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("haketa/email-finder-verifier").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": [
        "Tim Cook, apple.com",
        "Satya Nadella, microsoft.com",
    ] }

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

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).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": [
    "Tim Cook, apple.com",
    "Satya Nadella, microsoft.com"
  ]
}' |
apify call haketa/email-finder-verifier --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,haketa/email-finder-verifier"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/pfQdR727N5fVh85CM/builds/xE5cdbdrhHbIAMM3g/openapi.json