# Corporate Email Finder & Verifier (`invaluable_rondeau/corporate-email-finder-verifier`) Actor

Find likely corporate emails from a name and domain, then verify deliverability. Pay only for successfully resolved emails.

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

## Pricing

$30.00 / 1,000 resolved emails

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

## Corporate Email Finder & Verifier

B2B email discovery from a person name and company domain.
Syntax, MX, disposable-domain, and role-based signals are checked in the same run.
Results are heuristic signals for small, controlled lead-validation work—not delivery guarantees.

### Modes

#### Finder + Verifier

Provide `fullName` and preferably `domain`. The Actor generates up to five simple patterns, verifies each, and saves only the best result.

```json
{
  "fullName": "Taro Yamada",
  "domain": "example.co.jp",
  "maxCandidates": 5
}
```

#### Verifier only

Provide `emails` to verify one address per Dataset record.

```json
{
  "emails": [
    "taro.yamada@example.co.jp",
    "not-an-email"
  ]
}
```

`domain` is preferred. If it is absent, a domain-like value embedded in `companyName` can be used. The Actor does not query a company directory or LinkedIn.

### Output example

```json
{
  "inputName": "taro yamada",
  "inputDomain": "example.co.jp",
  "email": "taro.yamada@example.co.jp",
  "patternUsed": "first.last",
  "isValidSyntax": true,
  "hasMx": true,
  "isDisposable": false,
  "isRoleBased": false,
  "score": 85,
  "status": "risky",
  "checkedAt": "2026-08-05T00:00:00.000Z"
}
```

`valid` means the lightweight checks passed. `risky` means the address has a usable syntax/MX signal but also has an uncertainty or risk flag. `invalid` means syntax or MX failed. `not_found` means no usable candidate could be resolved.

### Billing

The PPE event is `email-resolved`, initially `$0.03` per event in code. Configure the matching event in Apify Console only after human approval; this repository does not publish the Actor or change production pricing.

Only a result with `status` `valid` or `risky` is billable, and charging is attempted after that result is saved to Dataset. `not_found`, `invalid`, and failed requests are not charged. The run checks `chargedCount` and stops safely when the buyer's charge limit is reached.

Dataset contains one record per Finder request or one record per supplied email. Therefore the billing reconciliation is `billableSavedCount == chargedCount`; total Dataset rows also include non-billable `invalid` and `not_found` records.

### Limits and safe use

- Candidate generation uses only five simple patterns: `first.last`, `firstlast`, `f.last`, `first_last`, and `first`.
- Names are normalized with Unicode compatibility normalization, whitespace collapsing, and lowercasing. Japanese and English names use simple token splitting; transliteration is not attempted.
- MX and a short SMTP TCP connection are signals only. The Actor does not send mail, perform `RCPT TO`, or guarantee delivery, mailbox ownership, or consent.
- Disposable and role-based lists are small built-in baselines and are not complete.
- Do not send large repeated runs or use the output for unsolicited bulk outreach. Test a small set first.
- No paid enrichment API, LinkedIn login, cookie, CRM integration, dashboard, or AI copy generation is used.

### How to use

1. Select **Try for free** in Apify.
2. Run one Finder input and one or two Verifier emails.
3. Inspect the Dataset and score/status before using any result.
4. Increase volume only after a small test is useful and the billing preview is understood.

# Actor input Schema

## `fullName` (type: `string`):

Name used to generate corporate email candidates in Finder+Verifier mode.

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

Preferred company domain, for example example.co.jp.

## `companyName` (type: `string`):

Optional fallback. Without a domain, only a domain-like value embedded in this field is used; no company directory lookup is performed.

## `maxCandidates` (type: `integer`):

Maximum generated candidates in Finder+Verifier mode.

## `emails` (type: `array`):

Optional verification-only mode. One Dataset record is produced per supplied email.

## Actor input object example

```json
{
  "maxCandidates": 5
}
```

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("invaluable_rondeau/corporate-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 = {}

# Run the Actor and wait for it to finish
run = client.actor("invaluable_rondeau/corporate-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 '{}' |
apify call invaluable_rondeau/corporate-email-finder-verifier --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,invaluable_rondeau/corporate-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/33tLyxNHFBsDRdK5k/builds/izcgVpydJIizUuNkO/openapi.json