# Email Verifier by Million Verifier - $1/1k emails (`account56/email-verifier`) Actor

✅ #1 Email Verification Service ✅ Only pay for valid and invalid emails ✅ No charge for catch all emails ✅ Easily verify emails from apollo, zoominfo etc

- **URL**: https://apify.com/account56/email-verifier.md
- **Developed by:** [Million Verifier](https://apify.com/account56) (community)
- **Categories:** Lead generation, Automation, MCP servers
- **Features:** Full permissions
- **Stats:** 18,609 total users, 2,841 monthly users, 100.0% runs succeeded, 183 bookmarks
- **User rating**: 4.46 out of 5 stars

## Pricing

from $1.00 / 1,000 email verifieds

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 Verifier by Million Verifier

✅ #1 Email Verification Service\
✅ Only pay for valid and invalid emails\
✅ No charge for catch all emails

This Apify actor verifies email addresses in bulk using the Million Verifier service. Every email is checked in seconds, you’re only billed for decisive results (valid, disposable, invalid), and responses land in the default dataset ready for download or automation.

### 💸 Pricing & Charging

- You’re billed $1 per 1,000 decisive verifications (result: `ok`, `disposable`, `invalid`).
- Catch-all, unknown, and other non-decisive outcomes are free.
- Charging happens automatically after each processing batch; the actor logs a summary at the end of the run.

### ✨ Features

- 🧹 Automatic deduplication across runs.
- 📊 Resumable stats and per-batch charging ensure accurate billing.
- 📈 Built-in dataset view for a clean, browsable summary in the Apify console.

### 📝 Input

- **emails** (required, array of strings): Email addresses you want to verify.

> Tip: You can paste a list directly into the “Emails” field in the Apify input UI—each line should contain a single address.

### ▶️ How to Run

1. Open the actor on Apify and click **Run**.
2. Paste or upload the list of emails into the `emails` field (or use the prefill to test).
3. Press **Start**. You’ll see live logs and progress in the console.
4. When the run finishes, visit the **Dataset** tab to download results as JSON, CSV, or Excel.

### 📦 Output

The actor writes each verification result to the default dataset. Results are sanitized to remove metadata fields that are not relevant for end users.

#### 🧾 Response Schema (application/json)

| Field         | Type    | Allowed values                                                                                                                                                | Description                                                                                                  |
|---------------|---------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|
| `email`       | string  | –                                                                                                                                                              | The verified email address.                                                                                  |
| `quality`     | string  | `""`, `"good"`, `"bad"`, `"risky"`                                                                                                                              | Quality assessment of the email address.                                                                     |
| `result`      | string  | `"ok"`, `"catch_all"`, `"unknown"`, `"error"`, `"disposable"`, `"invalid"`                                                                                      | Overall verification result.                                                                                 |
| `resultcode`  | integer | `1`, `2`, `3`, `4`, `5`, `6`                                                                                                                                    | Numeric verification result: `1` (ok), `2` (catch_all), `3` (unknown), `4` (error), `5` (disposable), `6` (invalid). |
| `subresult`   | string  | `"unknown"`, `"ok"`, `"internal_error"`, `"invalid_syntax"`, `"no_local_ip_available"`, `"dns_server_failed"`, `"dns_no_mx"`, `"dns_no_a"`, `"could_not_connect"`, `"no_code_in_banner"`, `"invalid_banner_code"`, `"no_code_in_ehlo_response"`, `"no_code_in_helo_response"`, `"no_code_in_mail_from_response"`, `"no_code_in_rcpt_to_response"`, `"ip_blocked"`, `"no_mailbox"`, `"mailbox_disabled"`, `"mailbox_full"`, `"greylisted"`, `"connection_lost"`, `"connection_timeout"`, `"connection_refused"`, `"connection_reset_by_peer"`, `"connection_no_route_to_host"`, `"host_not_accept_incoming_mail"`, `"mail_service_unavailable"`, `"bad_domain"`, `"dns_error"`, `"anti_spam_system"`, `"dns_no_domain"`, `"dns_refused"`, `"timeout_error"` | Detailed sub-result for diagnostic insight.                                                                  |
| `free`        | boolean | –                                                                                                                                                              | Whether the email belongs to a free email provider (e.g., Gmail).                                            |
| `role`        | boolean | –                                                                                                                                                              | `true` if the email belongs to a role-based inbox (e.g., `sales@`, `admin@`).                                |
| `didyoumean`  | string  | –                                                                                                                                                              | Suggested correction for common typos.                                                                       |
| `error`       | string  | –                                                                                                                                                              | Error message (only populated when `result` is `"error"`).                                                   |

Happy verifying! 🚀

# Actor input Schema

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

Enter the Emails of the people, you want to verify.

## Actor input object example

```json
{
  "emails": [
    "test@test.com",
    "test@gmail.com"
  ]
}
```

# 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": [
        "test@test.com",
        "test@gmail.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("account56/email-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 = { "emails": [
        "test@test.com",
        "test@gmail.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("account56/email-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 '{
  "emails": [
    "test@test.com",
    "test@gmail.com"
  ]
}' |
apify call account56/email-verifier --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,account56/email-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/VJ5w50TP6mAbyimyO/builds/65hd7pro94QewYDPa/openapi.json