# PhD, Postdoc & Research Jobs Scraper: 10 Boards in One (`nomad-agent/researcher-bundle`) Actor $0.2/1K jobs | PhD, postdoc and research jobs from 10 sources in one run: EURAXESS, EURES, jobs.ac.uk, AcademicPositions, ReliefWeb, UN Careers, LinkedIn and more, with full descriptions. Default search keeps research roles. No login or API key. - **URL**: https://apify.com/nomad-agent/researcher-bundle.md - **Developed by:** [Nomad.Devs](https://apify.com/nomad-agent) (community) - **Categories:** Jobs - **Features:** Limited permissions - **Stats:** 33 total users, 7 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $0.10 / 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. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. 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 ## PhD, Postdoc & Research Jobs Scraper: 10 Boards in One $0.2/1K jobs | PhD, postdoc and research jobs from 10 sources in one run: EURAXESS, EURES, jobs.ac.uk, AcademicPositions, ReliefWeb, UN Careers, LinkedIn and more, with full descriptions. Default search keeps research roles. No login or API key. Independent, unofficial tool. Not affiliated with or endorsed by the job boards and sites it reads. ### PhD, Postdoc & Research Jobs Bulk Scraper Our scraper collects PhD, postdoc and research jobs from 10 sources in one run and lets you filter by keyword, location, work arrangement, employment type and posting age. Every row carries the complete original description in text and HTML, the deadline when the source publishes one, and the link to the original posting. If you pass no `queries`, it searches 16 default research phrases and keeps a stored posting only when its job title contains one (like "postdoc", "PhD", "research fellow" or "professor"). EURAXESS, Ikerbasque and Universitat de Barcelona are research-focused boards, so they are kept whole. LinkedIn is searched live and keeps its own ranking. Your own `queries` search both title and description, and an empty list returns every posting. It is ideal for researcher job alerts, university career services and academic hiring analytics. - Want jobs from every kind of board, not only research? Use [All Jobs Scraper (No Login) + 21 Boards in One](https://apify.com/nomad-agent/all-jobs-scraper) (21 boards). - Need one research board with its own source-specific page? Use [EURAXESS Jobs Scraper — EU Research Positions](https://apify.com/nomad-agent/euraxess-scraper), [jobs.ac.uk Scraper — UK Academic, Postdoc & Research Jobs](https://apify.com/nomad-agent/jobs-ac-uk-scraper), [AcademicPositions Jobs Scraper (No Login) + Full Text](https://apify.com/nomad-agent/academicpositions-scraper) or [ReliefWeb Humanitarian & NGO Jobs | Full Descriptions](https://apify.com/nomad-agent/reliefweb-scraper). They are narrower than this bundle. - Mostly Europe? [Europe Jobs Scraper (No Login) + 14 Boards](https://apify.com/nomad-agent/europe-jobs-bundle) covers European boards across all job types, not only research. - Browse all our job-board scrapers: https://apify.com/nomad-agent #### Key Benefits - No login or API key: nothing to set up, no account of yours at risk, and no cookies to hand over. - Low pricing: **$0.20 per 1,000 jobs** ($0.0002 per job), with lower rates on Scale and Business plans ($0.15 and $0.1 per 1,000), plus $0.00005 per run start. - Full descriptions only: a posting with a missing or truncated description is never returned. - Research roles by default: with no `queries`, a stored posting is kept only when its job title names research work (`postdoc`, `phd`, `research fellow`, `professor` and 12 more phrases). EURAXESS, Ikerbasque and Universitat de Barcelona are kept whole, and `queries: []` returns every posting. - Research boards first: academic boards (EURAXESS, jobs.ac.uk, AcademicPositions) sit next to UN and NGO boards, in one schema. - No repeats across runs: schedule the same search daily and get only postings you have not received yet. ### How It Works 1. Provide your search. Every filter is optional, and an empty list means no filter: - (optional) Search queries (e.g., `postdoc`). A posting matches when its title or description contains every word of a query, as whole words. Leave them out for the built-in research searches. - (optional) Locations (e.g., `Europe`, `DE`, `Berlin`). Countries match by name, code and native name, and `EU` and `Europe` cover their member countries. - (optional) Work arrangement (`remote`, `hybrid`, `onsite`) and employment type (`Full-time`, `Part-time`, `Contract`, `Internship`). - (optional) Posted within (e.g., `24h`, `7d`, `2w`). Default is `any`. 2. Set how many jobs you want with `maxItems`. 3. Click Start. The form opens with `Europe`, 20 jobs and the 16 built-in research searches in `queries`; keep them for the default scope, or empty the list to search every posting. More settings: - `maxItems` - Maximum number of jobs per run. Default is 200; `0`, or anything above 200, means 200. - `maxItemsPerSource` - Caps how many postings each board contributes. Default is 50, at most 200. `maxItems` then keeps the newest postings across all boards. - `dedupe` - On by default: postings already delivered to your Apify account for the same search are skipped. Set `dedupe.enabled` to `false` to get everything again, or set `dedupe.key` to keep separate alert histories. Run the same search twice and the second run returns only new postings, possibly none. That is the repeat suppression working; turn `dedupe` off to see every posting again. Coverage: EURAXESS, EURES, Ikerbasque, Impactpool, jobs.ac.uk, ReliefWeb, Universitat de Barcelona, UN Careers and AcademicPositions are served from verified postings, and LinkedIn is read live on every run. Each row keeps its own `source`. LinkedIn can be limited or blocked during a run. When that happens its rows are fewer than requested or missing, the other boards are still returned, `RUN-SUMMARY.unavailableSources` names LinkedIn, and the run is marked `partial`. When you set work arrangement or employment type, a posting whose source does not state that fact is left out. Salary and hiring contacts are filled only when the source publishes them (none of the 10 rows in our test run had either), so treat them as bonus fields. #### Data You'll Receive - Job details: title, complete description (text and HTML), locations, posting date, deadline (when published), work arrangement, employment types, salary (when published). - Employer: company name. - Links: original posting URL. - Hiring contacts: the people a source names, when it names any (otherwise an empty list). - Identity: `source` and a stable `id`, so you can deduplicate across runs. Rows use the `nomad-agent-job-row-v3` format, newest postings first. Unknown optional facts are `null`. #### Sample output data Here is an example job from this Actor (one row of our test run, description shortened): ```json { "schemaVersion": "nomad-agent-job-row-v5", "source": "euraxess", "id": "472376", "url": "https://euraxess.ec.europa.eu/jobs/472376", "title": "Science for policy researcher for soil nutrients, LUCAS soil monitoring and laboratory analysis", "company": "Joint Research Centre", "locations": [ "Ispra, Italy" ], "countryCodes": [ "IT" ], "applicantLocations": null, "postedAt": "2026-10-13", "deadline": "2026-11-09T09:36:11+00:00", "description": "Page contents Job Information Offer Description Where to apply Requirements Additional Information Work Location(s) Contact 13 Oct 2026 Job Information Organisation/Company Joint Research Centre Department Sustainable Resources Research Field Environmental science » Natural resources management Agri… [truncated for display]", "descriptionHtml": "
\n
\n
\n
\n
\n
External Assurance Engagement on the Empowerment Guarantee Fund (EGF) managed by the Iraqi Company for Bank Guarantees (ICBG)

