# Email Verification API — Bulk Syntax, MX & Disposable Checks (`nexgendata/email-verification-tool`) Actor

Verify email addresses in bulk: syntax validation, live MX-record checks, disposable-domain and role-account detection — strips the addresses that cause most bounces. No SMTP mailbox probe (every row says so). $0.05 per address, only delivered verdicts are charged. No API key.

- **URL**: https://apify.com/nexgendata/email-verification-tool.md
- **Developed by:** [NexGenData](https://apify.com/nexgendata) (community)
- **Categories:** Lead generation, Marketing, Developer tools
- **Features:** Limited permissions
- **Stats:** 43 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $50.00 / 1,000 email verifications

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/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 Verification API is a NexGenData tool on Apify that returns verification results with syntax, MX, disposable and role-address checks from live DNS and MX checks.

> **Same product as [Email Validator](https://apify.com/nexgendata/email-validator).** Both listings run identical code (syntax + live DNS/MX + disposable/free/role detection; no SMTP mailbox probe). Use whichever you already have configured.

## Bulk Email Validator

Email verification for a whole list: verify email addresses in bulk with syntax, MX-record, disposable and role-address checks (no SMTP mailbox probe).

Validate and clean email lists at scale — syntax, MX, disposable and role-account checks in one pass.

> You supply the addresses; the Actor validates them. Use it in line with applicable outreach and privacy law.

### 📊 Sample Output

![3 real rows delivered by Bulk Email Validator — Verify & Clean Lists API — run pMjYbZhnvamntGNeB on build 0.0.23](https://api.apify.com/v2/key-value-stores/8gLgXMBveEI1tTz1z/records/email-validator-sample)

| `email` | `status` | `isValid` | `domain` | `localPart` | `normalized` |
|---|---|---|---|---|---|
| \[email on record] | valid | True | stripe.com | support | \[email on record] |
| \[email on record] | valid | True | github.com | info | \[email on record] |
| \[email on record] | valid | True | mailinator.com | someone | \[email on record] |

Real rows from run `pMjYbZhnvamntGNeB` on build 0.0.23 (2026-09-25), unedited apart from masked emails/phones and shortened long text; fields the source does not publish are empty.

### ⚙️ Sample inputs

This is the Store example input — the same input Apify's automated check runs — so it is proven to return rows on the current build. Paste it into the input form, or send it through the API, CLI or a schedule:

```json
{
  "emails": [
    "jeff@amazon.com"
  ]
}
```

### 🔧 Input reference

| Field | Type | Default | What it does |
|---|---|---|---|
| `emails` | array of string | `["support@stripe.com", "info@github.com", "someone@mailinat…` | Email addresses to validate. Accepts either a JSON array (recommended) or a string with one email per line / comma-separated. Each address returned as a row is billed once. |
| `singleEmail` | string | `""` | Convenience field to validate a single email address |

### 🧾 JSON sample record

One real record from run `pMjYbZhnvamntGNeB` (emails/phones masked, long text shortened):

```json
{
  "email": "[email on record]",
  "status": "valid",
  "isValid": true,
  "valid": true,
  "syntaxValid": true,
  "mxValid": true,
  "hasMx": true,
  "domain": "stripe.com",
  "localPart": "support",
  "normalized": "[email on record]",
  "isDisposable": false,
  "disposable": false,
  "isFreeProvider": false,
  "isRoleAccount": true,
  "roleAccount": true,
  "deliverable": true,
  "mxRecords": [
    {
      "priority": 10,
      "server": "aspmx.l.google.com"
    },
    {
      "priority": 20,
      "server": "alt2.aspmx.l.google.com"
    },
    {
      "priority": 20,
      "server": "alt1.aspmx.l.google.com"
    },
    {
      "priority": 30,
      "server": "aspmx2.googlemail.com"
    },
    {
      "priority": 30,
      "server": "aspmx3.googlemail.com"
    }
  ]
}
```

### 💰 Pricing

| Event | Price (USD) | When it is charged |
|---|---|---|
| Actor Start (`apify-actor-start`) | $0.00005 | Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event). |
| Email validation (`apify-default-dataset-item`) | $0.05 | Charged per email address validated — checks MX records, SMTP, role-based detection, disposable domains, syntax, and deliverability scoring. |

Pay-per-event: you pay only for what the run delivers. A run that delivers nothing bills no result events (only the actor-start event, when the actor defines one). Example: a run that delivers 100 results costs 100 × $0.05 = $5.00 plus the start fee.

### 📊 What you get

Clean JSON, one record per email validated:

- `email` / `normalized` — the address, lower-cased and trimmed
- `status` — `valid` or `invalid`
- `isValid` / `valid` — the domain publishes MX records
- `syntaxValid` — RFC-shaped address
- `mxValid` / `hasMx` — MX lookup result
- `mxRecords` — up to 5 `{priority, server}` entries
- `domain` / `localPart`
- `isDisposable` / `disposable` — throwaway-mailbox domain
- `isFreeProvider` — consumer webmail domain
- `isRoleAccount` / `roleAccount` — generic mailbox (info@, sales@, support@ …)
- `deliverable` — syntax OK **and** MX present **and** not disposable
- `reason` — why an address was rejected (`invalid_syntax`, `nxdomain`, `no_mx_records`)

**Scope (honest):** validation is syntax + live DNS/MX + list checks. **No SMTP mailbox
probe is performed** — `deliverable` means the domain can accept mail, not that the
individual mailbox exists. Addresses whose DNS never answers are skipped and **not billed**;
if DNS is unreachable for every domain the run fails rather than returning filler rows.

**Pricing:** $0.050 per email validated (Pay-Per-Event) — about **20 emails per $1**.
Only delivered rows are charged.

### 🤖 Use with AI agents

Point Claude, the OpenAI Agents SDK, an n8n flow or any MCP-aware client at it and clean lists on demand.

**Agentic payments (x402):** Supports agentic payment via x402 — agents can call this actor with USDC, no API key required.

### Run it on a schedule

Run it whenever a new batch of addresses comes in, for example a daily or weekly pass over new sign-ups or freshly collected leads. What changes between runs is the list you feed in: each run returns one verdict row per address you supply. The actor has no new-only mode, so send only the addresses you have not checked yet. Send each run's results onward with a webhook, Google Sheets, Zapier, Make or the Apify API.

Video guides from Apify: [Schedule your Actor](https://www.youtube.com/watch?v=1jI7WcVQmwM) · [Integrations](https://www.youtube.com/watch?v=bNACk1_S_6w)

### FAQ

#### Why use this instead of running my own DNS and MX checks?

You could check syntax and MX records yourself. This actor does it for a whole list in one pass and adds disposable-domain, free-provider and role-account detection, with one clean JSON row per address. It needs no API key, runs from the API or on a schedule, and charges only for delivered verdicts. Addresses whose DNS never answers are skipped and not billed.

#### What does a typical run cost?

You pay per result, not for run time: $0.05 for each row in the results, plus $0.00005 per run start (charged per GB of run memory, minimum one). A run that returns 3 email addresses costs about $0.15. Live prices are always shown in the Pricing tab.

#### Does this check whether the mailbox actually exists?

No. There is no SMTP mailbox probe. `deliverable` means the syntax is fine, the domain has MX records and it is not a disposable domain. It does not mean the individual inbox exists. Every row says so: `verificationLevel` is always `syntax+dns_mx+lists` and `mailboxVerified` is always null.

#### How do I remove disposable and role-based emails from a list?

Run the list through and filter on `isDisposable` for throwaway-mailbox domains and `isRoleAccount` for generic boxes such as info@, sales@ and support@. `isFreeProvider` flags consumer webmail domains. Rejected addresses carry a `reason` such as `invalid_syntax`, `nxdomain` or `no_mx_records`.

#### What format should my email list be in?

Pass `emails` as a JSON array, or as a string with one address per line or comma-separated. For a single address, use `singleEmail`. This listing runs the same code as the Bulk Email Validator actor, so use whichever one you already have set up.

### Related actors

- [Bulk Email Validator — Verify & Clean Lists API](https://apify.com/nexgendata/email-validator) — the same product under a second listing.
- [B2B Lead List Cleaner — Dedupe, Normalize & MX-Verify API](https://apify.com/nexgendata/b2b-lead-list-cleaner) — dedupe and normalize the whole lead list, not just the email column.
- [Phone Number Validation API — Format, Carrier & Line Type](https://apify.com/nexgendata/phone-number-validator) — validate the phone column in the same list.
- [Email DMARC Auditor — SPF/DKIM/DMARC Bulk Check](https://apify.com/nexgendata/email-dmarc-auditor) — check the email security setup of the domains in your list.
- [Lead Enrichment — Enrich Leads with Emails, Phones & Tech](https://apify.com/nexgendata/lead-list-enricher) — find more contacts from company domains, then verify them here.

# Actor input Schema

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

Email addresses to validate. Accepts a JSON list (recommended) or a text string with one email per line or comma-separated (the older format still works). Each address returned as a row is billed once.

## `singleEmail` (type: `string`):

Convenience field to validate a single email address

## Actor input object example

```json
{
  "emails": [
    "support@stripe.com",
    "info@github.com",
    "someone@mailinator.com"
  ],
  "singleEmail": ""
}
```

# Actor output Schema

## `results` (type: `string`):

Default dataset of Email Verification API — Bulk Syntax, MX & Disposable Checks records (19 fields per row: email, status, isValid, valid, syntaxValid, mxValid, hasMx, domain, localPart, normalized, isDisposable, disposable…).

# 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 = {
    "emails": [
        "support@stripe.com",
        "info@github.com",
        "someone@mailinator.com"
    ],
    "singleEmail": ""
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgendata/email-verification-tool").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 = {
    "emails": [
        "support@stripe.com",
        "info@github.com",
        "someone@mailinator.com",
    ],
    "singleEmail": "",
}

# Run the Actor and wait for it to finish
run = client.actor("nexgendata/email-verification-tool").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 '{
  "emails": [
    "support@stripe.com",
    "info@github.com",
    "someone@mailinator.com"
  ],
  "singleEmail": ""
}' |
apify call nexgendata/email-verification-tool --silent --output-dataset

```

## MCP server setup

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

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/DTgFaAOv0V6JgWdLK/builds/b0e0WU7lepiirfFUA/openapi.json