People arrive at this question expecting a yes or a no. The useful answer is a description of which surfaces exist and what each one is guarded by.
No documented public jobs API
Wellfound publishes no documented public API for its job listings. Every tool in this category — including this one — is reading the web surfaces, and a vendor implying otherwise is describing an internal endpoint rather than a supported one.
What robots.txt actually says
Checked on 9 September 2026, wellfound.com/robots.txt disallows a specific list:
| Disallowed | What it is |
|---|---|
/search | Site search results. |
/u/ | User profiles — people. |
/auth/, /onboarding, /profile/* | Account and session surfaces. |
/documents/, /embed/, /projects/ | Non-listing content. |
/*?role=*, /*?jobId=*, /*?jobSlug=* | Query-parameter forms of listing URLs. |
The role listing paths that carry job results are not in that list. The file also declares two sitemaps. Reading a robots.txt as a specification rather than as a formality is a habit worth having — robots.txt as a specification.
What Cloudflare sits in front of
Company profile pages are behind a Cloudflare challenge. That is a control the site put there on purpose, and this Actor treats it as a boundary rather than an obstacle — which happens to coincide with the fact that those pages name founders and employees. The data this Actor will not collect.
Cloudflare is also in front of the pages that are read, as a cache rather than as a challenge, which is why every row carries an age that includes somebody else's caching.
Path filtering, and why `?role=` is disallowed
Wellfound's filters are path segments. The query-parameter forms in robots.txt are alternative addresses for pages that already have a canonical path, and disallowing them is ordinary duplicate control rather than a statement about job data. It is also the same architectural fact that makes remote-plus-location a 404: there is no route for it.
What is left, and why it is enough
The role listing path and the job detail page it links to. That turns out to be enough for the thing an API would have been wanted for, because the listing surface already carries the full job description — measured present on 100% of 2,229 jobs. The field that usually costs a second request is the one that arrives first.
