Work Email Finder & Verifier — RocketReach Alternative

Find and assess work emails for known people and company domains. Export provider outcomes, confidence, DNS evidence, CRM IDs, and explicit fallback states so uncertain candidates remain separate from verified results. For sales operations, work-email mode returns a dataset record for each completed known-contact check, including provider and fallback outcomes.

Workflow: put the results to work

Provide the person's full name and employer domain along with your CRM key. Inspect the provider outcome and fallback state before using any returned address. Keep MX-only candidates separate from provider-verified results so a fallback cannot silently become a deliverability claim.

Public professional-profile search

Use operation: "public_profile_search" to search public LinkedIn professional profiles by a professional query or a public LinkedIn company URL, with optional title and location filters. The route is limited to 25 complete profiles per run and does not return email, phone, private profile fields, or outreach actions. It is separately billed only when the new paid event is active; until then the Actor completes with the explicit non-billable STAGED_UNAVAILABLE outcome. An invalid activation configuration remains a real CONFIG_ERROR failure.

{
  "operation": "public_profile_search",
  "publicProfileSearch": {
    "query": "sales operations",
    "title": "Director",
    "location": "New York"
  },
  "maxProfiles": 10
}

Output: what you get

One dataset row per completed known contact:

Field	Meaning
workEmailCandidate	Provider-selected work email, or an explicitly labelled DNS-candidate fallback.
verificationStatus	Deliverability, confidence, catch-all risk, no-match, or fallback state; the exact result is preserved.
provider and providerResult	email_list_verify and its returned status whenever the verification route completes.
providerConfidence	Provider match confidence for contact discovery, when available.
fallbackUsed	true only when the requested DNS-candidate continuity policy served a provider outage.
mxHost	Domain mail-routing provenance when an MX record is available.
externalId	Your original CRM/spreadsheet key, carried through unchanged.
collectedAt	ISO timestamp for this DNS observation.

Quick start: known contacts

{
  "contacts": [{
    "externalId": "crm-001",
    "fullName": "Ada Lovelace",
    "companyName": "Example Ltd",
    "companyDomain": "example.com",
    "linkedInUrl": "https://www.linkedin.com/in/example-person"
  }],
  "enrichmentMode": "find_and_verify",
  "fallbackPolicy": "strict",
  "maxResults": 25,
  "maxCandidatesPerContact": 3,
  "includeMxValidatedCandidates": true
}

Example record shape:

{
  "externalId": "crm-001",
  "fullName": "Ada Lovelace",
  "companyDomain": "example.com",
  "workEmailCandidate": "ada.lovelace@example.com",
  "candidatePattern": null,
  "candidateRank": null,
  "verificationStatus": "deliverable_high_confidence",
  "verificationMethod": "email_list_verify",
  "provider": "email_list_verify",
  "providerConfidence": "high",
  "providerResult": "ok",
  "enrichmentMode": "find_and_verify",
  "fallbackUsed": false,
  "mxHost": "mail.example.com",
  "source": "user_provided_contact_and_dns_mx",
  "collectedAt": "<ISO-8601 collection timestamp>"
}

The example illustrates the schema only. Provider deliverability assessment is distinct from identity, employment, consent, and authorization decisions; teams can apply their own authorized review before downstream communication.

Workflow: from CRM contact to a reviewable record

A sales-operations user starts with a caller-authorized CRM export, passes fullName, companyDomain, and an externalId, then receives one typed dataset row per contact. Next, the team can review the verificationStatus, provider result, confidence, source, collection time, and fallback state before it feeds an authorized CRM hygiene workflow. The Actor keeps each input, cost event, and output record easy to audit.

Reliability and continuity

strict is the default fallback policy: a missing secret, exhausted provider credits, or provider outage produces an explicit, non-billable terminal outcome rather than a completed verification. dns_candidate is the affordable continuity route: it returns a DNS MX-backed conventional candidate with fallbackUsed: true and provider_unavailable_candidate, separate from provider verification. EmailListVerify is the primary verifier; a direct EmailListVerify API integration is the practical outside-Apify continuity route when an Apify run is unavailable. A genuinely independent verifier requires a separately contracted second provider and becomes part of the route after its API integration has been tested.

