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

# List evaluation sets as an array

> Return an array of evaluation set IDs

Exposed by the verified SDK/ADK versions for trusted development and debugging. Paths depend on the installed ADK version and should not be used as public application entry points

This deprecated endpoint returns an array of evaluation set IDs directly. The replacement returns an object containing `evalSetIds`; update response parsing when migrating

See the [corresponding evaluation endpoint](/productions/api-reference/preview/en/harness-runtime/list-eval-sets) for the replacement and its complete requirements


## OpenAPI

````yaml productions/api-reference/openapi/en/harness-runtime.json GET /dev/apps/{app_name}/eval_sets
openapi: 3.1.0
info:
  title: Harness Runtime
  version: agentkit-cli 0.54.0 / SDK 0.8.0 / ADK 2.2.0
  description: >-
    Harness Runtime deployed by AgentKit CLI 0.54.0, verified with VeADK 1.0.8,
    AgentKit SDK 0.8.0, and Google ADK 2.2.0; scheduled tasks require separate
    enablement
servers:
  - url: http://localhost:8000
    description: Local server
security:
  - {}
  - RuntimeBearer: []
tags:
  - name: Service and applications
  - name: Sessions
  - name: Agent execution
  - name: Artifacts
  - name: Memory
  - name: Evaluation · development server
  - name: Debugging · development server
  - name: Compatibility endpoints
  - name: Harness cronjobs
paths:
  /dev/apps/{app_name}/eval_sets:
    get:
      tags:
        - Compatibility endpoints
      summary: List evaluation sets as an array
      description: >-
        Return an array of evaluation set IDs


        Exposed by the verified SDK/ADK versions for trusted development and
        debugging. Paths depend on the installed ADK version and should not be
        used as public application entry points
      operationId: harnessRuntimeListEvalSetsLegacy
      parameters:
        - name: app_name
          in: path
          required: true
          schema:
            type: string
            title: App Name
          description: Application name; harness_agent for the CLI deployment
          example: harness_agent
      responses:
        '200':
          description: Successful response
          content:
            application/json:
              schema:
                type: array
                items:
                  type: string
                title: >-
                  Response List Eval Sets Legacy Dev Apps  App Name  Eval Sets
                  Get
        '422':
          description: Request validation failed
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      deprecated: true
components:
  schemas:
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
          description: Error details
      type: object
      title: HTTPValidationError
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
              - type: string
              - type: integer
          type: array
          title: Location
          description: Location of the invalid field
        msg:
          type: string
          title: Message
          description: Validation error message
        type:
          type: string
          title: Error Type
        input:
          title: Input
        ctx:
          type: object
          title: Context
      type: object
      required:
        - loc
        - msg
        - type
      title: ValidationError
  securitySchemes:
    RuntimeBearer:
      type: http
      scheme: bearer
      description: >-
        Optional locally without a gateway; cloud deployments use the Runtime
        API key or user-pool JWT required by that deployment, never the model
        API key

````