Wellfound Locations API and MCP — Job Location Slugs for Job Search
Run it with no input, or filter by a name fragment and a type (US city, US state or other), and get the list of Wellfound job locations as JSON. Each entry has the name, slug, region, type, a link to the location page and a link to software-engineer jobs there.
- You send
- optionally a name fragment and a location type (city, state or other)
- You get back
- the list of Wellfound job locations with name, region, type, slug and links
- Coverage
- Wellfound records with a public page.
- Price
- 5 pts — $5 per 1,000
- Charged only when the record resolves. A request that finds nothing is not billed.
Ways to get this data
Three approaches teams use today, and where each one runs into trouble.
| Approach | What it takes | Cost | Trade-off |
|---|---|---|---|
| Wellfound directly | Browse Wellfound and note each entry | Free, and slow | Fine for one record, useless across a list, and the layout differs on every platform |
| Building a scraper | Write it, host it, and repair it when Wellfound changes its pages | Engineering time | A maintenance commitment for something that isn't your product |
| NeuralVerge | One request, the same shape as every other source in the catalog | $5 per 1,000, misses not billed | Returns what Wellfound publishes at request time. Other platforms are separate sources with the same request format |
What you get back
Every field in the example response below.
| Field | Type | Description |
|---|---|---|
session_id | string | Id of this run, for tracing. |
kind | string | Source type of the response, here wellfound_locations. |
partial | boolean | True if the run stopped before it finished. |
machine.total_items | number | Number of locations returned. |
machine.first_item | object | Copy of the first location. |
machine.items | array | The locations, one object each. |
machine.total_found | number | Total locations found. |
machine.page_count | number | Number of pages read. |
machine.blocked | boolean | Whether the platform refused the request. |
total_points | number | Points charged for the run. |
machine.items[].id | string | Location id. |
machine.items[].name | string | Location name. |
machine.items[].slug | string | Slug to use as location in Wellfound job search. |
machine.items[].region | string | Region or state code. |
machine.items[].type | string | city, state or other. |
machine.items[].url | string | Link to the location on Wellfound. |
machine.items[].jobs_url | string | Link to software-engineer jobs in the location. |
Example response
A real response, as returned.
{
"session_id": "11111111-1111-1111-1111-111111111111",
"kind": "wellfound_locations",
"partial": false,
"human": "# Wellfound — locations\n\n- **Query:** all\n- **Results:** 275 of 275 found\n- **Proxy traffic:** 155.3 KB",
"machine": {
"total_items": 275,
"first_item": {
"id": "albuquerque",
"name": "Albuquerque",
"slug": "albuquerque",
"region": "NM",
"type": "city",
"url": "https://wellfound.com/browse/tech-job-locations/albuquerque",
"jobs_url": "https://wellfound.com/role/l/software-engineer/albuquerque"
},
"items": [
{
"id": "albuquerque",
"name": "Albuquerque",
"slug": "albuquerque",
"region": "NM",
"type": "city",
"url": "https://wellfound.com/browse/tech-job-locations/albuquerque",
"jobs_url": "https://wellfound.com/role/l/software-engineer/albuquerque"
},
{
"id": "ann-arbor",
"name": "Ann Arbor",
"slug": "ann-arbor",
"region": "MI",
"type": "city",
"url": "https://wellfound.com/browse/tech-job-locations/ann-arbor",
"jobs_url": "https://wellfound.com/role/l/software-engineer/ann-arbor"
}
],
"total_found": 275,
"page_count": 1,
"blocked": false,
"proxy_traffic_bytes": 159013
},
"total_points": 5
}How to run it
The same lookup works from the app, the API, or as a tool an agent can call mid-task.
One record per request. Results come back in the same envelope as every other source: a session id, a readable summary, the structured result and the points charged.
curl -X POST https://api.neuralverge.ai/functions/v1/run-wellfound-locations \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{}'What teams use it for
Where this field shows up in an actual workflow.
Fetch valid location slugs before running job searches.
See which cities and countries Wellfound has a location page for.
Fill a location picker in your own tool from the list.
Loop over every city slug to compare hiring across locations.
Coverage, freshness and limits
What this source covers, how fresh it is, and where it stops.
Wellfound records with a public page.
Read at request time, so the answer reflects the platform as it stands when you ask.
This source returns information Wellfound shows publicly. Every response carries the session id you can trace.
- —The jobs_url in the sample points to software-engineer jobs; other roles use the role slug in job search.
- —Names like countries and non-US cities fall under type other.
- —The list reflects Wellfound as it stands when you ask; locations can be added or removed.
Questions, answered
Pass it as location to Wellfound job search together with a role slug.
Related sources
Try wellfound locations on your own data
One request format across every source in the catalog.