# B2B Email Deliverability Risk Gate (`invaluable_rondeau/b2b-email-deliverability-risk-gate`) Actor

Pre-send B2B email list hygiene gate returning allow, review, or suppress decisions using syntax, MX, disposable-domain, role-account, and free-provider signals.

- **URL**: https://apify.com/invaluable_rondeau/b2b-email-deliverability-risk-gate.md
- **Developed by:** [PROOFNEXA](https://apify.com/invaluable_rondeau) (community)
- **Categories:** Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$10.00 / 1,000 email risk decision scoreds

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

## B2B Email Deliverability Risk Gate

Run a read-only pre-send hygiene check on a B2B email list. The Actor returns one structured Dataset row per unique input address with a score, reason codes, and an operational decision:

- `allow`: syntax and MX passed, with no local high-risk flag.
- `review`: a human should review a role account, free provider, or unresolved MX lookup.
- `suppress`: malformed address, disposable domain, or no MX record.

This is a **risk gate**, not a mailbox-existence or delivery guarantee. It uses syntax checks, a small explicit disposable-domain list, a small role-prefix list, a small free-provider list, and DNS MX lookup (cached per domain). It does not send email, use SMTP `RCPT TO`, scrape websites, use proxies, access private data, or require an API key.

> **Companion B2B Email & Domain Tools:**
>
> - Need to discover corporate emails from a person's name + company domain? Use **[Corporate Email Finder & Verifier (`invaluable_rondeau/corporate-email-finder-verifier`)](https://apify.com/invaluable_rondeau/corporate-email-finder-verifier)**.
> - Need high-volume MX verification up to 50,000 emails at `$0.001`/email? Use **[Bulk Email Verifier (`invaluable_rondeau/email-verifier-bulk`)](https://apify.com/invaluable_rondeau/email-verifier-bulk)**.
> - Need SPF / DMARC / DKIM / MX provider security auditing across domains? Use **[B2B Domain Email Security & Deliverability Auditor (`invaluable_rondeau/b2b-domain-email-security-auditor`)](https://apify.com/invaluable_rondeau/b2b-domain-email-security-auditor)**.

### Input

```json
{
  "emails": [
    "person@company.com",
    "support@gmail.com",
    "alerts@mailinator.com",
    "not-an-email"
  ],
  "timeoutMs": 1500
}
```

`emails` accepts an array or a comma/newline-delimited string through the API. Up to 1,000 unique addresses are accepted per run. Case-insensitive duplicates are emitted once and are not processed twice.

### Output

Each row includes `email`, `normalized`, `domain`, `isValidSyntax`, `hasMx`, `isDisposable`, `isRoleBased`, `isFreeProvider`, `score`, `decision`, `reasonCodes`, `sourceChecks`, `checkStatus`, and `checkedAt`.

`score` is a pre-send quality signal, not a probability. `checkStatus: partial` means DNS could not be resolved in time; that row is returned as `review`, not as a clean pass.

### Pricing

The pay-per-event price is **$0.01 per saved risk decision** (`email-risk-scored`). A 1,000-address run is at most $10 before any account-level maximum-charge setting. Duplicate inputs are collapsed before processing. A Dataset row is saved before the charge is attempted. Failed processing is not charged.

Example: 10,000 scored addresses = approximately $100 in Actor charges.

### Quick start

1. Run 10–100 addresses first and inspect the Dataset.
2. Keep `review` rows out of automated sending until a human or downstream policy decides.
3. For recurring hygiene, create an Apify Schedule for the same list and inspect the new Dataset after each run.

### Privacy and safety

Only provide addresses you are authorized to process. The Actor does not enrich, discover, or send to addresses. It stores the input address and derived DNS/list signals in the Dataset so you can audit the decision. The built-in lists are intentionally small and are not complete.

***

### AI Agent (MCP) & Automation Integration (Claude, Cursor, n8n, Clay, Make)

This Actor is **Agentic-Payment & MCP Ready** (`LIMITED_PERMISSIONS`, `256 MB` fast cold-start, synchronous JSON output).

#### 1. Claude Desktop / Cursor / Windsurf MCP Configuration

Add to `claude_desktop_config.json` or `.cursor/mcp.json`:

```json
{
  "mcpServers": {
    "apify-b2b-quant": {
      "command": "npx",
      "args": [
        "-y",
        "@apify/actors-mcp-server",
        "--actors",
        "invaluable_rondeau/b2b-email-deliverability-risk-gate"
      ],
      "env": {
        "APIFY_TOKEN": "YOUR_APIFY_TOKEN"
      }
    }
  }
}
```

#### 2. Synchronous HTTP Webhook (n8n, Make, Clay, Zapier, cURL)

Call the synchronous dataset endpoint to get clean JSON items in a single HTTP request:

```bash
curl -X POST "https://api.apify.com/v2/acts/invaluable_rondeau~b2b-email-deliverability-risk-gate/run-sync-get-dataset-items?token=$APIFY_TOKEN&memory=256&clean=true" \
  -H "Content-Type: application/json" \
  -d '{}'
```

#### 3. Search Keywords & Supported Workflows

Compatible with **Model Context Protocol (MCP)**, **Clay.com HTTP API enrichment**, **n8n HTTP Request node**, **Make.com**, **Zapier**, **LangChain**, and **OpenAI Agent SDK**. Built as a high-margin, pay-per-event alternative to rigid monthly SaaS subscriptions (ZeroBounce, NeverBounce, MillionVerifier, Bouncer alternative for cold email hygiene, disposable email and catch-all risk scoring).

# Actor input Schema

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

Email addresses to classify. A CSV/newline/comma-delimited string is also accepted through the API.

## `timeoutMs` (type: `integer`):

Timeout for each MX lookup. The Actor never opens an SMTP connection.

## Actor input object example

```json
{
  "emails": [
    "satya.nadella@microsoft.com",
    "support@apify.com",
    "alerts@mailinator.com"
  ],
  "timeoutMs": 1500
}
```

# Actor output Schema

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

No description

# 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": [
        "satya.nadella@microsoft.com",
        "support@apify.com",
        "alerts@mailinator.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("invaluable_rondeau/b2b-email-deliverability-risk-gate").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": [
        "satya.nadella@microsoft.com",
        "support@apify.com",
        "alerts@mailinator.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("invaluable_rondeau/b2b-email-deliverability-risk-gate").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": [
    "satya.nadella@microsoft.com",
    "support@apify.com",
    "alerts@mailinator.com"
  ]
}' |
apify call invaluable_rondeau/b2b-email-deliverability-risk-gate --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,invaluable_rondeau/b2b-email-deliverability-risk-gate"
        }
    }
}
```

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/PKhFx1uranbPF7726/builds/mjwxLNMSxfLw6OcoA/openapi.json