How this bounded workflow compares with RocketReach

This is an independent, focused alternative for turning an already-known name and company domain into a provider-backed work-email result, or finding bounded public professional profiles. RocketReach remains the broader choice when a hosted people/company database, phone data, browser extension, outbound sequences, team workspace, or suite-level integrations are required.

Decision	This Actor	RocketReach	Best fit
Starting point	Known name + company domain, or a bounded public professional search query	Product-managed people/company search and lookups	Use this Actor for a specific email-verification or public-profile research job.
Output	Provider result, confidence, DNS provenance, fallback state, and explicit status semantics	Broader lookup and suite data	Use RocketReach for its broader database workflow.
Effective efficiency	One complete candidate/status/provenance record for each supplied contact	No same-job timing comparison has been authorized	Compare accepted records and operator minutes for your actual workflow.
Billing	Pay per event plus platform usage; see the Pricing tab for current rates.	Subscription/credit plans; check current RocketReach pricing	Compare current prices only for the same volume and fields.
Automation	Apify dataset/API output after a batch run	Product API/integration availability depends on plan	Choose the tool whose tested integration meets your workflow.
Deliverability route	EmailListVerify result when provider mode completes; DNS fallback is explicit	Outside this Actor's contract	Use an authorized workflow for contact policy decisions.

RocketReach is a trademark of its owner. This independent Actor is not affiliated with, associated with, or endorsed by RocketReach.

API

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('khadinakbar/rocketreach-alternative').call({
  operation: 'public_profile_search',
  publicProfileSearch: { query: 'sales operations', location: 'New York' },
  maxProfiles: 3
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

AI agent and MCP prompt

Search public professional profiles for this explicit business query, without email, phone, private-profile data, or outreach. Return the run outcome, dataset readback, source, collection time, and billed event count for every complete record.

An AI agent can run this Actor through the Apify API example above. It should read OUTPUT after the dataset, use verificationStatus to distinguish provider results from DNS-candidate continuity records, and preserve externalId as the downstream join key.

Best results and scope

Provide a complete professional name and the employer's canonical mail domain for work-email enrichment. A CRM key in externalId makes the result easy to join back to the source record. Use find_and_verify for a provider-backed contact search, verify_supplied_email for a known email, and candidate_only when a DNS pattern is the appropriate scoped result. For public-profile search, provide a professional query or public LinkedIn company URL and optional title/location filters. Treat public-profile data as public research data, not proof of identity, employment, contactability, consent, or authorization.

Builder's note

I built this Actor around a deliberately inspectable contract: known business contact in, provider-backed work-email result or explicitly labelled DNS continuity record out. My goal is to make the source, collection time, provider result, fallback state, and billing event visible so a team can decide the appropriate authorized next step.

Responsible use

Use professional contact data you are authorized to process. Respect opt-outs, privacy law, platform terms, and your organization's outreach rules. Treat a candidate string, an MX record, or a profile URL as a data point within your organization’s authorized contact policy.

Pricing and run costs

This Actor uses Pay per event plus Apify platform usage. The Pricing tab lists the current event rates and billing terms.

Event	Billing unit	When it applies
verified-contact	Verified contact enrichment	One accepted EmailListVerify find/verify or supplied-email validation record; provider failures are not charged.
contact-enriched	DNS-candidate contact enrichment	One accepted DNS-candidate or continuity record; provider failures are not charged.
apify-actor-start	Actor Start	Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event).
public-profile-discovered	Public professional profile discovered	One complete public professional profile returned by the paid public-profile search after the new event becomes active. Incomplete, unavailable, and staged search paths are not charged.

Run cost combines the charged events and Apify platform usage. Review the run charge limit and requested result count before starting.

Connect an AI agent

Use the Apify MCP configurator to choose an available client connection. Inspect this Actor’s current input schema and required credentials before running it.