# Wellfound Job Details with Visa and Remote Policy (`gubidonius/wellfound-job-details`) Actor

The full Wellfound job page, not the card: exact pay and period, equity band, visa sponsorship, which countries the company hires remotely from, preferred timezones, relocation, skills and the whole advert. Give it job links, or a role and city to find them.

- **URL**: https://apify.com/gubidonius/wellfound-job-details.md
- **Developed by:** [Gregory Bolshakov](https://apify.com/gubidonius) (community)
- **Categories:** Jobs, Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

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

## Wellfound Job Details with Visa and Remote Policy

Reads the full Wellfound job page, not the search card. Exact pay with its period, the equity
band, visa sponsorship, which countries the company will hire remotely from, preferred
timezones, relocation, skills, and the whole advert. No key and no login.

### What the card does not have

A Wellfound search card gives you a title, a company, a rounded pay range and a city. The job
page carries the rest, and most of it is not in any search result:

- Visa sponsorship, Available or Not Available
- Hires remotely in, which is often a country list and sometimes Everywhere
- Preferred timezones and collaboration hours
- Relocation, Allowed or Not Allowed
- Exact posting time. The page only says today or yesterday, the record behind it has the
  timestamp

### Pay comes from the record, not the line

The header prints `$194k - $220k`. The posting record behind it holds 194000 and 220000 with a
currency code and a period. This Actor reads that, so nothing is rounded and nothing is
converted.

`salaryPeriod` is on every row and says YEAR, HOUR or MONTH. Both turn up on job boards, and
an hourly rate read as a yearly one is out by a factor of two thousand.

`compensationRaw` keeps the printed line so you can check the parse yourself.

### Equity has three states

A band, `No equity`, or nothing said. `equityDisclosure` is `range`, `none` or `not-stated`.
Nothing said is not zero. You can filter for jobs that really grant equity, and separately for
jobs that told you they do not.

### Finding the jobs

Give it job links or ids. If you give none, it takes them from a role and city search.

A search page groups jobs under companies and shows at most three per company, so one page of
20 companies yields about 45 links against a search total of 733 jobs. That is a sample, not
the first 45. The run summary carries both numbers, and links are taken one per company before
going deeper, so a small run covers many companies instead of three jobs at one.

### What happens when a job is gone

A job link that has been taken down is a fact about that job. The other links are still read,
the gone ones are listed in `RUN_SUMMARY` with the reason, and you are not charged for them.

### Input

| Field | What it does |
|---|---|
| `jobUrls` | Job links or bare ids. Leave empty to search instead |
| `role` | Role slug, used only when no links are given |
| `location` | Location slug, used only when no links are given |
| `remote` | Read the role's remote board instead of the location |
| `maxResults` | Upper bound for the whole run. One job is one page load |
| `maxSearchPages` | How many search pages to take links from |

### Output

One row per job, with 41 columns. `RUN_SUMMARY` in the key value store holds the search
that was used, how many links it found against the total it claimed, how many jobs published
pay and equity, and every link that could not be read.

### Price

0.002 dollars per run and 0.008 dollars per job. One job is one page load, which is why this
costs more per row than the search Actors. Both are charged after the rows exist, so a run
that reads nothing costs nothing.

# Actor input Schema

## `jobUrls` (type: `array`):

Wellfound job links or bare ids, for example https://wellfound.com/jobs/4677991-founding-product-engineer or 4677991. Leave empty to find jobs with the role and location below instead.

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

Used only when no job links are given. A Wellfound role slug, for example software-engineer, product-manager, designer.

## `location` (type: `string`):

Used only when no job links are given. A Wellfound location slug, for example new-york, london, bangalore.

## `remote` (type: `boolean`):

Read the role's remote board and ignore the location above.

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

Upper bound on jobs for the WHOLE run. Each job is one page load, so this is also the request count. You are never charged for more than this.

## `maxSearchPages` (type: `integer`):

How many search pages to take job links from. Ignored when you give job links yourself.

## Actor input object example

```json
{
  "jobUrls": [],
  "role": "software-engineer",
  "location": "new-york",
  "remote": false,
  "maxResults": 20,
  "maxSearchPages": 3
}
```

# 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 = {
    "jobUrls": [],
    "role": "software-engineer",
    "location": "new-york",
    "maxResults": 20
};

// Run the Actor and wait for it to finish
const run = await client.actor("gubidonius/wellfound-job-details").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 = {
    "jobUrls": [],
    "role": "software-engineer",
    "location": "new-york",
    "maxResults": 20,
}

# Run the Actor and wait for it to finish
run = client.actor("gubidonius/wellfound-job-details").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 '{
  "jobUrls": [],
  "role": "software-engineer",
  "location": "new-york",
  "maxResults": 20
}' |
apify call gubidonius/wellfound-job-details --silent --output-dataset

```

## MCP server setup

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

```

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/i2zexTSWLdfO6gTIl/builds/K49NUjtXWOGgB6O2q/openapi.json