Research API
Research is Heimdall reading the web for what a project's brief never states: what products of this kind commonly do, the laws, regulations and standards that apply in the client's country and industry, the integrations the client will expect, what the market already offers and the security and accessibility expectations the client will be held to.
Research is Heimdall reading the web for what a project's brief never states: what products of this kind commonly do, the laws, regulations and standards that apply in the client's country and industry, the integrations the client will expect, what the market already offers and the security and accessibility expectations the client will be held to. A run is one such reading, asked for by a person and worked on the queue as them; it writes notes (a topic, a summary and the sources it cites) under the run and leaves suggestions on the project, research for a fact the project must honour and improvement for a gap in its own record, which people keep or dismiss on the dashboard rail. A dismissed idea is remembered and never proposed again; a later run's notes sit beside the earlier ones.
Tokens read and ask for research as staff with the import:* abilities: reading needs import:view-any, asking needs import:create and the project's AI assists on, and a client guest's token is refused everywhere here. Research spends the team's monthly AI budget, and one run is worked at a time per project. The suggestions are decided through the suggestion endpoints of the brief import.
Endpoints
/v1/projects/{project}/researchList a project's researchPOST/v1/projects/{project}/researchResearch a project's domainGET/v1/projects/{project}/suggestionsList a project's research suggestionsRelated
How is this guide?
Last updated on