Document Intelligence

Read the workspace's Document Intelligence configuration — whether it's available and which integrations are wired up.

All paths are relative to the base URL and require an Authorization: Bearer YOUR_API_KEY header.

Get configuration

GET /document-intelligence

Returns the Document Intelligence configuration for API consumers, without stored API keys.

Response — PublicDocumentIntelligenceConfigResponse

{
  "status": "configured",
  "error": null,
  "configuration": {
    "integrations": [
      {
        "type": "reducto",
        "endpoint": "https://backend.sema4.ai/reducto",
        "external_id": null
      }
    ]
  }
}

Field	Type	Description
status	string	`configured`, `not_configured`, `not_available`, or `error`.
error	object	Error detail when `status` is `error`; otherwise null.
configuration	object	The configuration, including the list of `integrations`; null when there is nothing configured.

Integration (PublicDocumentIntelligenceIntegration)

Field	Type	Description
type	string	Integration kind — `reducto`, `data_server`, or `quartermaster`.
endpoint	string	The endpoint the integration calls.
external_id	string	Identifier in the external system, or null.

Error (PublicDocumentIntelligenceError)

Field	Type	Description
code	string	Machine-readable error code.
message	string	Human-readable description of the problem.
error_id	string	UUID for correlating the failure with server-side logs.

An error is reported inside a 200 response with status set to error — it does not come back as an HTTP error status.

Breaking change. This endpoint no longer returns the API keys held by each integration, and it now rejects unauthenticated callers with 401. Responses carry only the integration metadata shown above.

Observability Agent MCP