A quick overview of a person: career, likely challenges, and angles

Required permissions: research:trigger.

Given a person — any person, by their LinkedIn profile, or a person in your workspace — return a short stakeholder overview: their career progression, professionalInsights tied to what your workspace sells, and the challenges they are likely up against.

Returns an overview in the same response, typically within 2–3 seconds. The server stops after 120 seconds by default with 503 research_failed. Set your client timeout above 120 seconds and retry once on retry_later. Each call generates a new answer. It saves nothing to your workspace. The company or person does not need to be in your workspace. This is the same quick overview the Trayo app shows. Public REST and MCP usage is recorded without daily usage caps, workspace quota cutoffs or lookup quotas for now. Workspace request pacing still applies.

How it works. A workspace person's existing match is read; without one, their LinkedIn username is looked up, which is also what a profile sent as linkedinUrl does. person.resolvedBy says which. The profile Trayo holds — headline and work history — informs the overview together with your workspace's solutions and stakeholder definition (GET /v1/workspace).

grounded. Ungrounded, the default: no web search, and the overview is built from the profile Trayo holds alone, so personalInsights, companyIntel, location and education are empty and challenges are inferences. Grounded, Trayo searches the web for timely company intel and personal facts — slower (5–15 seconds rather than 2–3), and it occasionally fails to answer (503 research_failed; retry once). Both modes draw on the quota the same way. A web fact Trayo could not source is withheld rather than stated, so an empty location means "could not be sourced", not "unknown". Source links are not published — the requirement to have one gates what is said, and the link itself is not returned, in research or in reportMarkdown. Treat a grounded overview as a lead to check, not as sourced evidence.

Compared with POST /v1/stakeholders/search. That finds WHO at a company fits a definition; this says what to know about ONE person you already have in hand — a stakeholder-search result's linkedinUrl goes straight into person.linkedinUrl here.