# JIG Member Directory Actor (`tehsnarf/jig-member-directory`) Actor

Scrapes the public JIG (Joint Inspection Group) aviation-fuel standards body member directory into structured company lead data.

- **URL**: https://apify.com/tehsnarf/jig-member-directory.md
- **Developed by:** [Chris Hoover](https://apify.com/tehsnarf) (community)
- **Categories:** Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-usage

## 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

## JIG Member Directory Actor

Scrapes the public [JIG (Joint Inspection Group)](https://www.jig.org/about/member-directory/)
aviation-fuel standards body member directory into structured company records — company name,
region, member-since date, website, and logo.

### Use cases

1. **Aviation-fuel supplier lead generation** — build a prospect list of JIG member companies
   (fuel suppliers, airport fuel operators, energy majors) for sales/BD outreach.
2. **Market mapping** — analyze the geographic spread of JIG's ~194-member network by region.
3. **Competitive/compliance monitoring** — track new members joining the JIG standards ecosystem
   over time via `memberSince` and repeated scheduled runs.

### Output fields

| Field | Type | Description |
|---|---|---|
| companyName | string | Member company name |
| region | string | Region/head office label (e.g. "Africa", "Europe") — blank for some members |
| memberSince | string | Member-since date as shown on site (e.g. "February 21, 2022") |
| websiteUrl | string | Member's website URL, if listed |
| logoUrl | string | Member's logo image URL |
| sourcePage | integer | Which directory page (1+) the row came from |
| scrapedAt | string | ISO 8601 scrape timestamp |

#### Example output

```json
{
  "companyName": "11 PLC",
  "region": "Africa",
  "memberSince": "February 21, 2022",
  "websiteUrl": "https://www.11plc.com",
  "logoUrl": "https://kamino.fra1.cdn.digitaloceanspaces.com/jig/app/uploads/2024/05/11PLC-300x187.jpg",
  "sourcePage": 1,
  "scrapedAt": "2026-08-03T00:14:59.299514+00:00"
}
```

### Input configuration

| Field | Default | Description |
|---|---|---|
| `startUrls` | JIG member directory page | Only the directory page itself is needed — page 1 is scraped directly, later pages are fetched automatically via the site's own AJAX endpoint |
| `maxItems` | 100 | Maximum member rows to scrape |
| `maxPages` | 20 | Safety cap on directory pages paged through (directory is ~4 pages / 194 members as of 2026-08-02, and will grow) |
| `delaySeconds` | 1.0 | Polite delay before each page fetch |

Pagination is inherently sequential (each page's existence can only be confirmed by fetching it —
there's no known total-page-count up front), so page fetches are not batched with concurrency;
all member data lives directly in each listing page, so there is no separate per-item detail-page
fetch loop for concurrency to apply to.

### Pricing

**$5 per 1,000 results.** The full directory is ~194 members, so a complete run costs under $1.
Example costs:

| Results | Cost |
|---|---|
| 100 | $0.50 |
| 500 | $2.50 |
| 1,000 | $5.00 |
| 5,000 | $25.00 |

### Notes

- Public data only — no login required, no personal names/emails collected (company-level fields
  only).
- `robots.txt` explicitly allows the AJAX endpoint (`admin-ajax.php`) used for pagination.

# Actor input Schema

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

URL of the JIG member directory page (only one is used — page 1)

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

Maximum number of member rows to scrape

## `maxPages` (type: `integer`):

Safety cap on how many directory pages to page through (directory has ~4 pages as of 2026-08-02, growing over time)

## `delaySeconds` (type: `number`):

Polite delay each fetch waits before requesting

## Actor input object example

```json
{
  "startUrls": [
    {
      "url": "https://www.jig.org/about/member-directory/"
    }
  ],
  "maxItems": 100,
  "maxPages": 20,
  "delaySeconds": 1
}
```

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

// Run the Actor and wait for it to finish
const run = await client.actor("tehsnarf/jig-member-directory").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("tehsnarf/jig-member-directory").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 '{}' |
apify call tehsnarf/jig-member-directory --silent --output-dataset

```

## MCP server setup

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

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/1kyXZXkAfMenMebWb/builds/omPu4liTSV09NE7hV/openapi.json