# People Enrichment - Name & Company to Verified Email (`renzomacar/people-enrichment`) Actor

Turn a name + company (or an email) into a contact profile: title, seniority, department, best-available email with confidence + live MX verification. Read live from the company site, not a stale database. Pay-per-result Apollo/Clearbit alternative.

- **URL**: https://apify.com/renzomacar/people-enrichment.md
- **Developed by:** [Renzo Madueno](https://apify.com/renzomacar) (community)
- **Categories:** Lead generation, Business
- **Stats:** 4 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $20.00 / 1,000 enriched people

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/platform/actors/running/actors-in-store#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

## People Enrichment — Name & Company to Title, Seniority & Verified Email

Turn a **person's name + their company** (or just an email) into a structured contact profile — **job title, seniority, department, best-available email, and live MX verification** — read **in real time from the company's own website**, not a stale database.

Unlike database tools (Apollo, Clearbit, ZoomInfo) that serve **cached records decaying every month**, this Actor reads the company's live site, so what it returns is as fresh as the site itself — and every field is **confidence-scored** so you know what to trust.

⭐ **Works for you? [Leave a 30-second review](https://apify.com/renzomacar/people-enrichment/reviews)** — and tell me what field to add next via the **Issues** tab. It's the single biggest thing that helps other teams find this.

### What you get

One clean JSON/CSV row per person:

| Field | Example | Notes |
|---|---|---|
| `name`, `firstName`, `lastName` | "John Lincoln" | Normalized from your input |
| `title` | "Co-Founder" | Matched from the company's team/about/leadership pages |
| `seniority` | C-Level · VP · Director · Manager · Founder/Owner · Senior · Entry/IC | Classified from the title |
| `department` | Executive · Engineering · Sales · Marketing · Finance · HR/People · … | Classified from the title |
| `email` | "john@company.com" | Found on-site, or inferred from the company's email pattern |
| `emailInferred` | true / false | **Honest flag** — is the email confirmed or pattern-constructed? |
| `emailConfidence` | 0–1 | Per-email confidence |
| `emailPattern` | "first.last" | Company format, inferred only from ≥2 real emails |
| `domainHasMx` + `mxProvider` | true · "Google Workspace" | Live DNS MX lookup — is the mailbox infrastructure real? |
| `companyName`, `companyDomain`, `companyLinkedin` | "Ignite Visibility" | Company context |
| `matchedOnSite`, `matchType` | true · "site-match+real-email" | Full provenance of how we resolved the person |
| `confidenceScore` | 0–1 | Overall signal coverage |

### How do I enrich a person?

Add people, **one per line** — any of these formats works:

```
John Lincoln, ignitevisibility.com
Jane Smith @ acme.com
jane.doe@notion.so
```

Give a **name + company** to resolve the title & email, or an **email** to enrich the person and verify the domain. Then run it — one structured row per person, exportable to JSON, CSV, Excel, or your CRM.

### Output example

```json
{
  "name": "John Lincoln",
  "firstName": "John",
  "lastName": "Lincoln",
  "title": "Co-Founder",
  "seniority": "Founder/Owner",
  "department": "Executive",
  "companyName": "Ignite Visibility",
  "companyDomain": "ignitevisibility.com",
  "email": "john@ignitevisibility.com",
  "emailInferred": true,
  "emailConfidence": 0.5,
  "emailPattern": "first",
  "domainHasMx": true,
  "mxProvider": "Google Workspace",
  "matchedOnSite": true,
  "matchType": "site-match+pattern-email",
  "confidenceScore": 0.7
}
```

### Use cases

- **Lead scoring & routing** — enrich inbound leads with seniority + department to route to the right rep.
- **CRM contact enrichment** — append title, seniority, and department to existing contacts.
- **ICP filtering** — keep only decision-makers (C-Level / VP / Director) from a raw name list.
- **Org-chart & account mapping** — see who's who at a target account, live from their site.
- **Email discovery** — resolve a likely, MX-verified email for a name + company.

### Pricing

Pay-per-result — no subscription, no seat license:

| Event | Price |
|---|---|
| Actor start | $0.01 |
| Enriched person (above your confidence threshold) | $0.02 |

**You only pay for people we actually resolve** — a title, an email, or a confirmed site match above your `minConfidence`. Names we can't resolve are returned but **not charged**.

### People Enrichment vs the alternatives

| | This Actor | Apollo / Clearbit | Generic email guesser |
|---|---|---|---|
| Live read from company site (not stale DB) | ✅ | ❌ cached | ❌ |
| Title + seniority + department | ✅ | ✅ | ❌ |
| Confidence score per email | ✅ | partial | ❌ |
| Live MX verification | ✅ | partial | ❌ |
| Honest "inferred" flag on constructed emails | ✅ | ❌ | ❌ |
| No API key / no seat | ✅ | ❌ | varies |
| Pay per result | ✅ | ❌ subscription | varies |

### FAQ

**Will it always return an email?** No — and that's deliberate. Personal emails are resolved when the company publishes them or a reliable email pattern exists, and inferred emails are flagged `emailInferred: true` with a lower confidence. We never pass off a blind guess as a verified email.

**What works best?** Companies that publish a team/about/leadership page (agencies, professional services, SMBs, mid-market). Large enterprises that hide their org behind a login return company-level context only.

**Do I need an API key?** No. It runs entirely on Apify and exports anywhere.

**Is this compliant to use?** It reads only publicly published business information from a company's own website. You are responsible for lawful use under your jurisdiction.

### Other Actors by this author

Need the full company profile too? Try **[Company Enrichment API](https://apify.com/renzomacar/company-enrichment)** (domain → tech stack, firmographics & decision-makers), plus my [other Actors](https://apify.com/renzomacar) — Yahoo Finance, SEC EDGAR, and Deep Research MCP.

***

Built by [Renzo Madueño](https://apify.com/renzomacar). Found a bug or want a field added? Open an **Issue** — I read and respond to every one.

# Actor input Schema

## `people` (type: `array`):

One person per line. Formats accepted: `Jane Smith, stripe.com` · `Jane Smith @ stripe.com` · or just an email `jane@stripe.com`. Give a name + company domain to find the email, or an email to enrich the person.

## `maxPagesPerDomain` (type: `integer`):

How many pages to crawl per company (homepage + about/team/leadership/contact). More pages = better title & email matching, slightly slower.

## `minConfidence` (type: `number`):

You only pay for results: people below this confidence score (or with no resolved title/email/site match) are returned but NOT charged.

## Actor input object example

```json
{
  "people": [
    "Patrick Collison, stripe.com",
    "Dylan Field, figma.com",
    "jane.doe@notion.so"
  ],
  "maxPagesPerDomain": 5,
  "minConfidence": 0.3
}
```

# Actor output Schema

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

One row per person: matched title, seniority and department.

# 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 = {
    "people": [
        "Patrick Collison, stripe.com",
        "Dylan Field, figma.com",
        "jane.doe@notion.so"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("renzomacar/people-enrichment").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 = { "people": [
        "Patrick Collison, stripe.com",
        "Dylan Field, figma.com",
        "jane.doe@notion.so",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("renzomacar/people-enrichment").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "people": [
    "Patrick Collison, stripe.com",
    "Dylan Field, figma.com",
    "jane.doe@notion.so"
  ]
}' |
apify call renzomacar/people-enrichment --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=renzomacar/people-enrichment",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/R9J0bckwYHdhwcdd4/builds/1VuDSYu8kTylaeSdg/openapi.json