F6S Scraper: Programs, Accelerators, Events & Jobs

Extract structured records from F6S in minutes. This scraper covers four F6S directories in one tool: funding programs, startup accelerators, startup events, and startup jobs. It returns 25+ fields per record, supports both filter search and pasted URLs, and runs on a Residential connection (preselected) for reliable access to the site.

Why this scraper?

• Four directories in one actor: programs, accelerators, events, and jobs. Most alternatives only cover programs.
• 25+ fields per record, including investment amount, equity, deadlines, apply links, plus optional full description, funding range, website, social links, and team.
• Two ways to start: pick filters (list type, location, keyword, program type, sort, investment, equity) or paste any F6S list URL.
• Fast: a one-time connection setup, then pages load quickly with concurrent detail enrichment.
• Cost-efficient: the one-time setup is reused across the whole run, so per-record cost stays low and well below typical directory scrapers.
• Clean pagination that walks forward page by page and de-duplicates by ID.

Data you get

Sample shape: values are illustrative placeholders, not from a live listing.

Field	Example
id	sample-accelerator-2026
listType	accelerators
name	Sample Accelerator 2026
location	London, United Kingdom
tags	Funds Startups in AI, Fintech, SaaS
verified	true
deadline	by Jan 1
investmentRaw	$100k per team
investmentAmount	100000
investmentCurrency	USD
equityRaw	6%
equityPercent	6
profileUrl	https://www.f6s.com/sample-accelerator-2026
aboutUrl	https://www.f6s.com/sample-accelerator-2026/about
applyUrl	https://www.f6s.com/sample-accelerator-2026/apply
image	https://www.f6s.com/content-resource/profiles/00000001_th3.jpg
description	Full program description appears here when fetchDetails is on.
fundingCurrency	USD
fundingAmountMin	100000
fundingAmountMax	100000
website	https://example.com/
socialLinks	["https://www.linkedin.com/company/example/"]
team	[{"name": "Jane Doe", "url": "https://www.f6s.com/jane-doe"}]
category	Accelerators
country	United Kingdom
city	London
sourceUrl	https://www.f6s.com/accelerators
scrapedAt	2026-01-01T00:00:00.000Z

How to use

Basic search (programs worldwide):

{
  "mode": "search",
  "listType": "programs",
  "maxPages": 5,
  "maxListings": 100,
  "proxy": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] }
}

Accelerators in a location, with full details:

{
  "mode": "search",
  "listType": "accelerators",
  "location": "london",
  "fetchDetails": true,
  "maxPages": 3,
  "proxy": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] }
}

Programs filtered by keyword, type, sort and investment:

{
  "mode": "search",
  "listType": "programs",
  "keyword": "ai",
  "programType": "accelerator",
  "sortBy": "popular",
  "minInvestment": 25000,
  "maxEquity": 8,
  "maxListings": 200,
  "proxy": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] }
}

URL mode (paste any F6S list links):

{
  "mode": "url",
  "urls": [
    "https://www.f6s.com/programs/new-york",
    "https://www.f6s.com/events"
  ],
  "maxPages": 5,
  "proxy": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"] }
}

Limits and resuming a run

• maxPages (default 0 = unlimited). Leave it at 0 to walk an entire list end to end — there is no artificial page cap. The walk stops naturally once a page adds no new records (it has looped back to results already seen), a page comes back empty, or maxListings is reached.
• maxListings (default 20) is the main limit on a run: it stops the scrape after this many records. Set it to 0 to remove it and walk the whole catalogue (bounded only by the natural stop above).
• resumeFromRunId lets you continue a previous run instead of starting over. Paste in the run ID (or its dataset ID) from an earlier run of this actor; already-saved records are detected and skipped, so the new run only fetches what's missing. Handy for very large catalogues split across multiple runs, or picking up after an interrupted run.
• A long run is also checkpointed automatically: if the platform migrates or restarts the run, it picks back up without re-scraping or re-charging records it already saved.

Incremental / recurring updates

For a search or URL list you run on a schedule (daily, weekly), turn on incrementalMode instead of pasting a run id every time. The actor remembers the records it saw last time — in a dedicated key-value store, keyed by a hash of your search/URL filters (or your own stateKey) — and classifies every record it scrapes against that memory:

changeType	Meaning
NEW	Not seen in any previous run for this search.
UPDATED	Seen before, and at least one field genuinely changed — changedFields lists which.
UNCHANGED	Seen before, nothing changed. Not returned by default (turn on emitUnchanged to get it anyway).
REAPPEARED	Seen before, then missing for a run, now back.
EXPIRED	Seen before, not found in this run, and this run reached the natural end of the search (no cap, no Resume) — see emitExpired below.

By default a recurring run therefore returns only what changed — a quiet run (nothing changed) can legitimately push zero records, which is not an error.

