# Bayt + GulfTalent Jobs Scraper — compare both boards (`entrogix_works/gulf-job-board-overlap`) Actor

Search one role in one Gulf country across Bayt and GulfTalent at once. Returns one row per board plus how much they overlap, so you can tell whether checking a single board would miss listings. Overlap is a floor and board-exclusive counts a ceiling. Unofficial; not affiliated with either site.

- **URL**: https://apify.com/entrogix\_works/gulf-job-board-overlap.md
- **Developed by:** [Entrogix Works](https://apify.com/entrogix_works) (community)
- **Categories:** Jobs
- **Stats:** 2 total users, 1 monthly users, 66.7% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$30.00 / 1,000 board compareds

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

## Bayt + GulfTalent Jobs Scraper — compare both boards

Search one role in one Gulf country on **Bayt and GulfTalent at the same time**, and find out how much the two boards actually overlap.

If you are hiring, this tells you whether posting on the second board reaches anyone new. If you are job hunting or sizing a market, it tells you whether one board is the whole picture. Neither board answers that about the other, and the headline result counts cannot be added together — the same role appears on both.

### What you get

One row per board:

| Field | Example |
|---|---|
| `board` | `bayt` |
| `listings`, `listingsMatchable` | `30`, `28` |
| `employers`, `distinctRoles` | `24`, `26` |
| **`overlapAtLeast`** | `4` |
| **`onlyOnAtMost`** | `22` |

Plus a summary in the key-value store (`OVERLAP_SUMMARY`): `role`, `country`, `overlapAtLeast`, `employersOnBothBoards`, `combinedAtMost`, `verdict`, and `matchedOn`.

**`employersOnBothBoards`** is the one figure here with no fuzziness in it: how many employers appear on both boards, whatever they posted. In a UAE "data analyst" run we measured exactly one shared *posting* out of thirty per board — but four employers posting on both. If you are tracking specific companies rather than specific openings, that is the number that matters.

### Read the two key numbers the right way

Listings are matched across boards on **normalized company name plus normalized job title** — legal suffixes (LLC, FZCO, Ltd), punctuation, case, and posting decorations (`urgent`, `required`) are stripped before comparing.

That matching **only ever errs in one direction**: it misses genuine matches when the two boards spell something differently, and it will not invent a match that is not there. So the two headline numbers are bounds, not point estimates, and they are named accordingly:

- **`overlapAtLeast`** — the boards share *at least* this many roles. The true overlap is this number or higher.
- **`onlyOnAtMost`** — *at most* this many roles are exclusive to this board. The true figure is this number or lower.

`combinedAtMost` in the summary follows from the same logic: it is the largest number of distinct openings the two boards could be showing between them.

`listingsMatchable` is how many listings had both a readable company and a readable title. The gap between it and `listings` is how much of the sample could not participate in the comparison at all — worth a glance before leaning on the result.

### The verdict

`verdict` takes one of three values:

- **`check-both`** — the boards share less than half of the smaller board's roles. Looking at only one **will** miss listings. This is the conclusion the data can support.
- **`largely-overlapping`** — the shared portion is large. Note that this is *not* a recommendation to drop one board: because overlap is a floor, "they overlap a lot" is the direction the measurement can drift toward, so it is reported as an observation rather than a verdict.
- **`incomparable`** — fewer than two boards returned matchable roles.

The asymmetry is deliberate. A tool that tells you to stop checking a board should be held to a higher standard than one that tells you to check both.

### Scope and limits

**If either board fails, the run fails.** A board that could not be fetched is never reported as zero listings, because zero would read as "nothing there" when it actually means "we could not look". You get an error and no charge rather than a comparison built on one side.

**Only countries both boards cover are accepted** — UAE, Saudi Arabia, Qatar, Kuwait, Bahrain, Oman. Bayt also covers Egypt, Jordan, Lebanon, and Morocco, but a comparison there would be one board against an absence.

**One role at a time.** Both boards receive the same search term, which is what makes the two sides comparable.

**Company and job titles only.** This Actor reads what employers publish about the position. It does not collect recruiter names, applicant details, or contact emails, and there is no mode that does.

### Pricing

Charged **per board compared**, not per listing. Each board needs its own browser fetch regardless of how many listings come back, so sampling more listings per board costs you nothing — and it makes the bounds tighter.

### Disclaimer

**This is an unofficial tool and is not affiliated with, endorsed by, or sponsored by Bayt or GulfTalent.** Both names are trademarks of their respective owners and are used here only to describe what this Actor reads. You are responsible for ensuring your use of the collected data complies with applicable law and with each site's terms.

# Actor input Schema

## `role` (type: `string`):

A single job title, e.g. "data analyst". Both boards are searched with the same term so the comparison stays fair.

## `country` (type: `string`):

Only countries both boards cover are offered. A country present on one board only would return the other as zero, which reads as a difference when it is really an absence.

## `maxItemsPerBoard` (type: `integer`):

Both boards are sampled the same way. You are charged per board, not per listing, so raising this does not cost you more.

## `minIntervalMs` (type: `integer`):

Pacing between page fetches. The two boards are fetched one after the other, never at the same time.

## `useProxy` (type: `boolean`):

On by default. Bayt does not serve without one (measured 0 of 6 attempts).

## `proxyType` (type: `string`):

Datacenter is enough for both boards. Residential costs more bandwidth for no measured gain here.

## Actor input object example

```json
{
  "role": "data analyst",
  "country": "uae",
  "maxItemsPerBoard": 30,
  "minIntervalMs": 3000,
  "useProxy": true,
  "proxyType": "DATACENTER"
}
```

# Actor output Schema

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

Every row this run produced, as JSON.

## `summary` (type: `string`):

Totals and medians for this run, so you can judge the rows without reading them all.

# 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 = {
    "role": "data analyst"
};

// Run the Actor and wait for it to finish
const run = await client.actor("entrogix_works/gulf-job-board-overlap").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 = { "role": "data analyst" }

# Run the Actor and wait for it to finish
run = client.actor("entrogix_works/gulf-job-board-overlap").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 '{
  "role": "data analyst"
}' |
apify call entrogix_works/gulf-job-board-overlap --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,entrogix_works/gulf-job-board-overlap"
        }
    }
}

```

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/kH7zwF4DOJXwxmbwn/builds/P2jCegfbAKnysSzyb/openapi.json