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

# List agents in a space

> Returns a list of all agents (configurations) within the specified space.



## OpenAPI

````yaml GET /api/v1/spaces/{spaceId}/agents
openapi: 3.0.1
info:
  title: Sequentum Cloud API
  description: API endpoints for Sequentum Cloud
  version: v1
servers: []
security:
  - ApiKey: []
    Bearer: []
paths:
  /api/v1/spaces/{spaceId}/agents:
    get:
      tags:
        - ApiSpace
      summary: Get all agents in a space
      description: >-
        Returns a list of all agents (configurations) within the specified
        space.
      parameters:
        - name: spaceId
          in: path
          description: The ID of the space
          required: true
          schema:
            type: integer
            format: int32
      responses:
        '200':
          description: Returns the list of agents
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/SpaceAgentApiModel'
        '401':
          description: If the API key is missing or invalid
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ProblemDetails'
        '404':
          description: If the space is not found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ProblemDetails'
        '429':
          description: Too Many Requests
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ProblemDetails'
components:
  schemas:
    SpaceAgentApiModel:
      type: object
      properties:
        id:
          type: integer
          format: int32
        name:
          type: string
          nullable: true
        description:
          type: string
          nullable: true
        configType:
          $ref: '#/components/schemas/ConfigType'
        status:
          type: integer
          format: int32
          nullable: true
        validationStatus:
          $ref: '#/components/schemas/ConfigValidationStatus'
        lastActivity:
          type: string
          format: date-time
          nullable: true
      additionalProperties: false
      description: Agent summary for space listing
    ProblemDetails:
      type: object
      properties:
        type:
          type: string
          nullable: true
        title:
          type: string
          nullable: true
        status:
          type: integer
          format: int32
          nullable: true
        detail:
          type: string
          nullable: true
        instance:
          type: string
          nullable: true
      additionalProperties: {}
    ConfigType:
      enum:
        - 1
        - 2
        - 3
        - 4
      type: integer
      description: '`1` = `Agent`; `2` = `SharedFile`; `3` = `Template`; `4` = `Command`'
      format: int32
    ConfigValidationStatus:
      enum:
        - 1
        - 2
        - 3
      type: integer
      description: "Semantic validation status of a config's most recently saved definition (e.g. whether every\r\nfixed export schema column is actually produced by a command). Serialized as its underlying\r\nint, not a string - see Sequentum.Enterprise.ControlCenter.Swagger.EnumDescriptionsSchemaFilter\r\nfor how these values get documented in the public OpenAPI spec. (`1` = `Unknown` - Validation status was not computed for this response (e.g. a historical config version, which does not retain its own stored status); `2` = `Invalid` - The config has one or more semantic validation errors (e.g. a required export column with no producing command); `3` = `Valid` - The config has no semantic validation errors)"
      format: int32
  securitySchemes:
    ApiKey:
      type: apiKey
      description: >-
        API Key authorization header. Example: "Authorization: ApiKey
        {your-api-key}"
      name: Authorization
      in: header
    Bearer:
      type: http
      description: 'OAuth 2.0 Bearer token. Example: "Authorization: Bearer {access-token}"'
      scheme: bearer
      bearerFormat: JWT

````