# AI Company & Remote Jobs Feed - Official ATS APIs (`frank_conifer_af4/ai-remote-jobs-feed`) Actor

Collect jobs from Cohere, Perplexity, Replit, Anthropic and Scale AI. Normalize remote status, salary and application URLs. Add Greenhouse, Ashby or Lever boards and track changes.

- **URL**: https://apify.com/frank_conifer_af4/ai-remote-jobs-feed.md
- **Developed by:** [Juddroid](https://apify.com/frank_conifer_af4) (community)
- **Categories:** Developer tools, Jobs
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 job or removal records

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

## AI Company & Remote Jobs Feed - Official ATS APIs

Build a niche job board, salary explorer or job-alert app from public company career feeds. Normalize jobs from **Cohere, Perplexity, Replit, Anthropic and Scale AI**, or add official Greenhouse, Ashby and Lever boards. Get stable job IDs, remote/hybrid classification, salary fields, application URLs and change records.

### Coverage

| Source ID | Company | Public ATS |
| --- | --- | --- |
| `cohere` | Cohere | Ashby |
| `perplexity` | Perplexity | Ashby |
| `replit` | Replit | Ashby |
| `anthropic` | Anthropic | Greenhouse |
| `scale-ai` | Scale AI | Greenhouse |

These companies hire for many functions: this is not a claim that every returned role is an AI engineering job. Use `titleKeywords` to target your niche. By default, the Actor returns up to **50 jobs total and 10 per company**, without a remote-only restriction. That is a sample, not a full market index.

### Quick start: a remote engineering feed

```json
{
  "sourceIds": ["cohere", "perplexity", "replit", "anthropic", "scale-ai"],
  "remoteOnly": true,
  "titleKeywords": ["engineer", "machine learning"],
  "maxItems": 200,
  "maxItemsPerSource": 1000,
  "monitorChanges": true,
  "onlyChanges": false,
  "snapshotStoreName": "my-remote-engineering-jobs"
}
```

`titleKeywords` is an OR match on whole words/phrases. `locations` is an optional OR substring filter on published locations, not a visa or work-authorization check. `hasSalary: true` requires a published numeric salary bound. `postedWithinDays` filters on known posting dates; `0` disables it. Unknown posting dates are excluded when the date filter is enabled.

Add a public board with `boards: [{"ats":"ashby","board":"your-company","name":"Your Company"}]`. Its source ID defaults to `ashby-your-company`; select that ID in `sourceIds` to collect only the custom board. Valid ATS values are `ashby`, `greenhouse` and `lever`; only simple board slugs are accepted, not arbitrary URLs. Caller-provided company labels are not independently verified. `listSources: true` lists configured sources without per-record charges (the start fee still applies).

### Normalized output

`id` combines ATS, board and source job ID. Each job has `company`, `title`, `locations`, `department`, `employmentType`, `workplaceType`, `isRemote`, `salary`, `postedAt`, `updatedAt`, `applicationDeadline`, `description`, `jobUrl`, `applyUrl` and `sourceUrl`. Monitoring adds `isActive`, `changeType`, `firstSeenAt` and `checkedAt`.

- **Remote is not worldwide.** `worldwideEligible` stays `null`. Location restrictions must be checked in the original posting. Hybrid roles are not included by `remoteOnly`.
- Salary is only populated from structured official fields. Missing values, currencies or intervals stay `null`; no annual pay or currency is guessed. Equity is not treated as base salary. Multiple location-based pay tiers may exist; a normalized salary is not every tier.
- Posting date is not substituted with last-update date. Unknown dates remain `null`. Descriptions are normalized plain text, capped at 20,000 characters, and may omit rich formatting.
- This does not verify whether a role has been filled. `removed` means no longer in the selected successful result set. Filter changes, rolling date windows, source edits or listing removal can affect results. Never advertise removals as confirmed hires.

`SUMMARY` contains source health, scanned/matched/delivered counts, completeness and caps. `SOURCE_CATALOG` lists endpoints. Errors become uncharged `status: "error"`, `type: "sourceError"` rows; they do not erase prior jobs. A fully failed source selection fails the run. Public APIs are used without login, resume collection or applicant data.

### Full and incremental synchronization

For a full board import, select one board, use `maxItems: 1000` and `maxItemsPerSource: 1000`, then check `SUMMARY` for caps. First-run output is a baseline. Recurring runs with the same filters/store and `onlyChanges: true` deliver only new, updated and removed records. Capped or budget-blocked changes are not consumed before delivery; repeat incremental runs to finish a baseline. Normal full-output mode can repeatedly return the same leading sample, so do not use it for pagination. There is no claim of unlimited results; a single run has a 1,000-record output cap.

Upsert successful rows by `id` in your database, apply inactive tombstones, and serve your website from that database. Schedule syncs instead of launching Actors for every visitor. Keep API tokens server-side. Snapshot stores belong to the caller's account; separate customers do not share snapshots. Use independent store names for independent apps and serialize runs using the same scope. If named storage is denied, monitoring fails clearly; disable it for a stateless run. Export datasets for permanent history. Follow the source's terms, attribution rules and applicable job-ad requirements before republishing.

### Pricing

**$0.001 per delivered job or removal record ($1 per 1,000)** plus **$0.001 per Actor start**. A 50-job run has a $0.05 record fee plus the start fee. `onlyChanges: true` avoids per-record fees for unchanged jobs after the baseline. Error and catalog rows have no record fee. Empty or failed runs can still incur the start fee. Taxes, platform-specific charges and promotional discounts are separate.

# Actor input Schema

## `sourceIds` (type: `array`):

Optional IDs from the documented catalog. Omit or leave empty for all sources.

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

Total result cap. Source errors are uncharged and do not count toward this cap.

## `monitorChanges` (type: `boolean`):

Stores delivered records in a named key-value store for future comparisons.

## `onlyChanges` (type: `boolean`):

Requires snapshots. First run or a new filter scope returns a baseline, subject to output caps.

## `includeRemoved` (type: `boolean`):

Billable tombstones for records no longer in a successfully collected result set. Not proof a program ended or a vacancy was filled.

## `snapshotStoreName` (type: `string`):

Optional lowercase store name (1-63 letters, digits or hyphens). Use separate names for independent consumers; do not run the same scope concurrently.

## `listSources` (type: `boolean`):

Returns the source catalog without per-record charges. The Actor start event still applies.

## `maxItemsPerSource` (type: `integer`):

Balances the default output across companies. Increase to 1000 for full-board syncs.

## `titleKeywords` (type: `array`):

Optional OR match on whole words or phrases, for example machine learning or engineer.

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

Optional OR substring match on official locations; this does not determine work authorization.

## `remoteOnly` (type: `boolean`):

Excludes hybrid, onsite and unknown roles. Remote does not imply worldwide eligibility.

## `hasSalary` (type: `boolean`):

Keep records with a published numeric minimum or maximum.

## `postedWithinDays` (type: `integer`):

0 disables the date filter. Jobs with unknown posting dates are excluded when enabled.

## `boards` (type: `array`):

Objects with ats (greenhouse, ashby or lever), board (slug), optional name and id. No arbitrary URLs. Select custom IDs in sourceIds to collect only those boards.

## Actor input object example

```json
{
  "maxItems": 50,
  "monitorChanges": true,
  "onlyChanges": false,
  "includeRemoved": true,
  "listSources": false,
  "maxItemsPerSource": 10,
  "remoteOnly": false,
  "hasSalary": false,
  "postedWithinDays": 0
}
```

# Actor output Schema

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

No description

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

No description

## `sources` (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("frank_conifer_af4/ai-remote-jobs-feed").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("frank_conifer_af4/ai-remote-jobs-feed").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 '{}' |
apify call frank_conifer_af4/ai-remote-jobs-feed --silent --output-dataset

```

## MCP server setup

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

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/szOzCF059oQeJPSbZ/builds/KD9R2NLk83kZQiMGD/openapi.json
