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

# List an eval run's verdicts

> Returns the judge's verdict on every test case of every graded call, oldest first, including the judge's reasoning. Verdicts appear as calls are graded, so you can poll this while the run is in progress. Narrow the list with `test_case_id` and/or `call_id`; an empty value means no filter.



## OpenAPI

````yaml /api-reference/voice-openapi.json get /v1/projects/{projectId}/agents/{agentId}/eval-submissions/{id}/verdicts
openapi: 3.0.3
info:
  title: Clarity Voice API
  version: '1.0'
  description: Voice agents, outbound calls, conversations, campaigns, and evals.
servers:
  - url: https://voice-api.onclarity.com
security:
  - organizationApiKey: []
tags:
  - name: Projects
    description: >-
      The projects your organization owns. Every other resource lives in a
      project.
  - name: Agents
    description: Create, configure, version and publish voice agents.
  - name: Outbound calls
    description: Have a published agent phone a number now.
  - name: Conversations
    description: >-
      One record per call session, with its calls, recordings, transcripts and
      artifacts.
  - name: Calls
    description: The calls of a project, with their status, direction, timing and outcome.
  - name: Campaigns
    description: Outbound calling campaigns that phone a list of numbers on a schedule.
  - name: Eval suites
    description: >-
      Reusable sets of eval scenarios and test cases to measure an agent
      against.
  - name: Eval judges
    description: The LLM judges that score eval calls against your test cases.
  - name: Eval scenarios
    description: The simulated-caller scenarios of your eval suites.
  - name: Eval test cases
    description: The checks a judge applies to each eval call.
  - name: Eval submissions
    description: Run an eval suite against an agent and read the verdicts.
paths:
  /v1/projects/{projectId}/agents/{agentId}/eval-submissions/{id}/verdicts:
    parameters:
      - $ref: '#/components/parameters/ProjectIdPath'
      - name: agentId
        in: path
        required: true
        schema:
          type: string
        description: Agent id
      - name: id
        in: path
        required: true
        schema:
          type: string
        description: Eval submission id
    get:
      tags:
        - Eval submissions
      summary: List an eval run's verdicts
      description: >-
        Returns the judge's verdict on every test case of every graded call,
        oldest first, including the judge's reasoning. Verdicts appear as calls
        are graded, so you can poll this while the run is in progress. Narrow
        the list with `test_case_id` and/or `call_id`; an empty value means no
        filter.
      operationId: listAgentEvalSubmissionVerdicts
      parameters:
        - name: test_case_id
          in: query
          required: false
          schema:
            type: string
          description: Only verdicts for this test case
        - name: call_id
          in: query
          required: false
          schema:
            type: string
          description: Only verdicts for this call
      responses:
        '200':
          description: The verdicts
          content:
            application/json:
              schema:
                type: object
                required:
                  - verdicts
                properties:
                  verdicts:
                    type: array
                    items:
                      $ref: '#/components/schemas/EvalVerdict'
              example:
                verdicts:
                  - id: vrd_01
                    submission_id: sub_01J9
                    call_id: call_01
                    test_case_id: tc_7f3a
                    source: common
                    verdict: passed
                    reasoning: >-
                      The agent read back Thursday 10:00 and the caller
                      confirmed.
                    error: null
                    judged_at: '2026-10-22T14:09:12.000Z'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '404':
          description: >-
            The project, agent or eval submission does not exist, or your
            credential cannot see it.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
              example:
                error: Eval submission not found
        '422':
          description: >-
            Validation failed, or the agent is a Voice Assist agent, which
            cannot take test calls (`code: AGENT_TYPE_NOT_DISPATCHABLE`).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ValidationError'
              example:
                error: >-
                  agent type assist cannot take calls: an assist agent listens
                  to a human-operated call and never speaks
                code: AGENT_TYPE_NOT_DISPATCHABLE
                agent_type: assist
                agent_id: agent_456
components:
  parameters:
    ProjectIdPath:
      name: projectId
      in: path
      required: true
      schema:
        type: string
      description: Project id
  schemas:
    EvalVerdict:
      type: object
      description: The judge's verdict on one test case for one call.
      properties:
        id:
          type: string
        submission_id:
          type: string
        call_id:
          type: string
        test_case_id:
          type: string
        source:
          type: string
          enum:
            - scenario
            - common
          description: >-
            `common`: checked on every call. `scenario`: checked only in its
            scenario.
        verdict:
          type: string
          enum:
            - passed
            - failed
            - not_relevant
            - not_sure
            - error
        reasoning:
          type: string
          nullable: true
          description: The judge's explanation
        error:
          type: string
          nullable: true
        judged_at:
          type: string
          format: date-time
    Error:
      type: object
      required:
        - error
      additionalProperties: true
      properties:
        error:
          type: string
          description: Error message
        code:
          type: string
          description: >-
            A stable machine-readable reason, present on the refusals a client
            may branch on. Among them: `PUBLISH_CAPABILITY_REQUIRED` (403, the
            credential may not change what is live), `AGENT_NOT_PUBLISHED` (409,
            the agent has no published version yet),
            `AGENT_TYPE_NOT_DISPATCHABLE` (422, a Voice Assist agent named where
            an agent must place or take a call; the body carries `agent_type`
            and `agent_id`), `NOT_APPLICABLE_TO_AGENT_TYPE` (422, a voice-only
            setting written on a Voice Assist agent), `AGENT_TYPE_BOUNDARY`
            (409), `AGENT_TYPE_NOT_SUPPORTED` (400), `VOICE_ASSISTANT_REQUIRED`
            (403, the organization is not licensed for Voice Assist),
            `ORGANIZATION_UNAVAILABLE` (503) and `REGION_PROFILE_CONFLICT`
            (503).
    ValidationError:
      type: object
      description: >-
        A validation failure. `error` is a human-readable summary; `issues`
        (request validation) or `details` (agent configuration validation)
        locate each problem.
      properties:
        error:
          type: string
        message:
          type: string
        issues:
          type: array
          items:
            type: object
            properties:
              path:
                type: string
                description: Dotted path of the offending field
              code:
                type: string
              message:
                type: string
        details:
          type: array
          items: {}
  responses:
    Unauthorized:
      description: No credential was sent, or the API key is invalid or revoked.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error: Invalid or revoked token
  securitySchemes:
    organizationApiKey:
      type: http
      scheme: bearer
      description: >-
        Your organization API key (it starts with `anek_org_`). The same key
        works on the Voice API and the Support API. See
        [Authentication](/authentication).

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.