Replace the workspace context (ICP, company positioning, content strategy, user background) and optionally update identity fields on the…
getContext, this endpoint is part of the agent boot sequence. Typical flow: fetch with GET /api/context, mutate the sub-sections the user wants to change, and PUT the full object back. Onboarding also calls this internally after scraping the user’s LinkedIn and company website.
Agents should not invent context — prefer asking the human for specifics or running onboarding to auto-derive it.
/api/context with other verbs. See the sibling page for related operations on the same resource.Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Whole-object replacement for context. There is no field-level PATCH — fetch with GET /api/context, mutate client-side, and PUT the full object back.
Full context object. Validated against FullUserContextSchema; all four sub-objects (user, company, content, market) must be present, extra may be null.
Optional identity fields to update alongside the context JSONB columns. Only keys present in the body are applied.
Context saved. Returns the newly persisted full context.
Assembled workspace context. Each sub-object is stored as a separate JSONB column on user_profiles and merged at read time.