• stateKey — optional human-readable label for the tracked search; leave empty for an automatic key derived from your filters.
• emitUnchanged (default off) — also return UNCHANGED rows, i.e. the full current snapshot every run.
• emitExpired (default off) — also return one tombstone row per record no longer found, but only when this run scanned the search to its natural end (no maxListings/maxPages cap hit, no resumeFromRunId) — a capped or resumed run can't tell "gone from F6S" apart from "not reached yet this run", so it skips EXPIRED detection and logs why instead of guessing.
• resumeFromRunId and incrementalMode are two different features — combine them only to bootstrap a monitoring baseline from a prior one-off crawl (the run fails fast if incremental mode already has saved state for that search).
• Fields excluded from change detection, so they never trigger a false UPDATED: scrapedAt (always changes, it is the fetch time) and sourceUrl (the search-results page a record was seen on — F6S's default "open" sort re-ranks the whole list as other records' deadlines shift, so the same record can land on a different page with nothing about the record itself having changed). Every other field, including deadline and investmentRaw, participates — a real change there is exactly the kind of thing a monitoring user wants surfaced. When fetchDetails is off, or an individual profile's About page fails to load, the detail-only fields (description, category, country, city, fundingCurrency, fundingAmountMin, fundingAmountMax, website, socialLinks, team, detailImage) are also excluded for that comparison rather than reading their absence as the site having removed them.

Input parameters

Parameter	Type	Default	Description
mode	string	search	search builds list URLs from filters; url uses pasted links.
listType	string	programs	programs, accelerators, events, or jobs.
location	string	(empty)	Location slug, for example london or europe.
keyword	string	(empty)	Free-text keyword, for example ai.
programType	string	any	accelerator, incubator, grant, competition, fellowship.
sortBy	string	open	open, popular, or closest (closing soon).
minInvestment	integer	(none)	Keep records offering at least this much per team.
maxInvestment	integer	(none)	Keep records offering at most this much per team.
maxEquity	integer	(none)	Keep records taking at most this much equity.
urls	array	(example)	F6S list URLs for URL mode.
fetchDetails	boolean	false	Open each About page for description, funding, website, social, team.
maxPages	integer	0	Result pages to walk per list. 0 = unlimited — walk the whole list; the walk stops naturally once a page repeats results already seen (no artificial page cap).
maxListings	integer	20	Stop after this many records. This is the main limit on a default run (0 = unlimited, opt-in).
resumeFromRunId	string	(empty)	Optional: a previous run ID (or its dataset ID) to continue. Records already saved there are skipped, so this run only adds new ones.
incrementalMode	boolean	false	Recurring monitoring: return only NEW/UPDATED/REAPPEARED records vs. the actor's own memory of the last run for this search. See "Incremental / recurring updates" above.
stateKey	string	(empty)	Optional label for the tracked search in Incremental mode. Auto-derived from filters when empty.
emitUnchanged	boolean	false	Incremental mode only: also return UNCHANGED records (the full snapshot every run).
emitExpired	boolean	false	Incremental mode only: also return EXPIRED records, when this run reached the natural end of the search.
proxy	object	Residential	Connection settings. Residential is required and preselected.

Send results into your apps (MCP connectors)

Optionally pipe the scraped results into the apps you already use, via Model Context Protocol (MCP) connectors. This is an extra delivery step after the scrape — the Apify dataset is never changed.

What gets written to the connector: a condensed, human-readable summary of each record — not the full JSON. Each item becomes one entry with a title and its key fields flattened to plain text. The complete record always stays in the Apify dataset.

1. Authorize a connector once under Apify → Settings → Integrations (Notion, Linear, Airtable, or Apify).
2. Select it in the "Pipe results into your apps" input field. (If the picker is empty, you haven't authorized a connector yet.)
3. For Notion, also set notionParentPageUrl to the page where items should be created.

The connection is mediated by Apify's MCP proxy, so this actor never sees your third-party credentials. Leave the field empty to skip.

Output example

Sample shape: values are illustrative placeholders, not from a live listing.

{
  "id": "sample-accelerator-2026",
  "listType": "accelerators",
  "name": "Sample Accelerator 2026",
  "slug": "sample-accelerator-2026",
  "profileUrl": "https://www.f6s.com/sample-accelerator-2026",
  "aboutUrl": "https://www.f6s.com/sample-accelerator-2026/about",
  "applyUrl": "https://www.f6s.com/sample-accelerator-2026/apply",
  "image": "https://www.f6s.com/content-resource/profiles/00000001_th3.jpg",
  "location": "London, United Kingdom",
  "tags": "Funds Startups in AI, Fintech, SaaS",
  "verified": true,
  "deadline": "by Jan 1",
  "investmentRaw": "$100k per team",
  "investmentAmount": 100000,
  "investmentCurrency": "USD",
  "equityRaw": "6%",
  "equityPercent": 6,
  "description": "Full program description appears here when fetchDetails is on.",
  "category": "Accelerators",
  "country": "United Kingdom",
  "city": "London",
  "fundingCurrency": "USD",
  "fundingAmountMin": 100000,
  "fundingAmountMax": 100000,
  "website": "https://example.com/",
  "socialLinks": ["https://www.linkedin.com/company/example/"],
  "team": [{ "name": "Jane Doe", "url": "https://www.f6s.com/jane-doe", "image": null }],
  "sourceUrl": "https://www.f6s.com/accelerators",
  "scrapedAt": "2026-01-01T00:00:00.000Z"
}

Plan requirement

This actor uses a Residential connection (preselected), which the site requires; it is available on the Starter plan and above. Pay-per-result billing applies: a small base rate per record, plus a small surcharge per detail page when fetchDetails is on.