> ## Documentation Index
> Fetch the complete documentation index at: https://docs.intelligence-management-platform.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Retrieve platform configuration

> Returns selected `ExuluApp` configuration options needed by the frontend: auth mode, feature entitlements, MCP status, telemetry, file-upload endpoint, worker health, LiteLLM status, and Recall integration. No authentication is required.



## OpenAPI

````yaml /openapi/openapi.json get /config
openapi: 3.1.0
info:
  title: IMP REST API
  version: 1.0.0
  description: >-
    REST endpoints of the IMP backend. GraphQL covers entity CRUD; REST covers
    agent runs, media, files, and system utilities. All requests require
    authentication unless the agent is public.
servers:
  - url: '{baseUrl}'
    variables:
      baseUrl:
        default: http://localhost:9001
        description: >-
          Base URL of your IMP backend. Self-hosted deployments typically run on
          port 9001.
security:
  - apiKey: []
  - bearer: []
tags:
  - name: Agents
    description: Endpoints for running, compacting, and querying agent instances.
  - name: Sessions
    description: Endpoints for managing files attached to agent sessions.
  - name: Media
    description: Transcription, speech synthesis, and image generation.
  - name: System
    description: Platform health and configuration utilities.
  - name: Budgets
    description: >-
      LiteLLM tag-budget management for users, roles, teams, projects, agents,
      and routines. Access requires `super_admin` or a role with
      `budget_management` write scope.
  - name: Skills
    description: >-
      Skills are versioned bundles of files (markdown, scripts, assets) mounted
      into the agent sandbox. These endpoints manage the skill registry and
      individual skill files.
  - name: Uploads
    description: >-
      Uppy-compatible S3 companion routes for single-part and multipart file
      uploads. Accept the standard API key. The `internal-key` header (set to
      `INTERNAL_SECRET`) is accepted only on `/s3/delete`, `/s3/download`,
      `/s3/list`, and `/s3/object` — it does **not** work on `/s3/sign` or the
      `/s3/multipart` routes.
  - name: Compliance
    description: >-
      GDPR / DSGVO operator endpoints for data-subject access (export) and
      erasure. Both require `super_admin`.
  - name: Artifacts
    description: >-
      Shareable artifact links — create, list, and revoke share links for files
      stored in S3.
paths:
  /config:
    get:
      tags:
        - System
      summary: Retrieve platform configuration
      description: >-
        Returns selected `ExuluApp` configuration options needed by the
        frontend: auth mode, feature entitlements, MCP status, telemetry,
        file-upload endpoint, worker health, LiteLLM status, and Recall
        integration. No authentication is required.
      operationId: getConfig
      responses:
        '200':
          description: Platform configuration subset.
          content:
            application/json:
              schema:
                type: object
                properties:
                  authMode:
                    type: string
                    enum:
                      - password
                      - otp
                  entitlements:
                    type: object
                    additionalProperties: true
                  MCP:
                    type: object
                    properties:
                      enabled:
                        type: boolean
                  telemetry:
                    type: object
                    properties:
                      enabled:
                        type: boolean
                  fileUploads:
                    type: object
                    properties:
                      s3endpoint:
                        type: string
                  workers:
                    type: object
                    properties:
                      enabled:
                        type: boolean
                      redisHost:
                        type: string
                      telemetry:
                        type: object
                        properties:
                          enabled:
                            type: boolean
                  liteLLM:
                    type: object
                    properties:
                      enabled:
                        type: boolean
                  recall:
                    type: object
                    properties:
                      enabled:
                        type: boolean
      security: []
components:
  securitySchemes:
    apiKey:
      type: apiKey
      in: header
      name: x-api-key
      description: >-
        Organisation API key. Format: `sk_<secret>/<keyname>` — the secret
        portion, a literal slash, and the human-readable key name. The header
        `exulu-api-key` is accepted as an alias. A `Bearer ` prefix is tolerated
        and stripped. Keys with an agent scope are only valid for the scoped
        agent instance.
    bearer:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: >-
        NextAuth session JWT (HS256, signed with `NEXTAUTH_SECRET`). This is the
        token the IMP frontend uses automatically.

````