# AI Jobs Tracker: Greenhouse, Lever, Ashby & Workable (`aiworkforcedata/ai-jobs-ats-tracker`) Actor Live jobs from 326 verified company career boards (AI labs, AI startups, big tech) via the official public Greenhouse, Lever, Ashby and Workable APIs. AI/ML role tagging, salary, remote, dedupe. Look up boards by company name. - **URL**: https://apify.com/aiworkforcedata/ai-jobs-ats-tracker.md - **Developed by:** [AI Workforce Data](https://apify.com/aiworkforcedata) (community) - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing $2.00 / 1,000 job results 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 Track who is hiring for AI, from the source. This Actor reads the **official public job-board APIs** that companies publish for their own career pages, so there are no logins, no proxies and no anti-bot workarounds. - **Company-name lookup:** type "Anthropic" or "Hugging Face" and the Actor finds the board (greenhouse:anthropic, workable:huggingface). Results are cached. - **Curated default list:** 326 boards verified on 2026-10-19 (154 Greenhouse, 151 Ashby, 19 Lever, 2 Workable). - **AI/ML tagging:** `is_ai_role`, `ai_role_category`, `ai_skills`, and `ai_tag_basis` (why it was tagged). - **Salary:** min/max/currency where the employer publishes it (53% of jobs in our test run). - **Dedupe:** drops repeated IDs and the same title+location cross-posted on one board. Real test run (2026-10-19, default list): 28,844 jobs, of which 2,938 were AI-tagged and 15,245 had a salary. 326 boards ran with 0 errors in 423 s. ### Input | Field | Type | Default | Notes | |---|---|---|---| | `companies` | string\[] | – | Plain names, resolved to boards | | `boards` | string\[] | – | `ats:token`, e.g. `greenhouse:anthropic`, `lever:palantir`, `ashby:openai`, `workable:huggingface` | | `onlyAiRoles` | bool | false | Output only AI/ML roles | | `postedWithinDays` | int | 0 | 0 = no filter | | `includeDescription` | bool | false | Plain-text description | | `maxItems` | int | 500 | 500 jobs ≈ $1. Set 0 for unlimited (full list ≈ 29k jobs ≈ $58) | | `requestDelaySecs` | number | 2 | Per-host politeness delay (≥1, ≥ robots Crawl-delay) | Leave `companies` and `boards` empty to use the curated list. ### Output (one dataset item per job) `job_id, source_ats, company, company_board, title, department, team, location, locations, country, remote, workplace_type, employment_type, seniority, is_ai_role, ai_role_category, ai_tag_basis, ai_skills, salary_min, salary_max, salary_currency, posted_at, updated_at, job_url, apply_url, scraped_at, content_hash, dedupe_key`. A `RUN_SUMMARY` key-value record lists counts per board, resolved and unresolved companies, and errors. ### Examples ```json {"companies": ["Anthropic", "Hugging Face"], "onlyAiRoles": true} {"boards": ["ashby:openai", "greenhouse:databricks"], "postedWithinDays": 7} {} // curated list, stops at the default 500 jobs, about $1 {"maxItems": 0} // whole curated list, about 28.8k jobs, about $57.69 ``` ### Pricing Pay per event: **$0.002 per job in the output** (`job-result`), with no start fee. The default `maxItems` of 500 caps a run at about $1. Your run's maximum-charge setting is always respected; the Actor stops cleanly when it is reached. ### Legal & compliance The Actor reads only the public job-board endpoints that employers publish for distributing their postings: Greenhouse Job Board API, Lever Postings API, Ashby public posting API, and Workable public widget API. It checks robots.txt and honors Crawl-delay, rate-limits each host, and never logs in, solves captchas, rotates proxies, or collects personal data. Job postings remain the property of the employers. ### FAQ - **A company is missing?** Add it under Company names; the run summary shows which names didn't resolve. - **Data freshness:** live on every run; `posted_at` and `updated_at` come from the employer's ATS. - **Is AI tagging perfect?** No. It is rule-based, and `ai_tag_basis` shows why each job was tagged. # Actor input Schema ## `companies` (type: `array`): Plain company names (e.g. Anthropic, Stripe). Each is resolved to its Greenhouse, Lever, Ashby or Workable board by probing the official public endpoints with likely slugs. Unresolved names are listed in the RUN_SUMMARY record. Results are cached for 7 days (unresolved for 1 day). If Company names and Job boards are both empty, the built-in curated list of 326 verified boards is used. ## `boards` (type: `array`): One entry per company board, as ats:token. ats is greenhouse, lever, ashby or workable. Token = the slug in the public board URL, e.g. greenhouse:anthropic (job-boards.greenhouse.io/anthropic), lever:palantir (jobs.lever.co/palantir), ashby:openai (jobs.ashbyhq.com/openai), workable:huggingface (apply.workable.com/huggingface). Leave both Company names and Job boards empty to use the built-in curated list of verified boards. ## `onlyAiRoles` (type: `boolean`): Output only jobs tagged is_ai_role = true. ## `postedWithinDays` (type: `integer`): 0 = no date filter. Jobs without a posted date are kept. ## `includeDescription` (type: `boolean`): Add the plain-text job description to each item (larger output). ## `maxItems` (type: `integer`): Maximum jobs to output (each output job = one $0.002 'job-result' event, so 500 ≈ $1). 0 = no limit: the full curated list is ~29k jobs ≈ $58. Your run's max-charge limit is always respected. ## `requestDelaySecs` (type: `number`): Politeness delay between requests to the same host. Never lower than the host's robots.txt Crawl-delay. ## Actor input object example ```json { "companies": [ "Anthropic", "Stripe", "OpenAI", "Hugging Face" ], "onlyAiRoles": false, "postedWithinDays": 0, "includeDescription": false, "maxItems": 500, "requestDelaySecs": 2 } ``` # 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 '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "companies": [ "Anthropic", "Stripe", "OpenAI", "Hugging Face" ], "maxItems": 500 }; // Run the Actor and wait for it to finish const run = await client.actor("aiworkforcedata/ai-jobs-ats-tracker").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 '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "companies": [ "Anthropic", "Stripe", "OpenAI", "Hugging Face", ], "maxItems": 500, } # Run the Actor and wait for it to finish run = client.actor("aiworkforcedata/ai-jobs-ats-tracker").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 '{ "companies": [ "Anthropic", "Stripe", "OpenAI", "Hugging Face" ], "maxItems": 500 }' | apify call aiworkforcedata/ai-jobs-ats-tracker --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,aiworkforcedata/ai-jobs-ats-tracker" } } } ``` 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 ` 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/W02BPs3FQMOXB14Nf/builds/cXEGv7lYX13QTFiS9/openapi.json