Skip to main content

Get resolved requester context

Resolve the current caller’s requester/company context variables and draft readiness for AI-draft workflows.

GET/api/llm/company-context
HTTP referenceScope authenticated user sessionUpdated September 27, 2026

This page documents the canonical HTTP contract for this endpoint.

This route requires an authenticated user session. Developer API keys are blocked by the shared auth dependency with HTTP 403.

This endpoint is the live readiness counterpart to GET /api/capabilities.

Use it when you need caller-specific requester context for AI drafting or workflow preflight.

  • variables returns the effective org + personal requester context that the enrichment/runtime layer will actually see.
  • draft_readiness.requester_context reports primary and secondary fields, available fields, and missing primary/secondary fields. research_context reports supported sources and the starred-field default; it does not evaluate a caller's selected research fields.

Errors

StatusMeaning
401Missing or invalid user session.
403Developer API keys are blocked for this session-only route.
404Requester context service reports a missing context value.
500Unexpected context-resolution error, including missing user context caught by the handler.

Docs