# B2B Local Business Contact & Email Resolver (`devilx-tools/b2b-contact-resolver`) Actor

Fast, verified contact and mailto resolver for local service businesses (Dental, Medspa, Home Remodeling).

- **URL**: https://apify.com/devilx-tools/b2b-contact-resolver.md
- **Developed by:** [sam world](https://apify.com/devilx-tools) (community)
- **Categories:** Lead generation
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$30.00 / 1,000 resolved leads

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

## 🎯 B2B Local Business Contact & Email Resolver

Extract, verify, and resolve rich B2B contact details — valid business emails, phone numbers, and contact-form signals — directly from company websites and domains. Fast, GET-only crawling. No API keys, no scraping blockers, no fluff.

> 💡 **Zero-Risk Pay-Per-Result Pricing:**
> Platform compute is 100% FREE. You only pay **$0.03 per successfully resolved lead**. If no contact is found, you are charged **$0.00**.

***

### ⚡ Why Use This Actor?

- **Pure Pay-Per-Result:** Never pay for failed lookups or idle server compute time. You only pay when actual value is delivered.
- **Direct Business Emails:** Finds active corporate and contact emails (mailto links and on-page addresses) with confidence scoring.
- **Deep Contact Enrichment:** Resolves phone numbers, detects contact forms, and returns every email candidate found — ranked, deduped, and source-tagged.
- **Cold Outreach Ready:** Export results directly in JSON, CSV, or Excel via the Apify API, formatted for instant import into tools like Instantly, Smartlead, or HubSpot.

***

### 📥 Input Format

Pass a list of business domains (optionally full URLs — they are normalized automatically):

```json
{
  "domains": [
    "stripe.com",
    "https://example-bakery.com",
    "gilbertdentalcenter.com"
  ],
  "allowFreemail": true
}
```

| Field | Type | Default | Description |
|---|---|---|---|
| `domains` | array | **required** | Business domains or website URLs to resolve |
| `paths` | array | `["", "/contact", "/contact-us", "/about", "/about-us"]` | URL paths crawled per domain |
| `allowFreemail` | boolean | `true` | Include gmail/yahoo etc. as valid business emails |

***

### 📤 Output Format

One dataset item per domain:

```json
{
  "domain": "gilbertdentalcenter.com",
  "email": "info@gilbertdentalcenter.com",
  "confidence": 1.0,
  "source": "mailto",
  "phone": "+1 480-555-0123",
  "has_contact_form": false,
  "status": "resolved",
  "all_candidates": [
    { "email": "info@gilbertdentalcenter.com", "source": "mailto", "freemail": false, "confidence": 1.0 }
  ]
}
```

`status` is `resolved` (email found — **only these are billed**) or `not_found` (billed $0.00).

***

### 💰 Pricing

| Item | Price |
|---|---|
| Platform compute | **$0.00 — always free** |
| Per resolved lead (email found) | **$0.03** |
| Not-found / failed lookups | **$0.00** |

A 100-domain run that resolves 40 leads costs **$1.20**, not 100 events.

***

### 🚀 Quick Start

```bash
apify run -p -i '{"domains":["example.com"],"allowFreemail":false}'
```

Or use the Apify API:

```
POST https://api.apify.com/v2/acts/devilx-tools~b2b-contact-resolver/runs
{ "domains": ["acme.com", "widgets.io"] }
```

Fetch results from the run's dataset — JSON, CSV, Excel and HTML export supported.

# Actor input Schema

## `domains` (type: `array`):

Domains to crawl for contacts

## `paths` (type: `array`):

Fixed URL paths fetched per domain for contact info.

## `allowFreemail` (type: `boolean`):

If false, gmail/yahoo/outlook addresses are dropped.

## Actor input object example

```json
{
  "paths": [
    "",
    "/contact",
    "/contact-us",
    "/about",
    "/about-us"
  ],
  "allowFreemail": true
}
```

# Actor output Schema

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

Default dataset items: domain, email, phone, confidence, status, source.

## `dataset` (type: `string`):

Console view of the default dataset with the table of resolved contacts.

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("devilx-tools/b2b-contact-resolver").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("devilx-tools/b2b-contact-resolver").call(run_input=run_input)

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

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

```

## CLI example

```bash
echo '{}' |
apify call devilx-tools/b2b-contact-resolver --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,devilx-tools/b2b-contact-resolver"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/UNykBrBv08vmWJ1AH/builds/SwuxMxCnrniD3E1b4/openapi.json