# US Home Inspectors · ASHI & InterNACHI Hub (`corent1robert/us-home-inspectors-hub`) Actor

One run merges public ASHI and InterNACHI inspector contacts into one CRM table. Pick both directories or one. Filter by US state. Children bill their own PPE — this hub does not double-charge rows. No login.

- **URL**: https://apify.com/corent1robert/us-home-inspectors-hub.md
- **Developed by:** [Corentin Robert](https://apify.com/corent1robert) (community)
- **Categories:** Lead generation, Real estate, Business
- **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.00005 / actor start

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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

## US Home Inspectors · ASHI & InterNACHI Hub

**One run, one CRM-ready table** — merge public **ASHI** and **InterNACHI** home inspector contacts without running two jobs yourself.

**No login. No directory account.** Pick **Both directories** or one source. Try starts on **ASHI + Florida** so the first run stays a cheap HTTP export.

***

### Who is this for?

| You are… | Typical goal | Suggested setup |
|----------|--------------|-----------------|
| Home-services / solar / roofing | Inspectors who already work with homeowners | **ASHI only**, Florida, contact-only |
| Insurance or restoration | Broader coverage in one state | **Both directories**, one state, `maxItems: 20` first |
| Agency / outbound | Territory list with email and phone | One state, contact-only, raise **Max inspectors** on a paid plan |
| Data / ops | Scheduled master table | Same inputs on a schedule |

**What you get by default:** the same rows as the standalone ASHI and InterNACHI Actors, appended into **one hub dataset**, with `source`, `hub_child_actor` and `hub_child_run_id` so you can trace which export produced each row.

**When to enable website emails:** InterNACHI listings typically show phone and website, not a mailbox. Turn **Find emails on the inspector website** on only for InterNACHI (or both-directory) runs when you need inboxes from public company sites.

***

### How it works (simple)

1. You choose **Both directories**, **ASHI only**, or **InterNACHI only**, plus **states** and **max inspectors**.
2. This hub starts the matching **child Actor(s)** on your Apify account (`corent1robert`).
3. The same `states`, `onlyWithContact` and `maxItems` are passed to every child. `findEmailsOnWebsite` is passed to **InterNACHI only**.
4. When each child run succeeds, its dataset rows are **copied into this hub’s dataset**.
5. You download **one CSV / Excel / JSON** from the hub run.

***

### Quick start

1. Open this Actor on Apify and click **Try for free** or **Start**.
2. Leave **Source** on **ASHI only** for a first run (or pick InterNACHI / both).
3. Keep **US states** on **Florida** and **Max inspectors** at 20.
4. Click **Start**. Open **Storage → Dataset** when the hub finishes.

***

### Ready-made examples

Saved Console tasks (publish tomorrow for Store landing pages):

| Example | Best for |
|---------|----------|
| Florida ASHI inspectors via the hub | First run / cheap HTTP |
| Florida ASHI and InterNACHI inspector list | Both directories, one state |
| California ASHI and InterNACHI inspectors | Second geo |
| US home inspectors nationwide sample of 20 | Capped nationwide sample |

***

### Standalone directory Actors

You can still run each directory alone (same data, no hub merge):

| Directory | Actor |
|-----------|--------|
| ASHI | [ASHI Home Inspectors · Emails & Phones by State](https://apify.com/corent1robert/ashi-homeinspector-scraper) |
| InterNACHI | [InterNACHI Inspectors · Emails & Phones by State](https://apify.com/corent1robert/internachi-inspectors-scraper) |

***

### Input

| Field | Type | Default | Notes |
|-------|------|---------|--------|
| `source` | string | `all` (Try prefill: `ashi`) | `all`, `ashi`, or `internachi` |
| `states` | array | Try prefill `["FL"]` | Passed through to each child. Empty = nationwide on **every** selected directory |
| `onlyWithContact` | boolean | `true` | Passed through. CRM-ready rows only |
| `maxItems` | integer | `20` | Passed through to each child. **0** = no row ceiling. **Free plan: 20 / child run** |
| `findEmailsOnWebsite` | boolean | `false` | Passed to **InterNACHI only**. ASHI already copies emails from the public profile |

Florida ASHI sample (Try):

```json
{ "source": "ashi", "states": ["FL"], "onlyWithContact": true, "maxItems": 20 }
```

Both directories, Florida:

```json
{ "source": "all", "states": ["FL"], "onlyWithContact": true, "maxItems": 20 }
```

Nationwide sample (omit `states`):

```json
{ "source": "all", "onlyWithContact": true, "maxItems": 20 }
```

**API-only:** `verboseLogs` (boolean, default `false`) — extra debug lines. Not shown on the Console form. `proxyConfiguration` is not used by the hub (children apply their own defaults).

***

### Output

Child schemas differ slightly (ASHI has membership fields; InterNACHI has city and optional website emails). The hub copies each row as-is and adds:

| Field | Meaning |
|-------|---------|
| `source` | Hub key (`ashi` or `internachi`) |
| `hub_child_actor` | Store id of the child Actor |
| `hub_child_run_id` | Child run id |

Example row (ASHI, transformed values as exported):

```json
{
  "source": "ashi",
  "name": "Jane Inspector",
  "companyName": "Coastal Home Inspections",
  "email": "jane@example.com",
  "phone": "(239) 555-0100",
  "website": "https://example.com",
  "state": "FL",
  "profileUrl": "https://www.homeinspector.org/profile/jane-inspector/",
  "hasEmail": true,
  "hasPhone": true,
  "hub_child_actor": "corent1robert/ashi-homeinspector-scraper",
  "hub_child_run_id": "xxxxx"
}
```

Download JSON, CSV or Excel from the hub dataset. Use the **Outreach CRM** view when you mainly need email and phone.

***

### How much does it cost to scrape US home inspectors?

This hub is **pay-per-event**:

| Event | FREE | Bronze | Silver | Gold |
|-------|------|--------|--------|------|
| Hub `apify-actor-start` | $0.00005 | $0.00005 | $0.00005 | $0.00005 |
| Copied dataset rows on the hub | $0 | $0 | $0 | $0 |

| Scenario | Hub start | Copied rows | Notes |
|----------|-----------|-------------|--------|
| 20 ASHI inspectors (Try) | ~$0.00005 | $0 on hub | Plus ASHI child PPE / compute |
| 20 + 20 both directories | ~$0.00005 | $0 on hub | Plus **two** child runs |
| Bulk paid plan | ~$0.00005 | $0 on hub | Children bill inspector-with-email / phone |

**On top of the hub start**, Apify also bills **each child Actor run** (compute and that child’s PPE). A **Both directories** job is **1 hub run + 2 child runs**. ASHI and InterNACHI still charge per inspector with email or phone. This hub does **not** double-charge copied rows.

**Free plan:** 20 inspectors per child run.

***

### Is it legal to scrape ASHI and InterNACHI?

This Actor only starts the public ASHI and InterNACHI directory Actors. It copies data those sites already publish. As with any file that contains personal information, make sure your use complies with GDPR, CCPA and relevant regulations.

[Is web scraping legal?](https://blog.apify.com/is-web-scraping-legal/)

***

### Good to know

- **Timeouts:** InterNACHI uses a browser. Allow extra time when running **both** directories or `maxItems: 0`.
- **Failures:** if one directory run fails, the hub logs it and continues with the other; check **RUN\_LOG**.
- **Local development:** `apify run` needs `APIFY_TOKEN` (or `apify login`) so the hub can call children. Without a token, the run logs a warning and exits without error.

***

### Local development

```bash
npm install
cp .actor/INPUT.json storage/key_value_stores/default/INPUT.json
apify run
```

Use `apify run` (not `npm start`). Local `storage/` is not synced to Apify Console.

***

### Also available

- **[ASHI Home Inspectors](https://apify.com/corent1robert/ashi-homeinspector-scraper)** — ASHI directory only
- **[InterNACHI Inspectors](https://apify.com/corent1robert/internachi-inspectors-scraper)** — InterNACHI directory only
- **[IICRC Certified Firms](https://apify.com/corent1robert/iicrc-certified-firms-scraper)** — restoration / mold / cleaning firms by state

***

### Support

Questions about a US inspectors delivery, or a custom merged file?

**<corentin@outreacher.fr>** — or reply on your Apify run thread.

Ready? Keep **ASHI only** and **Florida**, then click **Start**.

# Actor input Schema

## `source` (type: `string`):

Which inspector directory should this run start?

## `states` (type: `array`):

Keep inspectors listed in these states. Leave empty for a nationwide list. Try starts on Florida.

## `onlyWithContact` (type: `boolean`):

Get a CRM-ready file. Skip cards that do not publish a mailbox, phone or (InterNACHI) website on the public page.

## `maxItems` (type: `integer`):

Passed to every child Actor. **0** = no ceiling on that directory. **Free plan: 20 per child run.**

## `findEmailsOnWebsite` (type: `boolean`):

Passed to InterNACHI only. The InterNACHI directory itself does not publish emails. Turn this on to copy a public mailbox from the inspector website. Off by default. Ignored for ASHI-only runs.

## Actor input object example

```json
{
  "source": "ashi",
  "states": [
    "FL"
  ],
  "onlyWithContact": true,
  "maxItems": 20,
  "findEmailsOnWebsite": false
}
```

# Actor output Schema

## `overview` (type: `string`):

No description

## `outreachCrm` (type: `string`):

No description

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

No description

## `runLog` (type: `string`):

No description

# 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 = {
    "source": "ashi",
    "states": [
        "FL"
    ],
    "onlyWithContact": true,
    "maxItems": 20,
    "findEmailsOnWebsite": false
};

// Run the Actor and wait for it to finish
const run = await client.actor("corent1robert/us-home-inspectors-hub").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 = {
    "source": "ashi",
    "states": ["FL"],
    "onlyWithContact": True,
    "maxItems": 20,
    "findEmailsOnWebsite": False,
}

# Run the Actor and wait for it to finish
run = client.actor("corent1robert/us-home-inspectors-hub").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 '{
  "source": "ashi",
  "states": [
    "FL"
  ],
  "onlyWithContact": true,
  "maxItems": 20,
  "findEmailsOnWebsite": false
}' |
apify call corent1robert/us-home-inspectors-hub --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,corent1robert/us-home-inspectors-hub"
        }
    }
}
```

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/jy3ZTrc8gCY1Zqyfc/builds/dovTnd8pzVCDsL4WO/openapi.json