\n

Introduction andBackground

\n

Iraq, including the Kurdistan Region of Iraq, has faced a series of compounding crises over the past decade, including armed conflict, the rise of ISIL, mass displacement, fiscal instabili… [truncated for display]", "workType": null, "salary": null, "employmentTypes": null, "hiringContacts": [] } ``` Retained dedupe history can suppress previously returned postings. Keep a stable key and save your own history; an unchanged rerun can return zero new rows. Recent PhD, postdoc and research jobs with complete original descriptions. Each row carries the source ID and URL, title, employer, locations, the original description as text and HTML, posting date, deadline, work arrangement, employment type, salary and the hiring contacts the source names, whenever the source publishes them. Unknown optional facts are `null`; an empty `locations` array means the source names no physical place, and an empty `hiringContacts` array means the source names nobody. `locations` is where the job is, `countryCodes` lists the countries of those places as ISO 3166-1 two-letter codes (`null` when no place has a known country), and `applicantLocations` is where an applicant may live, for example a remote job open only to residents of some countries: it is `null` when the source states nothing and `[]` when it states no restriction. `workType` is set only when the source names exactly one arrangement and is `null` when it names several, such as remote or hybrid; `locationTypes` matches a posting when any arrangement it names is selected. Coverage includes these public job sources: EURAXESS; EURES; Ikerbasque; Impactpool; jobs.ac.uk; ReliefWeb; Universitat de Barcelona; UN Careers; AcademicPositions. LinkedIn is also served, fetched live on every run. Each row keeps its own `source`. Every posting is verified before it is served. A posting with a missing, truncated or unverified description is never returned: every row has the full original text. LinkedIn results use the requested search filters. Each posting still has its full description or it is left out. LinkedIn may limit or block a run, so its rows can be fewer than requested or missing: the other boards are still returned, `RUN-SUMMARY.unavailableSources` names LinkedIn, and the run is marked `partial`. Without `queries` (or the older `keyword`), runs mostly return PhD, postdoc and research roles: the default `queries` are listed under Input, and a stored posting is kept only when its job title contains one of them. EURAXESS, Ikerbasque and Universitat de Barcelona are research-focused boards, so every posting they list is kept whatever its title. UN Careers, ReliefWeb and Impactpool list every kind of job, so few of their postings pass the title rule; use `queries: []` or your own `queries` to get all of them. An empty `queries` list (`queries: []`) returns every posting. LinkedIn is searched live and keeps its own ranking. LinkedIn is searched live for at most 6 combinations of query, location and work arrangement per run. With the default `queries` it searches a curated subset of them, `postdoc`, `phd`, `research fellow`, `research associate`, `research scientist` and `doctoral`, while the stored boards use all of them. Naming several `locations` or `locationTypes` shares the six searches, so each location gets fewer of those phrases: two locations get the first three each, three get the first two, and four to six get the first phrase only. With your own `queries`, or more than six locations and work arrangements together, combinations beyond the sixth are not searched: the last locations you list can get no LinkedIn rows, the run is marked `partial`, and `RUN-SUMMARY.unavailableSources` says how many combinations were searched. #### Input ```json {"schemaVersion": "nomad-agent-simple-inventory-search-v2", "queries": ["postdoc", "phd", "research fellow", "research associate", "research scientist", "doctoral", "researcher", "research assistant", "research engineer", "postdoctoral", "post-doc", "predoctoral", "doctorate", "doktorand", "professor", "lecturer"], "locations": ["Europe"], "locationTypes": ["remote"], "employmentTypes": [], "postedWithin": "7d", "maxItems": 200, "maxItemsPerSource": 50, "dedupe": {"enabled": true, "key": ""}} ``` Every filter is optional, and an empty list means no filter. Filters are applied to all available postings before `maxItems` is counted. - `queries`: a posting matches a query when its title or description contains every word of it, as whole words, ignoring case. A posting matches when any query matches. **Default:** a run that sets neither `queries` nor the older `keyword` searches for PhD, postdoc and research roles with these queries: `postdoc`, `phd`, `research fellow`, `research associate`, `research scientist`, `doctoral`, `researcher`, `research assistant`, `research engineer`, `postdoctoral`, `post-doc`, `predoctoral`, `doctorate`, `doktorand`, `professor`, `lecturer`. On the stored boards it also keeps only postings whose job title contains one of them, except on EURAXESS, Ikerbasque and Universitat de Barcelona, which are research-focused boards. Your own `queries` or `keyword` replace them and are matched in the title and the description, and an empty list means no query filter. - `locations`: a city, region, country name or two-letter ISO country code. Countries match by name, code and native name (`Germany`, `DE` and `Deutschland` find the same postings), and `EU` and `Europe` cover their member countries. - `locationTypes` (`remote`, `hybrid`, `onsite`) and `employmentTypes` (`Full-time`, `Part-time`, `Contract`, `Internship`): while one is set, a posting whose source does not state that fact is left out. - `postedWithin`: a positive duration in hours (`h`), days (`d`), weeks (`w`) or 30-day months (`m`), up to 36500 days, or `any`. Postings without a source date use the date they were first seen, which later refreshes never reset. - `maxItems` defaults to 200; 0, or anything above 200, means 200. - `maxItemsPerSource` (default 50, at most 200) caps how many postings each source contributes; `maxItems` then keeps the newest postings across all sources. - `dedupe` suppresses postings already delivered to the same Apify account for the same search; different filters keep separate histories. Set `dedupe.enabled` to `false` to get stateless results, or set `dedupe.key` to keep separate alert histories. #### Output One flat row per posting in the `nomad-agent-job-row-v5` format: `schemaVersion`, `source`, `id`, `url`, `title`, `company`, `locations`, `countryCodes`, `applicantLocations`, `postedAt`, `deadline`, `description`, `descriptionHtml`, `workType`, `salary`, `employmentTypes`, `hiringContacts`. `employmentTypes` lists the types the source states (`Full-time`, `Part-time`, `Contract`, `Internship`) or is `null`. `countryCodes` lists the countries of the job's places as ISO 3166-1 alpha-2 codes (for example `DE`, `FR`), in the same order as `locations`, each once. A code comes from the source if it states one, otherwise from the place label. It's `null` when no place has a known country (a remote job with no country, or an unidentifiable place) and never an empty list. A place without a known country adds nothing, so the list can name fewer countries than there are places. A posting stored on a single-country board with no place at all carries that board's country, so `locations` can be `[]` while `countryCodes` names one. Postings read live from LinkedIn's public pages always have `countryCodes: null`. Those pages give a place label but no country code, so only stored postings carry a code. The `locations` filter matches countries against these codes as well as names and text. `applicantLocations` lists the regions where the source says an applicant may live (for example `United States` for a remote job open to US residents), `null` when it states nothing and `[]` when it states no restriction. Each hiring contact has a `name`, and a `title` and `url` or `null`. Newest postings come first. A run summary, including any input field that was mapped or ignored, is written to the `RUN-SUMMARY` record of the run's key-value store. #### Changes - **November 2026: the default search keeps PhD, postdoc and research roles.** Previously a run with no search matched every posting on every board. Now it searches 16 built-in phrases, listed under Input, and keeps a stored posting only when its job title contains one of them. EURAXESS, Ikerbasque and Universitat de Barcelona are research-focused boards, so every posting they list is kept whatever its title. UN Careers, ReliefWeb and Impactpool list every kind of job, so few of their postings pass the title rule; use `queries: []` or your own `queries` to get all of them. Your own `queries` still match both title and description, an empty `queries` list (`queries: []`) still returns every posting, and LinkedIn is searched live for six of them. The built-in phrases are part of the repeat-delivery scope, so the first run without `queries` after this change can return postings you already received. - **November 2026: University of Copenhagen (Mathematical Sciences) removed.** Its collector has had no successful run for 10 days, so every run was marked `partial` and returned nothing from it. The Actor now reads 10 sources. Input, row format and pricing are unchanged. - **October 2026: `countryCodes` added (row v5).** Rows are now `nomad-agent-job-row-v5`: one new field, `countryCodes`, lists the ISO 3166-1 alpha-2 country codes of the job's places, in the order of `locations`, each once (`null` when no place has a known country, never an empty list). A code is the country the source states, or if it doesn't state one, the country read from the place label. A place whose country can't be determined adds nothing. Postings read live from LinkedIn carry `null`; its public pages show a place label but no country code. `locations` and `applicantLocations` are unchanged. Input, other fields, and pricing are unchanged. Integrations validating against the v4 schema must allow the new field and the new `schemaVersion`. - **October 2026: `applicantLocations` added (row v4).** Rows are now `nomad-agent-job-row-v4`: one new field, `applicantLocations`, lists where an applicant may live as the source states it (`null` when the source states nothing, `[]` when it states no restriction). `locations` is unchanged and still the physical place only; for a remote job open to some regions it is often `[]` while `applicantLocations` lists the regions. Input, other fields and pricing are unchanged. Integrations that validate rows against the v3 schema must allow the new field and the new `schemaVersion`. - **October 2026: LinkedIn is read live.** LinkedIn results reflect its current public job pages. Every row still has the complete description or is left out, and the other boards are unchanged. A LinkedIn failure no longer affects the other boards: the run is marked `partial` and `RUN-SUMMARY.unavailableSources` names it. Pricing is unchanged. - **October 2026: `recordType` removed.** `nomad-agent-job-row-v3` rows no longer include the `recordType` field, because every dataset row is a posting. Read `schemaVersion` instead. The `RUN-SUMMARY` record is unchanged. - **September 2026: search filters and richer rows.** The input (`nomad-agent-simple-inventory-search-v2`) adds `queries`, `locations`, `locationTypes` and `employmentTypes`, and `maxItemsPerSource` (default 50). Rows are now `nomad-agent-job-row-v3` and add `employmentTypes` and `hiringContacts`. Integrations that still send `keyword` or `location` keep working: those values become `queries` and `locations`, `remote: true` becomes `locationTypes: ["remote"]`, and other old fields are ignored with a note in `RUN-SUMMARY` instead of failing the run. Pricing is unchanged. - **Earlier:** this Actor moved to verified available postings in the shared simple job format, and every row includes the complete description. #### Fast setup and source code [Public repository](https://github.com/Exdenta/nomad-agent-job-scrapers) · [Agent setup skill](https://github.com/Exdenta/OinkAIJobSearch/blob/main/.agents/skills/public-apify-actors/SKILL.md). Use the Actor’s current input form for filters, or start with its documented API example. Select the `latest` build. Read the dataset together with the run summary: a successful status alone does not show that every source was reached. Restrictive filters or repeat-delivery suppression can produce zero results. ##### Observed output example Selected fields from a real source record inspected on 2026-10-03; consult the output schema for the full contract. Values change with the source. ```json { "schemaVersion": "nomad-agent-job-row-v3", "source": "linkedin", "id": "4455773999", "url": "https://www.linkedin.com/jobs/view/applied-scientist-fauna-at-amazon-4455773999", "title": "Applied Scientist, Fauna", "company": "Amazon", "locations": [ "Sunnyvale, CA" ], "postedAt": "2026-10-01", "deadline": null, "workType": null, "salary": null, "employmentTypes": [ "Full-time" ], "hiringContacts": [] } ``` #### Product guides and related tools - [Guide and starter input on nomadagent.dev](https://nomadagent.dev/actors/researcher-bundle) - [Product overview and public links](https://jobatlas.dev/actors/directory/source-jobs#nomad-agent-researcher-bundle) - [Public setup guide](https://github.com/Exdenta/jobatlas/blob/main/docs/public-actors-setup.md) - [Job Atlas job-data tools](https://jobatlas.dev/actors) - [Oink personal job alerts](https://oinkjobsearch.com/) - [Search ten job boards with one API call](https://oinkjobsearch.com/articles/search-ten-job-boards-with-one-api-call/) #### Current costs Current Actor event rates, checked 2026-10-16. USD; use the **Pricing** tab for your plan and later changes. | Event | Free | Bronze | Silver | Gold | Platinum | Diamond | |---|---:|---:|---:|---:|---:|---:| | Job result (`result`) | $0.0002 | $0.0002 | $0.00015 | $0.0001 | $0.0001 | $0.0001 | | Actor start (`actor-start`) | $0.00005 | $0.00005 | $0.00005 | $0.00005 | $0.00005 | $0.00005 | For example, 100 × `result`, 1 × `actor-start` totals **$0.02005 in Actor event charges on Free**. This is an arithmetic example, before any waiver; actual charged events depend on the run and selected options. It is not a promise of output or a charge for simply setting an item cap. Your total is the charged Actor events, plus platform usage **only if this Actor’s Pricing tab bills it separately**, plus any external provider you use with your own key. Do not add platform usage twice when it is included. Apify credits and plan discounts affect your invoice. Set a run cost limit in Console before starting. *** **Independent tool.** We built and run this Actor ourselves. The job boards and sites it reads do not operate, sponsor or endorse it, and their names are used only to say where the data comes from. # Actor input Schema ## `queries` (type: `array`): Match postings whose title or description contains every word of a query, as whole words, ignoring case. A posting matches when any query matches. Words match as the posting wrote them, so where postings are not in English, add the local term as a further query. Empty: no filter. Default: queries that find PhD, postdoc and research roles; replace them with your own, or clear the list to search every posting. With the defaults, a stored posting also needs one of those terms in its job title, except on EURAXESS, Ikerbasque and Universitat de Barcelona, which are research-focused boards. Your custom queries match against both title and description. ## `locations` (type: `array`): City, region, country name or two-letter ISO country code. Countries match by name, code or native name; EU and Europe expand to their countries. A posting also matches when the source names the place as somewhere an applicant may live (`applicantLocations`). Empty: no filter. ## `locationTypes` (type: `array`): remote, hybrid or onsite. A posting matches when any arrangement it names is selected; `workType` in the row is set only when the source names exactly one. Postings whose arrangement the source does not state are left out. Empty: no filter. ## `employmentTypes` (type: `array`): Full-time, Part-time, Contract or Internship. Postings whose type the source does not state are left out. Empty: no filter. ## `postedWithin` (type: `string`): Positive duration in hours, days, weeks, or 30-day months, at most 36500 days; any disables the filter. Uses the first inventory admission date when the source has no posting date. ## `maxItems` (type: `integer`): Maximum returned jobs. Zero, or anything above 200, means 200. ## `maxItemsPerSource` (type: `integer`): Most postings any one source contributes, at most 200. maxItems then keeps the newest postings across sources. ## `dedupe` (type: `object`): Suppress confirmed repeat deliveries for the same Apify user and search. ## `schemaVersion` (type: `string`): Version marker for database-only simple job search. Version 1 inputs remain valid. ## Actor input object example ```json { "queries": [ "postdoc", "phd", "research fellow", "research associate", "research scientist", "doctoral", "researcher", "research assistant", "research engineer", "postdoctoral", "post-doc", "predoctoral", "doctorate", "doktorand", "professor", "lecturer" ], "locations": [ "Europe" ], "locationTypes": [], "employmentTypes": [], "postedWithin": "any", "maxItems": 20, "maxItemsPerSource": 5, "dedupe": { "enabled": true, "key": "" }, "schemaVersion": "nomad-agent-simple-inventory-search-v2" } ``` # Actor output Schema ## `dataset` (type: `string`): No description ## `runSummary` (type: `string`): One record describing this run: what was attempted, what was delivered, and anything that degraded. Written to the run's key-value store under RUN-SUMMARY. # 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 = { "locations": [ "Europe" ], "postedWithin": "any", "maxItems": 20, "maxItemsPerSource": 5, "dedupe": { "enabled": true, "key": "" } }; // Run the Actor and wait for it to finish const run = await client.actor("nomad-agent/researcher-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 = { "locations": ["Europe"], "postedWithin": "any", "maxItems": 20, "maxItemsPerSource": 5, "dedupe": { "enabled": True, "key": "", }, } # Run the Actor and wait for it to finish run = client.actor("nomad-agent/researcher-bundle").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 '{ "locations": [ "Europe" ], "postedWithin": "any", "maxItems": 20, "maxItemsPerSource": 5, "dedupe": { "enabled": true, "key": "" } }' | apify call nomad-agent/researcher-bundle --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,nomad-agent/researcher-bundle" } } } ``` 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/vW8dfaG0Dybl5oVQT/builds/ELnt1RbmDcqOvTfeg/openapi.json