# Member, Vendor & Supplier Directory Scraper (`seeb/member-vendor-supplier-directory-scraper`) Actor

Scrape structured records from public HTML member, vendor, supplier, and chamber-style directories. Best for listing pages and profile-based directories that expose company names, websites, contact details, and descriptions in visible HTML.

- **URL**: https://apify.com/seeb/member-vendor-supplier-directory-scraper.md
- **Developed by:** [Techionik](https://apify.com/seeb) (community)
- **Categories:** Lead generation, SEO tools, Automation
- **Stats:** 5 total users, 3 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 dataset items

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

## 🚀 Member, Vendor & Supplier Directory Scraper

> Extract clean, structured records from public HTML directories — without scraping clutter, maps, or login-only pages.

***

### ✨ Why use this actor?

This actor is built for **public directory-style websites** where businesses, members, vendors, or suppliers are already visible in HTML.

It works especially well for:

- **Member directories**
- **Vendor directories**
- **Supplier directories**
- **Chamber-style business directories**
- **Listing pages with dedicated profile pages**
- **Public HTML directories with visible listing cards**

Instead of dumping messy raw HTML into your dataset, this actor focuses on saving only the fields that are genuinely useful for research, outreach, and lead generation.

***

### ✅ Best for

Use this actor when you need to collect structured records from websites such as:

- Association member directories
- Vendor and supplier directories
- Chamber or chamber-style listings
- Public business/member profile pages
- Listing-based directories with visible website and contact details

***

### 📦 Typical output

Depending on what the target site publicly exposes, the actor can extract:

- **Organization name**
- **Category**
- **City**
- **Region / state / province**
- **Phone**
- **Email**
- **Website**
- **Source category name**
- **Profile URL**
- **Short description**

The dataset is intentionally kept **clean and practical** so it is easier to use in spreadsheets, CRMs, outreach workflows, and research pipelines.

***

### 🎯 Ideal use cases

This actor is a great fit for:

- Lead generation
- Vendor discovery
- Supplier research
- Association member research
- Public directory extraction
- Building niche outreach lists
- Collecting structured company records from public HTML listings

***

### ⚙️ Input

#### **Start URLs**

One or more public directory, category, or listing URLs.

#### **Crawl Mode**

Choose how the actor should run:

- **Collect items**\
  Tries to save up to the target number of results per start URL.

- **Crawl pages**\
  Crawls up to the target number of pages per start URL and saves what it finds.

#### **Max Items Per URL**

Maximum number of results to save for each start URL.

#### **Max Pages Per URL**

Maximum number of pages to crawl for each start URL.

#### **Use Apify Proxy**

Enable proxy usage if the target site rate-limits or blocks repeated requests.

***

### 🧾 Output fields

Saved results may include:

- `organizationName`
- `category`
- `city`
- `region`
- `phone`
- `email`
- `website`
- `sourceCategoryName`
- `profileUrl`
- `description`

Only fields with meaningful values are saved, which helps keep the dataset useful and easy to work with.

***

### 💼 What this actor supports well

This actor performs best on:

- Public HTML directories
- Directories with visible listing cards
- Directories with dedicated detail/profile pages
- Chamber-style and association-style listings
- Vendor and supplier directories with public detail pages

***

### 🚫 What this actor is not for

This actor is **not intended** for:

- Login-protected directories
- JavaScript-heavy apps that hide content behind client-side rendering
- Google Maps-style interfaces
- Arbitrary websites that are not directories
- Private portals or highly customized internal systems

***

### 📝 Notes

- Results depend on the target site’s public HTML structure.
- Some directories expose data directly on listing pages.
- Others require the actor to open detail/profile pages.
- Some sites only expose names and websites.
- Others also expose phone, email, city, region, and descriptions.
- If a site blocks requests, enabling **Apify Proxy** may improve reliability.

***

### 👍 Recommended usage

For best results:

1. Start with **one URL at a time**
2. Use **Collect items** when building lead lists
3. Use **Crawl pages** when testing a new directory
4. Enable proxy if the site appears blocked or rate-limited

***

### 🏁 Summary

**Member, Vendor & Supplier Directory Scraper** is a focused actor for extracting structured records from public HTML directories.

It is designed for practical business use, clean output, and reliable scraping of:

- member directories
- vendor directories
- supplier directories
- chamber-style listings
- profile-based public business directories

# Actor input Schema

## `startUrls` (type: `array`):

Public directory, category, listing, or search-result URLs to start from.

## `crawlMode` (type: `string`):

Choose whether the actor should collect a target number of items or crawl a target number of pages per start URL.

## `maxItemsPerStartUrl` (type: `integer`):

Maximum number of results to save for each start URL. Set 0 to disable this limit.

## `maxPagesPerStartUrl` (type: `integer`):

Maximum number of pages to crawl for each start URL. Set 0 to disable this limit and use the internal safety cap.

## `useApifyProxy` (type: `boolean`):

Enable Apify Proxy if the target site rate-limits repeated requests.

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://annapolischambermd.chambermaster.com/list/category/cafes-175"
    }
  ],
  "crawlMode": "collectItems",
  "maxItemsPerStartUrl": 10,
  "maxPagesPerStartUrl": 0,
  "useApifyProxy": false
}
```

# Actor output Schema

## `results` (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 = {
    "startUrls": [
        {
            "url": "https://annapolischambermd.chambermaster.com/list/category/cafes-175"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("seeb/member-vendor-supplier-directory-scraper").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 = { "startUrls": [{ "url": "https://annapolischambermd.chambermaster.com/list/category/cafes-175" }] }

# Run the Actor and wait for it to finish
run = client.actor("seeb/member-vendor-supplier-directory-scraper").call(run_input=run_input)

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

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

```

## CLI example

```bash
echo '{
  "startUrls": [
    {
      "url": "https://annapolischambermd.chambermaster.com/list/category/cafes-175"
    }
  ]
}' |
apify call seeb/member-vendor-supplier-directory-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=seeb/member-vendor-supplier-directory-scraper",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

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