A quick overview of a company: what it does, why now, and fit

Required permissions: research:trigger.

Given a company — any company, by its website (or LinkedIn page or name), or an account in your workspace — return a short overview: the firmographic facts, whyNow hooks drawn from its recent LinkedIn updates, and fit against what your workspace sells.

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. The company is identified exactly as the Trayo app identifies one — LinkedIn page, then website (following its redirect), then name, against the same data; company.resolvedBy says which key matched. Read company.name and company.website back before you act on the overview — a guessed handle or a common name can match a different company, and the overview will faithfully describe that one. The record Trayo holds — description, industry, size, tech stack and its recent company updates — informs the overview together with your workspace's solutions and stakeholder definition (GET /v1/workspace), which is where fit comes from. No web search: the "why now" signal is our own recent updates, so whyNow is empty when the company has posted nothing substantive.

Nothing is written. Adding a company as an account is what puts it on record — background work that persists the company, its people and its events. This is a read: seconds, nothing stored, any company, whether or not you hold it.