AI Jobs Scraper (aijobs.net) — ML & Data Roles avatar

AI Jobs Scraper (aijobs.net) — ML & Data Roles

Pricing

from $2.00 / 1,000 job results

Go to Apify Store
AI Jobs Scraper (aijobs.net) — ML & Data Roles

AI Jobs Scraper (aijobs.net) — ML & Data Roles

Scrape AI, machine learning and data science jobs from aijobs.net: ML engineer, data scientist, MLOps, research scientist, more. Each record has title, company, location, remote flag, seniority, salary band, posted date and apply URL. Filter by keyword and location; company + description included.

Pricing

from $2.00 / 1,000 job results

Rating

0.0

(0)

Developer

Nomad Dev

Nomad Dev

Maintained by Community

Actor stats

0

Bookmarked

8

Total users

2

Monthly active users

2 days ago

Last modified

Categories

Share

Fetch machine learning jobs and data science jobs from aijobs.net — AI engineer, ML engineer, data scientist, MLOps, research scientist and more — with company, remote flag, salary bands (where disclosed) and seniority levels. Filter by keyword and location, and page past the first ~50 cards.

Claude / Codex skill to describe and setup this actor: SKILL.md

What AI jobs data does this scraper extract?

Published postings follow nomad-agent-job-row-v1. The shared fields carry source identity, title and company, parsed locations, dates, the complete plain-text body when available, source markup when usable, and work type. Unavailable scalar facts are null; no parsed location is []. Source-only facts appear in versioned custom.data only when mapped there. See the Output example section for the exact dataset fields and diagnostic rows.

How to scrape AI jobs with this Actor

  1. Click Try for free / Run — no login to the target site, no cookies, no proxies to configure.
  2. Adjust the input — narrow with searchQuery (keyword) and location, raise maxItems to page past the first ~50 cards, or keep the defaults.
  3. Run it and export the dataset as JSON, CSV or Excel, or read it over the API.

Run it from your own code:

from apify_client import ApifyClient
client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("nomad-agent/ai-jobs-net-scraper").call(run_input={"maxItems": 50, "includeCompany": True})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
print(item["title"], "—", item["company"], item["url"])

Or a single HTTP call that runs the Actor and returns items in one response:

curl -X POST \
"https://api.apify.com/v2/acts/nomad-agent~ai-jobs-net-scraper/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>" \
-H "Content-Type: application/json" \
-d '{"maxItems": 50}'

Input

FieldTypeDefaultNotes
searchQuerystringKeyword filter (alias: keyword). Keeps only jobs whose card text contains every word you enter (case-insensitive), e.g. machine learning. Empty returns all.
locationstringLocation filter. Keeps only jobs whose location text contains this value (case-insensitive substring), e.g. Berlin, Germany, Remote. Empty returns all locations.
maxItemsinteger50How many listing cards to fetch. aijobs.net serves a "Load more" feed, so values above one page (~50) follow the pagination and fetch more cards, up to 300 (8 pages). Keyword/location filters are applied to the fetched cards, so the returned count may be lower. Set 0 to fetch just the first page (~50).
includeCompanybooleantrueThe listing page never shows the company name — only the per-job detail page does. On by default: fetches that page (one extra request per job, no extra per-job price) to populate company and description. Turn off for a faster listing-only pull, in which case both stay null.
euBiasbooleanfalseWhen enabled, listings whose location or title hints at a European country or remote-EU are sorted to the top. Non-EU jobs are still returned; they just appear later.
cacheTtlSecondsinteger1800(Advanced) Cache the page-1 fetch in the key-value store for this many seconds; re-runs within the window skip that call. Load-more pages (2+) are always fetched live. Set 0 to disable.

Output example

Every row follows nomad-agent-job-row-v1, the one shape shared by all of this fleet's job Actors. A row carries every field; null means the source did not publish that fact, and locations: [] means no usable location was parsed from the posting. Nothing is guessed.

