Relentless Identity Email Finder & Verifier Actor

Overview
Find and verify emails at scale using Relentless Identity's live identity-first verification API. This Actor helps SaaS teams, ecommerce operators, sales teams, marketers, and data teams discover likely work emails, verify existing addresses, resolve aliases, detect catch-all behavior, and identify supported corporate identity providers behind a domain.

Relentless Identity is built for modern email infrastructure where SMTP-only checks often fail. Instead of relying on stale lookup tables, it combines live provider and mailbox signals to return compact, actionable results for finder and verification workflows.

Why Relentless Identity?

1. Live Identity Verification
   Verify emails using live identity and routing signals instead of purchased databases, recycled enrichment tables, or stale cached records.
2. Finder + Probe Workflows
   Use the Finder flow to discover likely work emails for a person and company, or use Probe to verify a known email address.
3. Modern Infrastructure Coverage
   Resolve aliases, detect catch-all behavior, inspect MX hosts, and identify identity providers such as Okta, Microsoft Entra ID, Google Workspace, OneLogin, Auth0, Ping Identity, and others.

Finder vs. Probe

Tool	Endpoint	Best For	Notes
Finder	/client/attempt	Finding likely work emails from a person + company/domain input	Includes alias resolution, catch-all resolution, and multi-domain discovery for work email discovery.
Probe	/client/probe	Verifying a specific email address	Works for work and non-work emails. Alias resolution applies to work-email workflows.

Common Use Cases

• Sales & Marketing Prospecting
  Find verified work emails for decision-makers, enrich lead lists, and reduce bounce risk before outreach.
• CRM & Data Enrichment
  Fill missing work email fields and validate existing records before syncing to HubSpot, Salesforce, Clay, or custom pipelines.
• Email List Cleaning
  Use Probe to validate existing lists, including ecommerce or SaaS customer emails that may not be corporate work emails.
• Fraud, Risk & Identity Checks
  Map addresses to identity evidence, detect aliases, and understand whether an email is backed by real provider-side signals.

Automate Your Workflow

• Webhook Integration
  Push Actor results to Zapier, Make, n8n, Slack, or your CRM using Apify webhooks.
• Scheduled Verification
  Run recurring jobs to clean lead lists, refresh CRM records, or re-check high-value email addresses.
• Batch Processing
  Call the Actor repeatedly from your own workflow or queue if you need many Finder or Probe requests.

---

Input Examples

Provide either fullName + domain for Finder, or email for Probe. Mixing them is an error.

Finder Input

Use Finder when you want to discover the most likely work email for a person at a company.

{
  "fullName": "Jane Doe",
  "domain": "acme.com"
}

Probe Input

Use Probe when you already have an email address and want to verify whether it appears deliverable and identity-backed.

{
  "email": "jane.doe@acme.com"
}

---

Output Structure

Each Actor result is the Relentless Identity response returned by the backend.

Response Shape: /client/attempt (Finder)

{
  "state": "deliverable",
  "outcome": "found",
  "address": "string",
  "alternatives": ["string"],
  "is_alias": true,
  "alias": {
    "original": "string",
    "resolved": "string"
  },
  "is_catchall": true,
  "identity_providers": [
    {
      "provider": "okta",
      "hostname": "company.okta.com"
    }
  ],
  "mx_hosts": [
    "string"
  ],
  "request_id": "string"
}

Response Shape: /client/probe (Probe)

{
  "state": "deliverable",
  "outcome": "found",
  "address": "string",
  "is_alias": true,
  "alias": {
    "original": "string",
    "resolved": "string"
  },
  "is_catchall": true,
  "identity_providers": [
    {
      "provider": "okta",
      "hostname": "company.okta.com"
    }
  ],
  "mx_hosts": [
    "string"
  ],
  "request_id": "string"
}

---

Key Data Points

Field	What It Means	Use Case
state	Deliverability classification for the returned or verified address	Filter usable emails before outreach or import.
outcome	Whether the request produced a found/verified result	Route successful and unresolved records differently.
address	The discovered or verified email address	Save to CRM, enrichment table, or outreach tool.
alternatives	Additional valid identities found during Finder resolution (Finder only)	Expand outreach or retry against alternate addresses.
is_alias	Whether the email appears to be an alias	Understand whether the submitted address differs from the resolved identity.
alias.original	Original alias address	Audit alias resolution.
alias.resolved	Resolved identity-backed address	Prefer canonical or provider-backed address records.
is_catchall	Whether the domain appears to use catch-all behavior	Avoid treating SMTP acceptance alone as proof of a real inbox.
identity_providers	Detected identity provider signals	Understand the identity stack behind the domain.
mx_hosts	Mail exchanger hosts for the domain	Support deliverability, routing, and infrastructure analysis.
request_id	Unique request identifier	Debugging, support, and reconciliation.

---

FAQ

Q: What is the difference between Finder and Probe?
A: Finder uses /client/attempt to discover a likely work email from person and company/domain inputs. Probe uses /client/probe to verify a specific email address.

Q: Does Finder only work for work emails?
A: Finder is primarily designed for work email discovery.

Q: Do I need to verify addresses returned by the finder?
A: No.

Q: Can Probe verify non-work emails?
A: Yes.

Q: Does Probe perform multi-domain discovery?
A: No. Probe verifies the specific email address you submit.

Q: Does the Actor resolve aliases?
A: Yes, but alias resolution is limited to work-email workflows. Finder and work-email Probe results can return alias information through is_alias and the alias.original / alias.resolved fields.

Q: Does it work with catch-all domains?
A: Yes. Relentless Identity is designed to interpret catch-all behavior and return more precise signals than SMTP-only checks.

Q: How many free requests do I get?
A: Free-tier users pay the published list price above.

Q: Is pricing the same on Relentless Identity's own platform?
A: No. Apify free-tier users pay list price, while paid tiers use the discounted pay-as-you-go pricing.

Q: Can I use Relentless Identity outside Apify?
A: Yes. You can sign up directly on the Relentless Identity platform, start free, and use the native API or supported integrations outside Apify.

Q: Are all Relentless Identity endpoints available in this Actor?
A: No. This Actor focuses on Finder and Probe. Other endpoints, such as job scheduling endpoints, are not exposed through the Apify Actor.

Q: How fresh is the data?
A: Results are produced from live verification signals rather than stale lookup tables. Run scheduled jobs when you want to refresh a CRM, prospect list, or customer email list.

Q: What should I do with uncertain or unresolved results?
A: Keep them separate from deliverable records, retry later if appropriate, or route them into a manual review workflow depending on your risk tolerance.

---

Integration Code

Use the Apify API to run the Actor and return the dataset items directly.

curl "https://api.apify.com/v2/actors/codemaggot~relentless-identity-api/run-sync-get-dataset-items?format=json" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "email": "jane.doe@acme.com"
  }'

If you prefer the run object first, use run-sync and then fetch the run's default dataset items.

---

Learn More

• Homepage
• Documentation
• REST API Reference
• MCP Reference
• Pricing

---

Stop guessing which emails are real. Find, verify, and resolve identities with live signals.