Recruitment by filter works for most studies. Sometimes it doesn't — the panel you want is a hand-picked dozen out of three thousand candidates, or a customer asks specifically for "the personas you used last month, plus three more from Texas". Until this week the answer was "we'll do that for you over email". Now it's an API call.
What's new
`GET /v1/agents/search` — search the persona library with the same filter DSL the recruitment endpoint uses, plus pagination and a
recruitable_onlyscope. Returns the full agent record including the numericid, the demographics, and the summary text. Useful as a first pass when you know roughly what you want but not exactly who.Manual group composition. Add personas to an existing group by ID. Partial-success responses tell you which IDs were added and which weren't (and why) rather than failing the whole call. Use it to extend a recruited group, hand-curate from a search, or rebuild a group from a saved list.
How to use it
The search endpoint takes the standard filter parameters (country, age range, gender, parent status, education) plus pagination. The composition endpoint takes a group_uuid and a list of agent_ids to add. Pair the two when you want to recruit by filter, then add a couple of specific personas you've used before.
The original POST /v1/research-groups/recruit and POST /v1/research-group-requests flows are unchanged. Hand-composition is additive, for the cases where filter-based recruitment isn't quite what you need.
Full reference is in the API docs.
---