Email Finder & Verifier API — Find Verified B2B Emails

Email Finder + Verifier — Name & Domain → Deliverable Email

You give: a person's name and their company domain — e.g. Patrick Collison + stripe.com. You get: their verified, deliverable email address — one confirmed mailbox, with a confidence score, marked FOUND or NOT_FOUND. You pay: only per verified email found — $0.008. Not-found is free.

No LinkedIn, no scraping of protected sources. This is a deterministic pattern engine plus live deliverability verification — the two things that actually turn a name into an address you can send to.

---

Why "verified" is the whole point

Most email finders hand you first.last@company.com and call it a day. You send, it bounces, and your domain reputation takes the hit. Here, every FOUND address has been through:

pattern generation → syntax → MX record → live SMTP mailbox check → catch-all detection → confidence score

Only an address that a real mail server accepts, that is not catch-all, at confidence ≥ 0.80, is returned as FOUND. Everything else is NOT_FOUND with a reason and a clearly-labelled best_guess — never a silent, billed guess.

How it works

1. Normalize the name (lowercase, strip accents/punctuation) and the domain (strip https://, www., paths — full URLs are fine).
2. Generate candidates in priority order: first.last, first, flast, firstlast, first_last, f.last, last.first, lastf, first-last, last — each @domain.
3. Optional site scan (siteScan, on by default): fetch the company's homepage, /contact and /about and promote any published address that matches a candidate to the front — those are real, not guesses.
4. Local pre-filter (free): drop bad-syntax candidates and, if the domain has no MX record at all, return NOT_FOUND immediately — with no charge.
5. One batched deliverability check: survivors go to a proven Apify Store validator with real SMTP egress, in a single call per run.
6. Pick the winner: the first deliverable, non-catch-all, confident address becomes FOUND. You are charged only for FOUND.

What each row gives you

Column	Meaning
action	FOUND (verified deliverable) or NOT_FOUND (with reason)
firstName / lastName	The person you asked about
domain	The normalized company domain
verified_email	The deliverable address — only on FOUND
pattern	Which pattern won (first.last, flast, published, …)
confidence	0–1 deliverability confidence
source	pattern (generated) or published (found on the company site)
candidates_checked	How many addresses were tested
reason	On NOT_FOUND: catch_all_domain / all_rejected / no_mx / verifier_unavailable
best_guess / best_guess_confidence	On NOT_FOUND: the most-likely address, clearly not verified

Honest by design

• We never invent an address and label it verified. FOUND means a live mail server accepted that specific mailbox.
• Catch-all domains — which accept everything and confirm nothing — are returned as NOT_FOUND (catch_all_domain) and are not charged. We will not bill you for a domain that cannot actually confirm the person.
• If the verifier is unavailable, we degrade to NOT_FOUND (verifier_unavailable) — never a fabricated "deliverable" result, never a charge.
• A best_guess is always presented as a guess, never as a verified address.

For agents & automation

Call it via the Apify API or MCP. Pass an array of {firstName, lastName, domain} (or {fullName, domain}) and get back deduped, verified rows — ideal as a step in an enrichment pipeline. Schedule it for recurring enrichment of a lead list into your CRM or sequencer. You pay only for the addresses that are actually deliverable.

---

Input: people (array of name + domain). Optional: maxCandidatesPerPerson (cost cap), siteScan, verifierActorId, requestTimeoutSecs.