# Contact Enricher (`roseapps/contact-enricher`) Actor

Crawls a company's website to extract emails, phones, socials, address and tech hints, infers the company email pattern, and optionally verifies emails via MX/catch-all checks.

- **URL**: https://apify.com/roseapps/contact-enricher.md
- **Developed by:** [Elliot Rose](https://apify.com/roseapps) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 1 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 domain enricheds

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?

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

## Contact Enricher

Given a list of company domains or URLs, crawls a handful of high-signal
pages per site (home, contact, about, team, footer links, JSON-LD), extracts
emails, phones, socials, address, company name and tech hints, infers the
company's email pattern (e.g. `{first}.{last}`), optionally verifies emails
via MX lookup + catch-all detection, and emits **one normalised record per
domain**.

### Input

| Field | Type | Default | Description |
|---|---|---|---|
| `domains` | string\[] | *(required)* | Domains or URLs to enrich, e.g. `"acme.com"` or `"https://www.acme.com"`. `urls` is accepted as an alias. |
| `maxPagesPerSite` | integer | `8` | Max pages crawled per domain (home + up to `maxPagesPerSite - 1` internal links). |
| `verifyEmails` | boolean | `true` | Run MX + catch-all checks on every extracted/guessed email. |
| `wantPersonNames` | boolean | `false` | Include named individuals found on the site and generate up to 10 pattern-guessed personal emails. Off by default — business contact data only, per policy. |
| `verifierProvider` | string | *(none)* | Optional third-party verifier API name (see `src/verify.py` adapter). |
| `verifierApiKey` | string | *(none)* | API key for the third-party verifier, if used. |
| `maxConcurrency` | integer | `5` | Domains processed in parallel. |

### Output (one dataset row per domain)

```json
{
  "domain": "acme.com",
  "company_name": "Acme Corp",
  "emails": [
    {
      "value": "info@acme.com",
      "type": "generic",
      "source": "observed",
      "off_domain": false,
      "mx_ok": true,
      "smtp_status": "unknown",
      "confidence": 0.9
    },
    {
      "value": "jane.doe@acme.com",
      "type": "named",
      "source": "observed",
      "off_domain": false,
      "mx_ok": true,
      "smtp_status": "unknown",
      "confidence": 0.9
    },
    {
      "value": "john.smith@acme.com",
      "type": "named",
      "source": "pattern",
      "off_domain": false,
      "mx_ok": true,
      "smtp_status": "unknown",
      "confidence": 0.6
    }
  ],
  "email_pattern": "{first}.{last}",
  "phones": ["+15551234567"],
  "socials": { "linkedin": "https://linkedin.com/company/acme" },
  "address": "123 Main St, Springfield, IL, 62704, US",
  "tech_hints": { "cms": "wordpress", "analytics": "google-analytics" },
  "pages_crawled": 5,
  "source_urls": [
    "https://acme.com/",
    "https://acme.com/contact",
    "https://acme.com/about",
    "https://acme.com/team"
  ],
  "fetched_at": "2026-08-29T12:00:00+00:00"
}
```

A failed domain produces `{"domain": "...", "error": "..."}` instead, and is
never charged.

When `wantPersonNames` is `true`, a `person_names` array is also included.

### Pricing events (pay-per-event)

| Event | Suggested price | When |
|---|---|---|
| `domain-enriched` | $0.002 | Once per successfully processed domain (one dataset row). |
| `email-verified` | $0.004 | Per email that went through `verify_email` (only when `verifyEmails` is `true`). |

Failed domains are never charged.

### MCP

Exposed as an MCP tool `enrich_company(domain)`, which maps to running this
Actor with `domains: [domain]` and default options, returning the single
resulting record.

### Limitations

- **JS-only sites**: the crawler is a plain HTTP client (httpx) with no
  headless browser — content injected client-side by JavaScript frameworks
  won't be seen.
- **SMTP probing is often blocked**: outbound port 25 is frequently blocked
  from datacenter/cloud IPs, so catch-all detection and per-mailbox checks
  regularly come back inconclusive. In that case `smtp_status` is
  `"unknown"` (still usable — `mx_ok` and `confidence` are still populated
  from the MX lookup).
- Only business contact data is emitted by default; named individuals and
  pattern-guessed personal emails require the explicit `wantPersonNames`
  flag.
- Email-pattern inference and address/company-name selection are heuristic,
  not guaranteed correct — always treat guessed (`source: "pattern"`) emails
  as lower confidence than observed ones.

# Actor input Schema

## `domains` (type: `array`):

Company domains or URLs to enrich, e.g. "acme.com" or "https://www.acme.com".

## `maxPagesPerSite` (type: `integer`):

Maximum number of pages to crawl per domain (home page + high-signal internal links).

## `verifyEmails` (type: `boolean`):

Check MX records and probe for catch-all domains for every extracted/guessed email.

## `wantPersonNames` (type: `boolean`):

Include named individuals found on the site and generate pattern-guessed personal emails (max 10 per site). Off by default: business contact data only.

## `verifierProvider` (type: `string`):

Optional: name of a third-party email verification API to call instead of/alongside the built-in MX + catch-all check (e.g. "generic").

## `verifierApiKey` (type: `string`):

Optional API key for the third-party verifier provider above.

## `maxConcurrency` (type: `integer`):

Maximum number of domains processed in parallel.

## Actor input object example

```json
{
  "domains": [
    "mailchimp.com"
  ],
  "maxPagesPerSite": 8,
  "verifyEmails": true,
  "wantPersonNames": false,
  "maxConcurrency": 5
}
```

# 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 = {
    "domains": [
        "mailchimp.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("roseapps/contact-enricher").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 = { "domains": ["mailchimp.com"] }

# Run the Actor and wait for it to finish
run = client.actor("roseapps/contact-enricher").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 '{
  "domains": [
    "mailchimp.com"
  ]
}' |
apify call roseapps/contact-enricher --silent --output-dataset

```

## MCP server setup

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

```

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/4flTgD6IaaBWmwna3/builds/e2VaqdtE9RzxHZK1j/openapi.json