> ## Documentation Index
> Fetch the complete documentation index at: https://docs.enricho.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Email Intelligence

> Five checks on any email address: may you cold email it, does it work, who owns it, gender and data breaches. 1 credit per answer.

Paste a list of email addresses and pick the checks you need. Enricho tells you who is behind each address, whether the mailbox works, whether a cold email to them is allowed under the recipient's law, and more. One request covers up to 100 checks.

> Check these 40 signups: are they real addresses, who are they, and can I cold email them?

> [card] [In Enricho Chat](https://docs.enricho.co/chat.md#pick-a-product)
>
> Pick **Email Intelligence** in the prompt bar and paste addresses. You approve the cost first.

> [card] [With the API](https://docs.enricho.co/api-reference/email-intelligence.md)
>
> `POST /api/directory/email/intelligence` with `emails` and `checks`.

> [!NOTE]
>
> Email Intelligence is available in [Enricho Chat](https://docs.enricho.co/chat.md), your AI assistant over [MCP](https://docs.enricho.co/connect.md) (the `email_intelligence` tool) and the [REST API](https://docs.enricho.co/api-reference/email-intelligence.md). There's no free preview, so your assistant should tell you the cost and ask before running it.

## The five checks

Run only the checks you need. Each one is charged separately, and only when it has an answer.

> [card] [Compliance](https://docs.enricho.co/intelligence/email-compliance.md)
>
> **Can I cold email them?** Finds the recipient's country and returns the verdict under its law (`allowed`, `consent_required`, `do_not_send`), with the conditions you must meet and any exceptions. 71 countries covered.

> [card] Validity
>
> **Does it receive mail?** Asks the mail server whether the mailbox exists, without sending anything. Also flags catch-all domains, throwaway inboxes and shared inboxes like `info@`, with a 0–100 confidence score.

> [card] Identity
>
> **Who owns it?** The person's name, job title, seniority, LinkedIn and location, and their company's industry, size and head office. Add `deep_identity` to look further when Enricho's records don't know them.

> [card] Gender
>
> **How should I address them?** From the person's record when Enricho holds it, otherwise inferred from the first name in the address, with a probability.

> [card] Breaches
>
> **Has it leaked?** The public data breaches the address appears in: the service, the date and what data was exposed. Sensitive breaches are never included.

### Which check answers your question

| You want to know | Checks |
| - | - |
| Is this list safe to send a campaign to? | `validity`, `compliance` |
| Who signed up for my product? | `identity` |
| Is this lead worth a sales call? | `identity`, `validity` |
| How do I open the email? (*Dear Ms…*) | `gender` |
| Is this account at risk of takeover? | `breaches` |
| Everything | all five (up to 20 addresses per request) |

## Try it

```bash cURL theme={null}
curl -X POST 'https://api.enricho.co/api/directory/email/intelligence' \
  -H 'Authorization: Bearer enr_YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
    "emails": ["anna.schmidt@northwind.example", "info@lumen.example"],
    "checks": ["compliance", "validity", "identity"]
  }'
```

```javascript JavaScript theme={null}
const res = await fetch("https://api.enricho.co/api/directory/email/intelligence", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.ENRICHO_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    emails: ["anna.schmidt@northwind.example", "info@lumen.example"],
    checks: ["compliance", "validity", "identity"],
  }),
})
const { result } = await res.json()
for (const r of result.results) {
  console.log(r.email, r.validity?.status, r.compliance?.verdict, r.identity?.full_name)
}
```

```python Python theme={null}
import os, requests

res = requests.post(
    "https://api.enricho.co/api/directory/email/intelligence",
    headers={"Authorization": f"Bearer {os.environ['ENRICHO_API_KEY']}"},
    json={
        "emails": ["anna.schmidt@northwind.example", "info@lumen.example"],
        "checks": ["compliance", "validity", "identity"],
    },
    timeout=120,
)
res.raise_for_status()
for r in res.json()["result"]["results"]:
    print(r["email"], r.get("validity", {}).get("status"), r.get("compliance", {}).get("verdict"))
```

Each address comes back with one section per check you asked for. A shortened result for the first address:

```json theme={null}
{
  "email": "anna.schmidt@northwind.example",
  "valid": true,
  "validity": {
    "status": "valid",
    "reason": "The mailbox exists and accepts mail.",
    "mailbox": "deliverable",
    "score": 95,
    "catch_all": false,
    "disposable": false,
    "role_address": false,
    "free_provider": false
  },
  "compliance": {
    "recipient_type": "business",
    "country_code": "XX",
    "country_source": "person_record",
    "country_confidence": "high",
    "verdict": "allowed",
    "reason": "Cold email to business addresses in XX is allowed if you meet the conditions.",
    "conditions": ["Identify the sender clearly.", "Give a free, easy way to unsubscribe in every message."],
    "exceptions": []
  },
  "identity": {
    "found": true,
    "match": "email",
    "full_name": "Anna Schmidt",
    "job_title": "Head of Marketing",
    "seniority": "head",
    "company": { "name": "Northwind", "domain": "northwind.example", "industry": "software", "employee_size_band": "51-200" }
  }
}
```

The full response, with every field, is in the [API reference](https://docs.enricho.co/api-reference/email-intelligence.md).

## Reading the results

* **`valid: false`** means the address is malformed: `reason` says why. Its checks are skipped and free.
* **Validity `status`** is the verdict to act on: `valid` (send), `risky` (catch-all domain, throwaway or shared inbox: send with care), `invalid` (remove), `unknown` (the mail server didn't say: free, try later).
* **Identity `match`** is `email` when Enricho's record holds this exact address, or `name_at_company` when someone with the name in the address (`anna.schmidt@`) works at the domain's company. Treat `name_at_company` as a likely match, not a confirmed owner.
* **Compliance `country_confidence`** tells you how the country was found: `high` from the person's own record, `medium` from a name match or the company's head office, `low` from the domain ending. See [how compliance works](https://docs.enricho.co/intelligence/email-compliance.md).
* **Breaches `status: "unavailable"`** means the lookup didn't answer in time. It isn't charged; run it again later.

## Deep identity

When Enricho's records don't know who owns an address, set `"deep_identity": true` to look the address up in a wider people database.

* It runs only for addresses the normal identity check couldn't answer, and never for shared (`info@`) or throwaway inboxes.
* A person found this way comes back with `deep_lookup: true` and richer detail: headline, departments, work history and social links.
* It costs **5 credits** per person found, instead of 1. Nothing is charged when nobody is found.

In Enricho Chat, the assistant offers a deeper lookup when an identity check finds nobody, and runs it only if you say yes.

## Credits

| What | Cost |
| - | - |
| Each check with an answer, per address | 1 credit (\$0.02) |
| An identity found by deep identity | 5 credits (\$0.10) |
| Unknown gender or country, identity with nobody found, breaches unavailable, validity `unknown` | Free |
| Malformed addresses | Free |
| The same check on the same address within a year | Free (counted in `already_purchased`) |

Twenty addresses with `validity` and `compliance` cost at most 40 credits. If your balance can't cover the whole request, nothing runs and nothing is charged (`402`).

## Limits and good practice

* **Up to 100 checks per request**, counting addresses × checks: 100 addresses with one check, or 20 with all five. Split bigger lists; see the [batching recipe](https://docs.enricho.co/api-reference/recipes.md#clean-a-list-before-a-campaign).
* Addresses are lowercased, trimmed and de-duplicated, keeping your order.
* A large request can take a minute or more while mail servers answer. Set your HTTP timeout to at least 120 seconds.
* Compliance is a summary of each country's rules, not legal advice. Check with counsel before relying on a verdict.
* Gender inference from a name is a guess. Use it for greetings, never to decide who to contact or hire.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.