{
"schemaVersion": "nomad-agent-job-row-v1",
"recordType": "posting",
"source": "foorilla",
"id": "a1b2c3",
"url": "https://example.com/foorilla/jobs/a1b2c3",
"title": "Senior Backend Engineer",
"company": "Example Company",
"locations": [
"Bilbao",
"Spain"
],
"postedAt": "2026-09-02T00:00:00Z",
"deadline": null,
"description": "The complete posting body as plain text, exactly as the source published it — never truncated.",
"descriptionHtml": "<p>The complete posting body as the source's own markup.</p>",
"workType": "remote",
"custom": {
"schemaId": "nomad-agent-job-custom-foorilla-v1",
"data": {
"slug": "…",
"postedAtText": "…"
}
}
}
FieldMeaning
schemaVersionAlways "nomad-agent-job-row-v1".
recordType"posting" for a job, "diagnostic" for a row reporting something about the run itself.
sourceWhich job source the posting came from, from the collector registry's vocabulary — not the Actor name.
idStable identifier for the posting within source.
urlCanonical public URL of the posting on the source site.
titleJob title exactly as the source publishes it, untruncated.
companyEmployer name as published.
locationsPlaces the role is based, most specific first — e.g. ["Bilbao", "Spain"].
postedAtWhen the source published the posting, ISO-8601 UTC (YYYY-MM-DDTHH:MM:SSZ).
deadlineClosing date for applications as an ISO-8601 calendar date (YYYY-MM-DD).
descriptionThe complete posting body as plain text — never truncated, never summarised.
descriptionHtmlThe posting body as the source's own markup, preserving lists, headings and links.
workTypeWorking arrangement: "remote", "hybrid" or "onsite".
customFacts only this source publishes, as {"schemaId", "data"}.

A run also emits diagnostic rows — recordType: "diagnostic" with a warnings array — when it has something to report, such as a source returning nothing. They are never billed and are easy to filter out on recordType.

Pricing

Pay per event: $0.005 per Actor start and $0.002 per job returned. 100 jobs ≈ $0.205. No subscription, no rental — you pay only for what you fetch. Enabling includeCompany adds an extra request per job but does not change the per-job price.

Use cases

  • AI-specialist job boards and newsletters
  • Tracking ML-engineer demand and salaries
  • Sourcing AI talent pipelines
  • Feeding the ml-ai-dev-bundle with anchor data

FAQ

Is it legal to scrape AI jobs? This Actor reads only publicly available job postings — data any visitor can see without logging in. No personal data behind authentication is touched. Review the target site's terms and your local regulations for your specific use case.

Do I need an account on the target site? No. Postings are fetched from public pages/APIs — no login, cookies or session tokens.

How fresh is the data? Every run fetches live listings. Results are cached for cacheTtlSeconds (default 30 min, set 0 to always hit the source live).

How many jobs can I get? maxItems caps the run. aijobs.net serves its listing as a "Load more" feed, so raising maxItems above one page (~50) follows the pagination and fetches more cards, up to 300 (8 pages). Keyword/location filters are then applied to the fetched cards, so the returned count may be lower. Set 0 to fetch just the first page.

Why is company empty? It normally isn't — includeCompany defaults to true, so company (and the full description) is fetched from each job's detail page. company is only null if you turn includeCompany off, or if a particular detail page has no company anchor.

Can I filter by keyword or location? Yes. Set searchQuery (keyword; every word must match) and/or location (substring of the location text). Both are case-insensitive and applied to the fetched cards.

Something broken or missing? Open an issue on the Actor's Issues tab — it is monitored and reliability fixes ship fast.

Integrations

Export the dataset as JSON, CSV, Excel/XLSX, or plug it straight into Make, Zapier or n8n via the Apify integrations. For one-shot pulls, call run-sync-get-dataset-items to run the Actor and get items back in a single HTTP response, or drive it through the Apify MCP server from any MCP-compatible agent.

Is this Actor useful to you? A quick ⭐ review on the Actor's Reviews tab helps other AI/ML job seekers find it — and tells us what to build next.


From the maker of Oink — an open-source, AI-powered job-search bot for Telegram that runs on these Actors. Try the free bot, get a managed instance at oinkjobsearch.com, or browse the full catalog of 50+ Actors.