# Verifox Email Verifier (`verifox/verifox-apify`) Actor

Verify emails in bulk with Verifox — deliverability, catch-all deep check, disposable, role & free detection plus a 0–100 quality score. No API key needed; simple flat pricing per email checked.

- **URL**: https://apify.com/verifox/verifox-apify.md
- **Developed by:** [Verifox AI](https://apify.com/verifox) (community)
- **Categories:** Lead generation
- **Stats:** 13 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: 5.00 out of 5 stars

## Pricing

from $4.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.

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

## Verifox Email Verifier ⚡

**Bulk-verify email deliverability with [Verifox](https://verifox.ai) — right inside your Apify workflows.** Drop in a list of emails (or pipe in a dataset from any scraper) and get a precise, per-email verdict: valid, reachable, disposable, role-based, free-provider, catch-all, and a **0–100 quality score**. Export to CSV, JSON, or Excel, or chain it straight into your next step.

> ✅ **No API key. No account. No setup.** Just paste your emails and run. Simple, predictable pricing — a flat rate per email checked.

***

### Why Verifox

- **Real SMTP checks**, not just syntax/MX guessing — actual mailbox reachability.
- **Catch-all deep check** — resolves accept-all Gmail/Microsoft domains to a real `safe`/`invalid` verdict instead of leaving them `risky`.
- **Disposable & role detection** so you don't ship to traps or temp-mail.
- **0–100 quality score** to rank and threshold leads at a glance.
- **Fast at scale** — realtime concurrency for small lists, a true bulk pipeline for large ones (up to 100k).
- **Reliable** — automatic retry/backoff on rate-limits and transient errors; nothing silently dropped.

### What you get per email

| Field | Meaning |
|-------|---------|
| `email` | The address checked |
| `reachable` | `safe` · `risky` · `invalid` · `unknown` — deliverability verdict |
| `isValid` | Passes syntax + MX + SMTP |
| `score` | Quality score **0–100** |
| `syntax` | Valid address format |
| `smtp` | SMTP detail: `hostExists`, `deliverable`, `catchAll`, `fullInbox`, `disabled` |
| `isDisposable` | Throwaway / temp-mail provider |
| `isRole` | Role address (`info@`, `sales@`, …) |
| `isFree` | Free provider (gmail, yahoo, …) |
| `hasGravatar` | Address has a Gravatar profile |
| `suggestion` | Typo fix (e.g. `gmial.com` → `gmail.com`), or `null` |
| `domain` · `source` · `verifiedAt` | Domain, result source, ISO timestamp |
| `ok` · `error` | `false` + reason if a single address couldn't be checked |

A **run summary** (counts by verdict) is also written to the key-value store as `OUTPUT`.

### Modes

| Mode | How it works | Best for |
|------|--------------|----------|
| **Auto** (default) | Picks per list size — bulk above 500, else realtime | Most runs |
| **Realtime** | One request per email, parallel (`concurrency`), streamed as they finish | Small/medium lists, live progress |
| **Bulk** | Submits the whole list to the Verifox bulk API, polls to completion, collects results | Large lists (up to 100k), fewest calls |

### Setup (10 seconds)

1. Paste (or map in) your list of emails.
2. Run. That's it — no API key, no account, no configuration.

### Pricing

**Pay per result: $0.004 per email checked** ($4.00 per 1,000). Predictable, list-size × rate — no platform compute charges on top.

### Input

| Field | Required | Description |
|-------|----------|-------------|
| `emails` | ✅ | List of emails (paste, or map a field from another Actor) |
| `mode` | — | `auto` (default) · `realtime` · `bulk` |
| `concurrency` | — | Parallel verifications in realtime mode, 1–20 (default 5) |
| `apiBaseUrl` | — | Advanced override; leave default |

### Example output

```json
{
  "email": "support@stripe.com",
  "reachable": "safe",
  "isValid": true,
  "score": 98,
  "syntax": true,
  "smtp": { "hostExists": true, "deliverable": true, "catchAll": false, "fullInbox": false, "disabled": false },
  "isDisposable": false,
  "isRole": true,
  "isFree": false,
  "hasGravatar": false,
  "suggestion": null,
  "domain": "stripe.com",
  "verifiedAt": "2026-07-21T12:00:00.000Z",
  "ok": true
}
```

### Use cases

- **Clean scraped leads** before importing to your CRM or outreach tool.
- **Protect sender reputation** — drop invalid/disposable/catch-all before a campaign.
- **Chain after any scraper** (LinkedIn, directories, maps) to validate captured emails.
- **Score & segment** leads by the 0–100 quality score.

### Integrate

- **Pipe from another Actor:** map its dataset's email field into this Actor's `emails` input.
- **Automate:** schedule runs, or trigger via the Apify API / webhooks and read the dataset downstream.
- **Export:** CSV / JSON / Excel from the run's dataset, or pull it via the Apify API.

### FAQ

**Do I need a Verifox account or API key?** No. Verification is fully managed — just paste emails and run.
**What does a run cost?** $0.004 per email checked ($4.00 per 1,000). Predictable up front: list size × rate.
**How big a list can it handle?** Up to 100k in bulk mode.
**What if an address can't be checked?** You still get a row with `ok: false` and the reason — nothing is dropped.

***

Powered by **[Verifox](https://verifox.ai)** — real-time email verification API. Licensed under [MIT](./LICENSE).

# Changelog

This Actor's version history is a separate document: https://apify.com/verifox/verifox-apify/changelog.md

# Actor input Schema

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

Email addresses to verify. Paste a list, or map in a field from another Actor's dataset.

## `mode` (type: `string`):

auto = pick per list size (bulk when > 500). realtime = one request per email, streamed. bulk = submit the whole list to the Verifox bulk API, then collect results.

## `concurrency` (type: `integer`):

How many emails to verify in parallel in realtime mode (1–20). Higher is faster.

## `apiBaseUrl` (type: `string`):

Override the Verifox API base URL. Leave as default unless told otherwise.

## Actor input object example

```json
{
  "emails": [
    "support@stripe.com"
  ],
  "mode": "auto",
  "concurrency": 5,
  "apiBaseUrl": "https://api.verifox.ai"
}
```

# Actor output Schema

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

Verified emails with their deliverability verdict and score.

# 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"
    ]
};

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

# Run the Actor and wait for it to finish
run = client.actor("verifox/verifox-apify").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"
  ]
}' |
apify call verifox/verifox-apify --silent --output-dataset

```

## MCP server setup

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

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/99nlx3dhL82rircNq/builds/bDiE8BlyD9UKa2doy/openapi.json