Extract criteria
Turns a job description or plain-language brief into structured criteria, without running a search. Use the returned criteria as the body of POST /api/scans once a human has reviewed it.
Authorizations
A signed-in workspace session, sent as a browser cookie. Requests must include credentials, and act on the session's active workspace.
Body
The job description or brief.
"Clinic manager in Lévis, Québec. French required. 5+ years managing a multi-site clinic. Find 25."
candidate searches for people against a role. client discovers target companies first, then their decision-makers.
candidate, client Which model extracts criteria. Anything outside this allowlist is rejected. Omit to use the workspace default.
claude-haiku-4-5, claude-sonnet-5, claude-opus-5 Response
Structured criteria plus coverage diagnostics.
The structured brief a search runs on. Every field is optional, but a search with no signal finds nothing useful.
The distinction that matters: exclude_* fields are hard and disqualify, while avoid_* fields are soft and only rank down. A great person at a firm you'd rather avoid still shows up; a person at an excluded firm never does.
Which criteria dimensions the input actually pinned down — drives the confirmation chips in the app.
True when the role sits outside the known role-family taxonomy. The role name is preserved as a title variant.