/dash/explore/search). The same filters are available through MCP search or GET /people.
Recruiter language
Type a sentence. FreshTalent compiles it to structured filters. Explicit filters always win if both are present. Examples that parse today:Filters
Full query params: GET /people.
To browse a company roster instead of a people query, use Companies.
For the source and meaning of each flag, see Availability.
Exploring
FreshTalent’s AI assesses whether someone looks open to a new employment role now, using profile text and changes observed in the last 30 days. Unchanged openness can qualify without a new edit. People marked Open to work or Between roles are excluded. Routine profile polishing or a completed job move alone is not enough. Hover over or select the badge for an AI explanation. Highlighted text opens the supporting current snapshot or before/after change, with its observation date. See how we detect exploration for the process, a worked example, and how to interpret the evidence.Compact vs full
Open a person for coworkers and similar people (
include=coworkers,similar).
Role family vs Title
The search bar Role token has two modes:
Name + headline keywords do not search job titles. Use Role → Title for that.
Export
On a result set, Export (dashboard only). CSV or JSON.Recent searches
The empty Search page shows Recent searches (last 8, this browser) plus recommended queries. Sharing a Search URL reuses the same filters. Persist for the org with POST /queries, or start a Target.The echoed query
Every search returnsquery — the snake_case object that actually ran. That object is what you:
- save with POST /queries
- reuse on
GET /peoplefor a repeat graph search - adapt the filters for discovery; Target discovery uses a different schema and is not an exact replay of the graph search. See Search query compatibility.
From an agent
MCP toolsearch accepts nl and/or the same structured filters. It returns {slug,s} rows plus the echoed query. See Claude & Cursor.