# Company Jobs Scraper — Greenhouse Lever Ashby Workable Workday (`nomad-agent/company-careers-bundle`) Actor Turn a list of companies into their live job postings. This ATS job scraper probes six boards per company — Greenhouse, Lever, Ashby, Workable, SmartRecruiters and Workday — and returns one merged, deduped dataset: title, company, location, remote, salary and apply URL. No per-ATS setup. - **URL**: https://apify.com/nomad-agent/company-careers-bundle.md - **Developed by:** [Nomad.Dev](https://apify.com/nomad-agent) (community) - **Categories:** Jobs, Lead generation, MCP servers - **Stats:** 1 total users, 1 monthly users, 75.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $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/platform/actors/running/actors-in-store#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 ## Company Jobs Scraper — Greenhouse Lever Ashby Workable Workday > **Claude / Codex skill to describe and setup this actor: [SKILL.md](https://github.com/Exdenta/OinkAIJobSearch/blob/main/skill/company-careers-bundle/SKILL.md)** One input — a list of companies. This ATS job scraper auto-detects each company's ATS across **six providers** (Greenhouse, Lever, Ashby, Workable, SmartRecruiters and Workday), pulls every live posting through official public APIs and returns a single deduped dataset. No login, no proxies, no per-ATS setup. ### How ATS detection works You pass company slugs — the Actor probes each company on Greenhouse, Lever, Ashby, Workable and SmartRecruiters (one API request per ATS; the fetch itself is the probe). Whichever board answers is fetched in full; companies found nowhere are logged and skipped. Everything is merged and cross-source-deduped by URL into one dataset. Use `atsProviders` to skip ATS you know a company isn't on — fewer providers probed per company means fewer upstream requests and a faster run. Each ATS fails open independently: if one provider's API errors, the run keeps going on the others (and the error surfaces as a dataset row, not a run failure). #### Workday needs a full URL Greenhouse, Lever, Ashby, Workable and SmartRecruiters are addressed by a bare company slug. **Workday is the exception**: its API is keyed by datacenter + career-site (e.g. `acme.wd1.myworkdayjobs.com` / site `External`), which a bare slug can't express. To include a Workday board, pass its full careers URL in `companies`, e.g. `https://acme.wd1.myworkdayjobs.com/en-US/External` — the Actor decodes the tenant, datacenter and site from it. A bare slug is simply a Workday probe miss (the other five ATS still run for it). ### Input | Field | Type | Default | Description | |---|---|---|---| | `companies` | array | — | Company slugs (full board URLs also accepted). Slugs are probed on every selected ATS; misses are just logged. For **Workday**, pass the full careers URL (see above). Optional if you use `presetLists`. | | `presetLists` | array (multi-select) | — | Curated company groups (`ai-labs`, `tech-unicorns`, `devtools-infra`) — pick one to run without your own slug list. Merged + deduped with `companies`. | | `atsProviders` | array (multi-select) | all 6 (`greenhouse`, `lever`, `ashby`, `workable`, `smartrecruiters`, `workday`) | Restrict which ATS get probed per company. | | `keyword` | string | — | Case-insensitive substring match on the job title. | | `titleExclude` | array | — | Drop postings whose title contains any of these substrings (case-insensitive). | | `locationFilter` | string | — | Case-insensitive substring match on the location. | | `postedSince` | integer | — | Keep only postings first published within this many days. Postings with no posting date are dropped when this is set. | | `remoteOnly` | boolean | `false` | Keep only postings the source ATS flags as remote. Greenhouse-hosted companies never match this filter — see FAQ. | | `includeDescription` | boolean | `true` | Include a plain-text description snippet per posting. | | `maxItemsPerCompany` | integer | `100` | Cap postings returned per company (0 = no cap). Each result is a billed event. If the cap actually cuts postings for a company, one extra dataset row flags it (`warnings: ["truncated ..."]`) — see "Warning rows". | | `maxItems` | integer | `200` | Hard cap on total postings returned (0 = no cap). Each result is a billed event. If the cap actually cuts postings, one extra dataset row flags it (`warnings: ["truncated ..."]`) — see "Warning rows". | | `onlyNewSinceLastRun` | boolean | `false` | Delta/monitoring mode: only output postings not seen on a previous run made with this flag on (see "Delta mode / monitoring"). | | `aiEnrichment` | boolean | `false` | Adds `aiKeySkills`/`aiExperienceLevel`/`aiWorkArrangement`/`aiVisaSponsorship` per posting via the Anthropic or Mistral API — BYOK (see "AI enrichment"). | | `aiProvider` | string | `anthropic` | Which AI provider runs enrichment: `anthropic` (default, uses `anthropicApiKey`) or `mistral` (uses `mistralApiKey`). | | `anthropicApiKey` | string (secret) | — | Your Anthropic API key. Only used when `aiEnrichment` is on and `aiProvider` is `anthropic`; billed separately by Anthropic, not by this Actor. | | `aiModel` | string | `claude-haiku-4-5-20251001` | Claude model for AI enrichment (when `aiProvider` is `anthropic`): `claude-haiku-4-5-20251001` (fast/cheap) or `claude-sonnet-4-5` (higher quality). | | `mistralApiKey` | string (secret) | — | Your Mistral API key. Only used when `aiEnrichment` is on and `aiProvider` is `mistral`; billed separately by Mistral, not by this Actor. | | `mistralModel` | string | `mistral-small-latest` | Mistral model for AI enrichment (when `aiProvider` is `mistral`): `mistral-small-latest` (default, fast/cheap — matches larger Mistral models on this task), `mistral-medium-latest`, or `mistral-large-latest`. | | `concurrency` | integer | `8` | Companies fetched in parallel (advanced). | ### What company career pages data does this scraper extract? One flat JSON record per live posting: | Field | Meaning | |---|---| | `ats` | Which ATS actually served this posting — `"greenhouse"`, `"lever"`, `"ashby"`, `"workable"`, `"smartrecruiters"` or `"workday"` | | `company` | Real company display name, resolved per-ATS (falls back to the input slug / Workday tenant if unresolvable) | | `id` | Posting ID from the source ATS | | `title` | Job title as posted | | `department` | Department or team where provided | | `location` | Location text (may include remote hints) | | `locations` | Array of location strings (usually one element mirroring `location`) — stable structured shape across the ATS family | | `city` / `region` / `country` | Structured location breakdown — populated for `ats: "smartrecruiters"` records, `null` for the other ATS (which expose only a single location string) | | `url` | Direct link to the posting | | `postedAt` | First-published date (`YYYY-MM-DD`) where provided. For Workday, derived from the board's relative "Posted N days ago" text (imprecise `30+ days` forms are left blank rather than guessed) | | `employmentType` | Employment type where the source ATS provides one — populated for Lever/Ashby/SmartRecruiters; always `null` for `greenhouse`/`workable`/`workday` | | `remote` | `true`/`false`/`null` faithful tri-state — always `null` for `ats: "greenhouse"` (no such signal); genuine `true`/`false` for Lever/Ashby/Workable/SmartRecruiters/Workday when the source states it | | `snippet` | Plain-text description excerpt (optional). Always empty for `smartrecruiters`/`workday` — their list APIs carry no description | | `salary` | Compensation display text, or `null` — populated only for `ats: "ashby"`/`"lever"` records where the company discloses it; always `null` for `greenhouse`/`workable`/`smartrecruiters`/`workday` (no compensation exposed) | | `salaryMin` / `salaryMax` | Structured salary range bounds, or `null` | | `salaryCurrency` | 3-letter currency code (e.g. `"USD"`), or `null` | | `salaryPeriod` | Pay period the range covers (`"year"`, `"hour"`, etc.), or `null` | | `hasEquity` | `true`/`false` only for `ats: "ashby"` records that disclose compensation (`true` when it includes an equity component); `null` everywhere else — never guessed | | `globalId` | Stable composite id `::` — unique across the whole dataset even when the same company appears on two ATS | | `warnings` | Array of data-quality notes for this record (e.g. `["postedAt missing"]`); empty array when there's nothing to flag | | `isNew` | Only present when `onlyNewSinceLastRun` is on — always `true` (already-seen postings are dropped, never emitted with `isNew: false`) | | `isClosed` | Only present (`true`) on delta-mode diagnostic rows for a posting seen on a prior run that has since disappeared — see "Delta mode / monitoring" | | `aiKeySkills` | Only present when `aiEnrichment` is on — array of skills/technologies explicitly named in the posting text, never invented | | `aiExperienceLevel` | Only present when `aiEnrichment` is on — one of `entry`/`mid`/`senior`/`lead`/`unknown` | | `aiWorkArrangement` | Only present when `aiEnrichment` is on — one of `onsite`/`hybrid`/`remote`/`unknown` | | `aiVisaSponsorship` | Only present when `aiEnrichment` is on — `true`/`false` only if the posting explicitly states a policy, otherwise `null` | ### How to scrape company career pages with this Actor 1. Enter one or more **company slugs** (`stripe`, `duolingo`, `openai`, `netguru`) — or select a `presetLists` group. Use the company's careers-page slug. When unsure, pass your best guess — slugs are probed on all selected ATS providers and misses are just logged. For Workday boards, pass the full careers URL instead of a slug. 2. Optionally restrict `atsProviders`, and set `keyword` / `titleExclude` / `locationFilter` / `postedSince` / `remoteOnly` / caps. 3. Run and export JSON, CSV or Excel — or call it over the API: ```python from apify_client import ApifyClient client = ApifyClient("") run = client.actor("nomad-agent/company-careers-bundle").call(run_input={ "companies": ["stripe", "duolingo", "openai", "netguru"], "keyword": "engineer", }) for item in client.dataset(run["defaultDatasetId"]).iterate_items(): print(item["company"], "|", item["title"], item["url"]) ``` ```bash curl -X POST \ "https://api.apify.com/v2/acts/nomad-agent~company-careers-bundle/run-sync-get-dataset-items?token=" \ -H "Content-Type: application/json" \ -d '{"companies": ["stripe", "duolingo", "openai", "netguru"]}' ``` ### Output example ```json { "ats": "lever", "company": "Mistral AI", "id": "7894fd8a-ffc9-4c89-87f0-f8a7b695cf01", "title": "Account Executive – AI for Citizens", "department": "Business", "location": "Paris", "url": "https://jobs.lever.co/mistral/7894fd8a-ffc9-4c89-87f0-f8a7b695cf01", "postedAt": "2025-07-28", "employmentType": "Full-time", "remote": false, "snippet": "We are hiring an Account Executive...", "salary": null, "salaryMin": null, "salaryMax": null, "salaryCurrency": null, "salaryPeriod": null, "globalId": "lever:mistral:7894fd8a-ffc9-4c89-87f0-f8a7b695cf01", "warnings": [] } ``` A `stripe`-sourced record in the same run would instead carry `"ats": "greenhouse"` with `"employmentType": null` and `"remote": null` — Greenhouse's API doesn't expose either field. Check `ats` per record if you need to know which fields to trust. Every record carries the five `salary*` keys regardless of `ats`, for a stable merged schema — only Ashby/Lever records ever have them populated, e.g. `"salary": "$185K - $325K", "salaryMin": 185000, "salaryMax": 325000, "salaryCurrency": "USD", "salaryPeriod": "year"` for an Ashby posting whose company opted in to compensation disclosure. ### Delta mode / monitoring Set `onlyNewSinceLastRun: true` to turn this Actor into a "what's new" monitor. Postings already seen on a previous run made with this flag on are dropped before push — you are not billed for them, so pairing this with an Apify schedule (cron) means every run only returns, and only charges for, postings that showed up since the last flagged run. How it works: seen postings are tracked in a dedicated key-value store, keyed by each posting's `globalId`, capped at roughly 50,000 entries (oldest evicted first). The first run made with the flag on has nothing to compare against yet, so it emits everything — all `isNew: true`. Every emitted record gets `isNew: true` stamped on it; there's no `isNew: false` in the output, since unseen postings just aren't included. **Closed-posting detection:** in delta mode, a posting that was seen on a previous flagged run but has since disappeared from its board (filled/removed) is reported as one extra diagnostic row with `isClosed: true` carrying its `ats`/`company`/`id`/`globalId`. This is scoped to companies actually fetched this run and to the ATS you probed, so a transient fetch failure or a narrowed provider/company list never falsely marks postings closed. Each closed posting is reported once. These rows are **not billed**. Runs made with the flag off never read or write this cache — turning it on and off between runs is safe and has no side effects on normal runs. ### Preset company lists No slug list yet? Select one or more `presetLists` groups and the Actor runs against a curated set of well-known boards (verified live) without any `companies` input: | Preset | Companies (sample) | |---|---| | `ai-labs` | OpenAI, Anthropic, Mistral, Cohere, Hugging Face, ElevenLabs, Together | | `tech-unicorns` | Stripe, Databricks, Figma, Ramp, Notion, Coinbase, Reddit, Discord, … | | `devtools-infra` | GitLab, Vercel, Confluent, CockroachLabs, Postman, Gusto, Samsara, … | Presets are merged with (and deduped against) any `companies` you pass. If neither `companies` nor `presetLists` is provided, the Actor falls back to a built-in default spread so a first run works out of the box. ### AI enrichment Turn on `aiEnrichment` and supply your own `anthropicApiKey` (or `mistralApiKey`, with `aiProvider: "mistral"`) to add four AI-extracted fields to every posting. Enrichment runs once on the final merged, deduped set of postings across all probed ATS providers — not once per ATS — so you're never billed extra provider calls just because a company happens to be findable on more than one board. | Field | Meaning | |---|---| | `aiKeySkills` | Specific skills/technologies/tools explicitly named in the title or description — the model is instructed to never invent one. | | `aiExperienceLevel` | One of `entry` / `mid` / `senior` / `lead` / `unknown`. | | `aiWorkArrangement` | One of `onsite` / `hybrid` / `remote` / `unknown`. | | `aiVisaSponsorship` | `true` / `false` only when the posting explicitly states a sponsorship policy, otherwise `null`. | The extraction prompt is explicit about never guessing: when the text doesn't clearly support a value you get `"unknown"` / `null` / an empty array, not a fabricated answer. Pick the model with `aiModel` (Anthropic: `claude-haiku-4-5-20251001` default, fast/cheap, or `claude-sonnet-4-5` higher quality) or `mistralModel` (Mistral: `mistral-small-latest` default — matches larger Mistral models on this task, `mistral-medium-latest`, `mistral-large-latest`). Postings are batched (~12 per call) through whichever provider's API you picked (`aiProvider`). **Your Anthropic or Mistral API key is billed separately by that provider, not by this Actor.** Rough cost with Haiku or Mistral Small: enriching 100 postings runs well under $0.05 in provider token spend (short prompts, small JSON replies); Sonnet/Mistral Large cost roughly 4-5x that for the same batch. Enrichment needs a posting's description text even when you have `includeDescription` off — this Actor fetches it internally for enrichment either way, then still honors your `includeDescription` choice for what actually ends up in the output `snippet` field. If `aiEnrichment` is on but no matching key is available (`anthropicApiKey`/`ANTHROPIC_API_KEY` for `aiProvider: "anthropic"`, or `mistralApiKey`/`MISTRAL_API_KEY` for `aiProvider: "mistral"`), enrichment is skipped: you get one extra dataset row explaining why (`warnings: ["aiEnrichment skipped: no anthropicApiKey or mistralApiKey provided"]`), a run status message, and every other posting is still returned normally, just without the `ai*` fields. This is the same class of field fantastic-jobs' `career-site-api` prices a whole tier on (`ai_key_skills`, work arrangement, visa signals) — comparable output here, opt-in and BYOK instead of bundled into every row's price. ### Warning rows Alongside normal posting records, this Actor can push a handful of extra rows that are all `null` except `company`/`ats`/`warnings` — same flat schema as a posting record, so a dataset-only consumer (no access to the run log) still sees every problem: | Trigger | Example `warnings` | |---|---| | A requested company slug 404'd (or hard-failed) on every ATS probed | `["not found on any ATS probed (greenhouse/lever/ashby/workable/smartrecruiters/workday): 'acme-corp' (404 on every probe)"]` | | `maxItemsPerCompany` actually cut postings for one company | `["truncated for 'acme-corp': maxItemsPerCompany=100 returned 100 of 137 matching postings — raise maxItemsPerCompany to get the rest"]` | | `maxItems` actually cut the total run | `["truncated: maxItems=200 returned 200 of 340 matching postings — raise maxItems to get the rest"]` | | `aiEnrichment` requested but no API key available | `["aiEnrichment skipped: no anthropicApiKey or mistralApiKey provided"]` | | A posting seen last run has disappeared (delta mode) | row carries `isClosed: true` + the posting's `globalId`; `warnings` empty | | An unexpected run error (kept SUCCEEDED, not billed) | `["run error (…): … — no further postings returned; see the run log. This row is not billed."]` | None of these rows are billed as a `result` event — only genuine postings are. Pass 50 company slugs in one run and you can tell exactly which ones need fixing straight from the dataset, instead of hunting through the run log. ### Integrations Export results as JSON, CSV or Excel/XLSX, or pipe them straight into Make, Zapier or n8n. Call this Actor synchronously with `run-sync-get-dataset-items`, or plug it into any AI agent through the [Apify MCP server](https://apify.com/apify/actors-mcp-server). ### Pricing Pay per event: a small **per-run start fee** plus a flat **price per posting returned** — current rates are on this Actor's Pricing tab. No subscription, no minimum: pay only for what you fetch, and cap spend per run with `maxItems` / `maxItemsPerCompany`. Warning/diagnostic rows are never billed. If you turn on `aiEnrichment`, your Anthropic or Mistral key is billed separately by that provider for the enrichment calls themselves — see "AI enrichment" above for a rough per-100-postings cost estimate. Delta mode (`onlyNewSinceLastRun`) only *reduces* cost: already-seen postings are dropped before the billed push step. ### Use cases - Watchlists: monitor hiring across target/competitor/portfolio companies - Recruiting agencies: one feed over every client's ATS - VC talent teams: portfolio-wide open-roles dashboards - Job boards that aggregate by company rather than by board ### FAQ **Is it legal to scrape company career pages?** The data comes from the ATS providers' official, public, unauthenticated JSON APIs — the same data any visitor sees on the company's careers page. Review the providers' terms for your use case. **Do I need an API key or login?** No. These are public job-board APIs — no authentication of any kind. **What if a company isn't found?** The run continues with the other companies, and — since 2026-07 — you also get one dataset row for it: `{"company": "", "ats": "...", "warnings": ["not found on any ATS probed (...): '' (404 on every probe)"]}` (or `"fetch failed on every ATS probed ..."` for a network/5xx failure rather than a clean 404). Previously this was only visible in the run log, easy to miss across a 50-slug batch. Full board URLs are also accepted and reduced to slugs automatically. See "Warning rows". **Why do some records have `remote: null` and `employmentType: null`?** Those are `ats: "greenhouse"` records. Greenhouse's public API never exposes a remote/workplace-type or employment-type field, so this Actor reports `null` rather than guessing. Lever/Ashby/Workable records populate both fields whenever the source states them. **How fresh is the data?** Every run hits the ATS APIs live. No caching layer in between. **Something broken or missing?** Open an issue on the Actor's **Issues** tab — it is monitored and fixes ship fast. ### Related Actors - [Greenhouse Jobs Scraper — Company Job Boards](https://apify.com/nomad-agent/greenhouse-jobs-scraper) - [Lever Jobs Scraper — Company Job Postings API](https://apify.com/nomad-agent/lever-jobs-scraper) - [Ashby Jobs Scraper — Company Job Boards API](https://apify.com/nomad-agent/ashby-jobs-scraper) - [Workable Jobs Scraper — Company Job Boards](https://apify.com/nomad-agent/workable-jobs-scraper) - [Web Developer Jobs Scraper — 10 Boards in One](https://apify.com/nomad-agent/web-dev-bundle) - [LinkedIn Jobs Scraper — No Login, No Cookies](https://apify.com/nomad-agent/linkedin-scraper) *** **From the maker of [Oink](https://github.com/Exdenta/OinkAIJobSearch)** — an open-source, AI-powered job-search bot for Telegram that runs on these Actors. [Try the free bot](https://t.me/job_search_everyday_bot), get a managed instance at [oinkjobsearch.com](https://oinkjobsearch.com), or browse the [full catalog of 50+ Actors](https://apify.com/nomad-agent). # Actor input Schema ## `companies` (type: `array`): Company slugs as used on their ATS board (full board URLs also accepted). Use the company's careers-page slug. When unsure, pass your best guess — slugs are probed on the selected ATS providers and misses are just logged. Workday is keyed by datacenter + career-site, so a bare slug can't reach it: to include a Workday board pass its full careers URL, e.g. https://acme.wd1.myworkdayjobs.com/en-US/External. Leave empty to use presetLists or the built-in default list. ## `presetLists` (type: `array`): Curated company groups — pick one or more to run without supplying your own slug list. Their companies are merged with (and deduped against) companies. ## `atsProviders` (type: `array`): Restrict which ATS this Actor probes per company. Fewer providers means fewer upstream requests per company — faster and slightly cheaper runs. Leave empty to probe all six (default). Note: Workday only activates for entries passed as a full Workday careers URL (see Companies). ## `keyword` (type: `string`): Optional case-insensitive substring match on the job title (e.g. engineer). ## `titleExclude` (type: `array`): Drop postings whose title contains any of these substrings (case-insensitive). Example: \[intern, staffing]. ## `locationFilter` (type: `string`): Optional case-insensitive substring match on the location (e.g. remote, london). ## `postedSince` (type: `integer`): Only keep postings first published within this many days. Leave empty (or 0) for no date filter. When this is set, postings the source didn't give a posting date for are dropped rather than guessed at. ## `remoteOnly` (type: `boolean`): Keep only postings the source ATS explicitly flags as remote. Greenhouse never reports a remote flag, so companies hosted only on Greenhouse yield zero results with this on; Lever/Ashby/Workable results are filtered normally. ## `includeDescription` (type: `boolean`): Include a plain-text description snippet per posting. Turn off for lighter, faster output. ## `maxItemsPerCompany` (type: `integer`): Cap postings returned per company. Each posting returned is a billed result, so this keeps one large board from dominating the run's cost. 0 = no cap. ## `maxItems` (type: `integer`): Hard cap on total postings returned across all companies. Each posting returned is billed as a paid result — raise this only as high as you actually need. 0 = no cap (not recommended for large company lists). ## `onlyNewSinceLastRun` (type: `boolean`): Delta/monitoring mode: only output postings not seen in a previous run that also had this flag on. Already-seen postings are dropped before push (not billed), so this is the cheapest way to run this Actor on a cron schedule and only pay for genuinely new postings. State is tracked per Actor in a dedicated key-value store, keyed by each posting's globalId. See README “Delta mode / monitoring”. ## `aiEnrichment` (type: `boolean`): Adds aiKeySkills / aiExperienceLevel / aiWorkArrangement / aiVisaSponsorship to every posting via the Anthropic or Mistral API (pick which below). Requires your own API key for the provider you pick — billed separately by that provider, not by this Actor (see README “AI enrichment”). If turned on without a matching key, enrichment is skipped (with a warning) and postings are still returned normally, without the ai\* fields. ## `aiProvider` (type: `string`): Which AI provider runs enrichment (only relevant when “AI enrichment” is on). anthropic (default) uses Claude via anthropicApiKey. mistral uses a Mistral model via mistralApiKey instead — pick this if you'd rather bring a Mistral key than an Anthropic one. openai uses a GPT model via openaiApiKey. ## `anthropicApiKey` (type: `string`): Your Anthropic API key (sk-ant-…). Only used when “AI enrichment” is on and aiProvider is anthropic; billed separately by Anthropic. Not required unless aiEnrichment is on. ## `aiModel` (type: `string`): Claude model used for AI enrichment when aiProvider is anthropic (only relevant when “AI enrichment” is on). Haiku is fast and inexpensive; Sonnet gives higher-quality extraction on longer, more nuanced descriptions. ## `mistralApiKey` (type: `string`): Your Mistral API key. Only used when “AI enrichment” is on and aiProvider is mistral; billed separately by Mistral. Not required unless aiEnrichment is on with aiProvider=mistral. ## `mistralModel` (type: `string`): Mistral model used for AI enrichment when aiProvider is mistral (only relevant when “AI enrichment” is on). Small is the default — testing found it matches larger Mistral models on this extraction task (small, well-scoped fields) at a fraction of the cost. ## `openaiApiKey` (type: `string`): Your OpenAI API key (sk-…). Only used when “AI enrichment” is on and aiProvider is openai; billed separately by OpenAI. Not required unless aiEnrichment is on with aiProvider=openai. ## `openaiModel` (type: `string`): OpenAI model used for AI enrichment when aiProvider is openai (only relevant when “AI enrichment” is on). Defaults to gpt-4.1-mini — cheap, fast and ample for this extraction task. Any chat-completions model works, including the gpt-5 family (e.g. gpt-5.4-mini). ## `concurrency` (type: `integer`): How many companies to fetch at the same time. Higher is faster but hits the source APIs harder — the default is a safe, fast setting for almost every run. ## Actor input object example ```json { "companies": [ "stripe", "duolingo", "openai", "netguru" ], "atsProviders": [ "greenhouse", "lever", "ashby", "workable", "smartrecruiters", "workday" ], "titleExclude": [ "intern", "staffing" ], "remoteOnly": false, "includeDescription": true, "maxItemsPerCompany": 100, "maxItems": 200, "onlyNewSinceLastRun": false, "aiEnrichment": false, "aiProvider": "anthropic", "aiModel": "claude-haiku-4-5-20251001", "mistralModel": "mistral-small-latest", "openaiModel": "gpt-4.1-mini", "concurrency": 8 } ``` # Actor output Schema ## `dataset` (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": [ "stripe", "duolingo", "openai", "netguru" ], "titleExclude": [ "intern", "staffing" ] }; // Run the Actor and wait for it to finish const run = await client.actor("nomad-agent/company-careers-bundle").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": [ "stripe", "duolingo", "openai", "netguru", ], "titleExclude": [ "intern", "staffing", ], } # Run the Actor and wait for it to finish run = client.actor("nomad-agent/company-careers-bundle").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"]) for item in client.dataset(run["defaultDatasetId"]).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": [ "stripe", "duolingo", "openai", "netguru" ], "titleExclude": [ "intern", "staffing" ] }' | apify call nomad-agent/company-careers-bundle --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=nomad-agent/company-careers-bundle", "--header", "Authorization: Bearer " ] } } } ``` ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/TmG3tuikPbP8aNwoY/builds/WGhBeZFsH91cUgtb9/openapi.json