# Remote Jobs Scraper (Remote OK, We Work Remotely, Jobicy) (`hexadatalabs/remote-jobs-scraper`) Actor

Use this when you need current remote jobs from Remote OK, We Work Remotely and Jobicy in one clean, de-duplicated list: title, company, region, category, tags, salary, description and link. Filter by keyword, category, region and date, or get only new jobs since the last run. Pay per job.

- **URL**: https://apify.com/hexadatalabs/remote-jobs-scraper.md
- **Developed by:** [Hexadata](https://apify.com/hexadatalabs) (community)
- **Categories:** Jobs, Lead generation, Agents
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$2.00 / 1,000 job saveds

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?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

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

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Remote Jobs Scraper (Remote OK, We Work Remotely, Jobicy)

Remote jobs scraper that returns the current openings of Remote OK, We Work Remotely and Jobicy in one clean list: about 2,000 open remote jobs with title, company, region, category, tags, salary when published, full description and link, de-duplicated across boards and newest first. Filter by keyword, category, region and date, or get only the jobs that are new since your last run. Pay per result: **$2.00 per 1,000 jobs**, nothing for jobs that do not match your filters.

### What you get

One JSON object per open remote job, the same shape for the three boards:

- `id` (string) — stable id, `<board>:<posting id>`; no duplicates inside a run.
- `title` (string), `url` (string, the job page on the board), `applyUrl` (string | null).
- `source` (string: `remoteok`, `weworkremotely` or `jobicy`), `sourceName` (string), `attribution` (string, the credit line the board asks for).
- `companyName` (string | null).
- `location` (string | null) — the region or countries the job is open to, e.g. `Anywhere in the World`, `LATAM, Europe`, `USA`; `country` (string | null).
- `remote` (boolean) — always `true`.
- `category` (string | null), `tags` (string\[]), `employmentType` (string | null), `seniority` (string | null).
- `salaryMin`, `salaryMax` (number | null), `currency`, `salaryPeriod` (string | null) — only when the board publishes a salary.
- `publishedAt`, `expiresAt` (ISO 8601 | null), `scrapedAt` (ISO 8601).
- `description` (string | null) — plain text, no HTML.

The run also writes a `SUMMARY` record to the key-value store: open jobs per board, how many matched, how many were saved and how many duplicates across boards were skipped.

### Use cases

1. **Remote job boards and newsletters** backfill a niche board (design, support, LATAM-friendly) every morning with the new postings only.
2. **Recruiters and talent agencies** watch which companies hire remotely for a role and in which regions.
3. **Sales teams** treat remote hiring as a signal: a company opening remote support roles is a lead for help-desk tooling.
4. **Compensation analysts** collect published remote salary ranges by role and seniority.
5. **AI agents and job seekers** ask "what remote product design jobs open to Europe were posted this week?" and get a structured answer.

### Input

| Field | Type | Default | Description |
| --- | --- | --- | --- |
| `searchQueries` | string\[] | `[]` | Case-insensitive phrases matched in the job title and tags, e.g. `engineer`, `customer support`. Empty = every open remote job. |
| `excludeKeywords` | string\[] | `[]` | Skip jobs whose title contains any of these, e.g. `senior`. |
| `searchInDescription` | boolean | `false` | Also match `searchQueries` in the description. |
| `categories` | string\[] | `[]` | Phrases matched in the category and tags, e.g. `programming`, `design`, `sales`. |
| `locations` | string\[] | `[]` | Phrases matched in the region or countries, e.g. `anywhere`, `usa`, `europe`, `latam`. |
| `sources` | string\[] | all three | Any of `remoteok`, `weworkremotely`, `jobicy`. |
| `onlyWithSalary` | boolean | `false` | Keep only jobs that publish a salary range. |
| `dateFrom` | string (YYYY-MM-DD) | — | Keep jobs published on or after this date. |
| `onlyNewSinceLastRun` | boolean | `false` | Return only jobs that earlier runs with the same filters did not deliver. For schedules. |
| `maxResults` | integer | `100` | Hard cap on the jobs saved, newest first, and therefore on the cost of the run. |
| `includeDescription` | boolean | `true` | Return the description as plain text. |
| `removeDuplicates` | boolean | `true` | Keep one posting when the same role of the same company is on two boards. |
| `proxyConfiguration` | object | off | Not needed: these are public feeds. |

Filters are combined with AND; several values inside one filter are OR-ed. The input is validated before the first request; a wrong value stops the run with a message that says which one, and nothing is charged.

### Output example

Two real items from a run on 2026-11-11 (the first description is shortened here; the second run had `includeDescription` off):

```json
[
  {
    "id": "jobicy:161414",
    "title": "Principal Software Engineer, Containers",
    "url": "https://jobicy.com/jobs/161414-principal-software-engineer-containers",
    "applyUrl": "https://jobicy.com/jobs/161414-principal-software-engineer-containers",
    "source": "jobicy",
    "sourceName": "Jobicy",
    "attribution": "Source: Jobicy (https://jobicy.com). Credit Jobicy and send applicants to `url` when you display this job.",
    "companyName": "Chainguard",
    "location": "Canada, Germany, UK, USA",
    "country": null,
    "remote": true,
    "category": "Software Engineering",
    "tags": ["Software Engineering"],
    "employmentType": "Full-Time",
    "seniority": "Senior",
    "salaryMin": 229000,
    "salaryMax": 258000,
    "currency": "USD",
    "salaryPeriod": "yearly",
    "publishedAt": "2026-11-11T18:44:42.000Z",
    "expiresAt": null,
    "description": "Chainguard is the trusted source for open source. By delivering hardened, secure, and production-ready builds of all the open source software engineers and AI agents rely on…",
    "scrapedAt": "2026-11-12T05:23:06.826Z"
  },
  {
    "id": "weworkremotely:anchour-marketing-designer",
    "title": "Marketing Designer",
    "url": "https://weworkremotely.com/remote-jobs/anchour-marketing-designer",
    "applyUrl": "https://weworkremotely.com/remote-jobs/anchour-marketing-designer",
    "source": "weworkremotely",
    "sourceName": "We Work Remotely",
    "attribution": "Source: We Work Remotely (https://weworkremotely.com). Link back to `url` when you display this job.",
    "companyName": "Anchour",
    "location": "Anywhere in the World, Alabama",
    "country": null,
    "remote": true,
    "category": "Sales and Marketing",
    "tags": [],
    "employmentType": "Full-Time",
    "seniority": null,
    "salaryMin": null,
    "salaryMax": null,
    "currency": null,
    "salaryPeriod": null,
    "publishedAt": "2026-11-09T17:43:52.000Z",
    "expiresAt": "2026-12-09T17:43:52.000Z",
    "description": null,
    "scrapedAt": "2026-11-12T05:24:07.524Z"
  }
]
```

### Pricing & cost examples

Pay per event: **$0.002 per job saved** ($2.00 per 1,000). Starting a run is free. Jobs that do not match your filters and duplicates are never charged, and `maxResults` is a hard cap.

- **Every open remote job on the three boards**, about 2,000 jobs ≈ **$4.00**.
- **A daily schedule with `onlyNewSinceLastRun` for "engineer"**, about 60 new jobs a day ≈ **$0.12 per day**, ≈ $3.60 per month.
- **The 20 newest jobs of the prefilled example** ≈ **$0.04**.

### Use with AI agents (MCP)

Add the Actor to any MCP client (Claude, Cursor, VS Code) through the Apify MCP server:

```
https://mcp.apify.com?tools=hexadatalabs/remote-jobs-scraper
```

Send your Apify token as `Authorization: Bearer <APIFY_TOKEN>`. The tool appears as `hexadatalabs--remote-jobs-scraper`. Example prompt: *"Use the remote jobs scraper to find remote product design jobs open to Europe posted this week, with salary when published, and list them with the link to apply."*

#### Pay with USDC (x402, no account needed)

AI agents can pay for this Actor with USDC (x402) or a prepaid token bought from Apify AGI with a [Coinbase Agentic Wallet](https://docs.cdp.coinbase.com/agentic-wallets/welcome), with no Apify account. The Actor is eligible: pay-per-event pricing, limited permissions, no Standby mode. The flow:

```bash
npx -y awal auth login <email> && npx awal auth verify <code>   # one-time wallet setup; then fund it with USDC and a little ETH on Base
TOKEN=$(npx awal x402 pay 'https://agi.apify.com/protocols/x402/prepaid-tokens?amount=1&currency=usd' --max-amount 1000000 --json | jq -r .token)
curl -s -X POST "https://api.apify.com/v2/acts/hexadatalabs~remote-jobs-scraper/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  -d '{"searchQueries":["designer"],"locations":["europe","anywhere"],"maxResults":25}'
```

Cost: **$1 USDC ≈ 500 jobs**; the token balance is a hard spending cap, and the token expires 14 days after purchase.

### API & integrations

`run-sync-get-dataset-items` returns the jobs in the same HTTP call:

```bash
curl -s -X POST "https://api.apify.com/v2/acts/hexadatalabs~remote-jobs-scraper/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"searchQueries":["engineer"],"onlyWithSalary":true,"maxResults":50}'
```

```python
from apify_client import ApifyClient

client = ApifyClient("<APIFY_TOKEN>")
run = client.actor("hexadatalabs/remote-jobs-scraper").call(run_input={
    "categories": ["design"],
    "locations": ["anywhere", "europe"],
    "maxResults": 100,
})
for job in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(job["companyName"], "|", job["title"], "|", job["location"], "|", job["url"])
```

```javascript
import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<APIFY_TOKEN>' });
const run = await client.actor('hexadatalabs/remote-jobs-scraper').call({
    searchQueries: ['customer support'],
    onlyNewSinceLastRun: true,
    maxResults: 200,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
```

**Schedules and webhooks.** Create a Schedule (for example every day at 07:00) with `onlyNewSinceLastRun: true` and add a webhook on `ACTOR.RUN.SUCCEEDED` to push the new jobs to Slack, a sheet or your own job board. Each filter set keeps its own memory, so several schedules do not interfere. The same works from n8n, Make and Zapier with the Apify integration.

### Limitations & legal

- **Sources and their conditions.** [Remote OK API](https://remoteok.com/api) (link back to the job URL and name Remote OK as the source), [We Work Remotely RSS feeds](https://weworkremotely.com/remote-job-rss-feed) ("Anyone can use the feed", with links attributed back) and the [Jobicy API](https://jobicy.com/jobs-rss-feed) (storing and redistributing is allowed; credit Jobicy and send applicants to the original URL). **If you display these jobs, keep the link in `url` and the credit in `attribution`.** Do not use the Remote OK logo.
- **Boards left out on purpose.** Himalayas, Remotive and Arbeitnow do not allow their feeds to be passed on to third parties or used commercially, so they are not included.
- **Freshness.** The boards are read at most once an hour, as they ask; a run within the same hour reuses the copy, so results can be up to about an hour old. Jobicy lists the last 7 days; Remote OK about its 100 newest jobs; We Work Remotely its current listings.
- **Fields depend on the board.** Remote OK has tags but no category; We Work Remotely rarely publishes salary; Jobicy gives a region list instead of a country. Missing values are `null`, never guessed.
- **Duplicates.** The same role at the same company on two boards is matched by company and title; near-identical titles with different wording are kept as separate jobs.
- **No personal data.** Job postings describe roles, not people.

### Changelog

- 0.1 (2026-11-11) — first release: Remote OK, We Work Remotely and Jobicy; keyword, category, region, salary and date filters; duplicates across boards removed; `onlyNewSinceLastRun`.

### Support

Open an issue in the Issues tab; we answer within 24 hours. Know a remote board whose terms allow reuse? Open an issue with the link to its API or feed terms and we add it.

# Actor input Schema

## `searchQueries` (type: `array`):

Case-insensitive phrases matched in the job title and tags, one per line, e.g. `engineer`, `customer support`, `python`. Leave empty for every open remote job.

## `excludeKeywords` (type: `array`):

Jobs whose title contains any of these phrases are skipped, e.g. `senior`, `intern`.

## `searchInDescription` (type: `boolean`):

Match `searchQueries` in the job description as well, e.g. to find every job that mentions `kubernetes`.

## `categories` (type: `array`):

Phrases matched in the job's category and tags, e.g. `programming`, `design`, `sales`, `marketing`, `customer support`, `devops`.

## `locations` (type: `array`):

Phrases matched in the region or countries the job is open to, e.g. `anywhere`, `usa`, `europe`, `germany`, `latam`.

## `sources` (type: `array`):

Which boards to read. Leave empty for all three.

## `onlyWithSalary` (type: `boolean`):

Keep only jobs that publish a salary range.

## `dateFrom` (type: `string`):

Keep jobs published on or after this date (YYYY-MM-DD), e.g. `2026-11-01`.

## `onlyNewSinceLastRun` (type: `boolean`):

Use this for a daily schedule: each run returns only the jobs that earlier runs with the same filters did not deliver. The first run returns everything that matches.

## `maxResults` (type: `integer`):

Stop after this many jobs, newest first, e.g. `100` costs at most $0.20.

## `includeDescription` (type: `boolean`):

Return the full description as plain text. Turn it off for lighter rows; the price per job is the same.

## `removeDuplicates` (type: `boolean`):

When the same role of the same company is on two boards, keep only the newest posting.

## `proxyConfiguration` (type: `object`):

These are public feeds and do not need a proxy; leave it off.

## Actor input object example

```json
{
  "searchQueries": [
    "engineer"
  ],
  "searchInDescription": false,
  "onlyWithSalary": false,
  "onlyNewSinceLastRun": false,
  "maxResults": 20,
  "includeDescription": true,
  "removeDuplicates": true,
  "proxyConfiguration": {
    "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 = {
    "searchQueries": [
        "engineer"
    ],
    "maxResults": 20,
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("hexadatalabs/remote-jobs-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 = {
    "searchQueries": ["engineer"],
    "maxResults": 20,
    "proxyConfiguration": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("hexadatalabs/remote-jobs-scraper").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 '{
  "searchQueries": [
    "engineer"
  ],
  "maxResults": 20,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call hexadatalabs/remote-jobs-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,hexadatalabs/remote-jobs-scraper"
        }
    }
}
```

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/FrEzquDch5PMxYi8L/builds/hde9dEQkC48avaanH/openapi.json
