How FreshTalent works

Recruiters already have a one-off LinkedIn search. FreshTalent is what happens after: you keep the people, you pin the query, and you get told when someone actually moves. The sidebar names are the product names. Use them.

Search finds people

Natural language and filters compile to the same query object. Every response includes that object so a human or an agent can save and replay the search. Target discovery uses a different schema and is not an exact replay of the graph search. See Search query compatibility.

Companies is the roster

Browse teams, leavers, and role mix. Current team and Recent leavers. Start company search turns that into a Target.

Lists are the pipeline

Stages To contact, Contacted, Responded, Passed. People on a List show up in Monitoring even if they are not Monitored on a Target.

Targets stay standing

A people search (Start people search) or a company (Start company search). Only people you Accept (filter Monitored) stay enriched and count toward slots.

Monitoring is the feed of profile diffs on people you keep (List or Monitored). Email and Slack are configured in Settings → Notifications and can include anyone in the graph. Org, Team, and webhook URL live under Settings. API Keys is a separate sidebar item.

The objects

Object	Id	Dashboard	REST / MCP
Person	LinkedIn slug	Search row or dossier	`GET /people`, `GET /people/:slug`
Company	key	Companies	`GET /companies/:key` · MCP `expand`
Query	uuid	The filters behind a search	`POST /queries`
List	name or uuid	Lists	`/lists` · MCP `collect`
Target	uuid	Targets	`/targets` · MCP `watch`
Event	uuid	Monitoring	`GET /events` · MCP `events`
Notification prefs	org	Settings → Notifications	`/signals/preferences` · MCP `subscribe`

Person ids are always LinkedIn slugs (derek-morrow), never emails.

Compact vs full

Search (and MCP) returns a compact row so agents and list views stay cheap:

{
  "slug": "derek-morrow",
  "name": "Derek Morrow",
  "headline": "FDE, Anduril",
  "linkedin_url": "https://www.linkedin.com/in/derek-morrow",
  "current": { "company": "Anduril", "title": "FDE", "months": 14 },
  "match": { "company": "Palantir", "months": 50 },
  "open_to_work": false,
  "between_roles": false,
  "exploring": false,
  "github_hireable": true
}

Open the person — or GET /people/:slug — for the dossier. ?include=coworkers,similar expands one hop of the graph. Availability in the app: Open to work, Between roles, Exploring, GitHub Available for hire. See Availability for their sources and how AI exploration detection works.

The echoed query on a search response is the filter language. Copy it. Do not invent Cypher or guess at field names.

Who does what

Job	Surface
Source and pipeline	Dashboard — recruiter quickstart
Agent runs the loop in Slack-speed	Claude / Cursor
Nightly sync to ATS	Events poll

Search

How queries compile and what you can filter.

Companies

Current team, Recent leavers, then a company Target.

Lists

To contact, Contacted, Responded, Passed.

Targets

Find people, Accept, Start monitoring.

Settings

Organization, Notifications, Profile. API Keys is separate.

Start here

The product

Connect

Reference

How FreshTalent works

Search finds people

Companies is the roster

Lists are the pipeline

Targets stay standing

The objects

Compact vs full

Who does what

Next

Search

Companies

Lists

Targets

Settings

Search finds people

Companies is the roster

Lists are the pipeline

Targets stay standing

​The objects

​Compact vs full

​Who does what

​Next

Search

Companies

Lists

Targets

Settings

The objects

Compact vs full

Who does what

Next