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

# List feedback for an agent

> Every score the agent has earned, across all its objectives, in one flat stream.

All the [feedback](/docs/api-reference/objectiveservice/submit-feedback-for-an-objective) submitted on any objective this agent has run, newest first. Where [List objective feedback](/docs/api-reference/objectiveservice/list-feedback-for-an-objective) scopes to one run, this is the agent-wide roll-up.

<CodeGroup>
  ```typescript TypeScript theme={null}
  const feedback = await client.agents.feedback.list(agentId, { workspaceId });

  for await (const f of feedback) {
    console.log(f.data.score, f.data.comment, f.info?.submittedBy?.metadata.name);
  }
  // 1    'good'   Global API Key
  // 1    ''       Global API Key
  // -0.2 ''       Global API Key
  ```

  ```go Go theme={null}
  feedback := client.Agents.Feedback.ListAutoPaging(ctx, agentID,
  	cadenya.AgentFeedbackListParams{
  		WorkspaceID: cadenya.String(workspaceID),
  	})

  for feedback.Next() {
  	f := feedback.Current()
  	fmt.Println(f.Data.Score, f.Data.Comment, f.Info.SubmittedBy.Metadata.Name)
  }
  ```

  ```ruby Ruby theme={null}
  feedback = cadenya.agents.feedback.list(agent_id, workspace_id: workspace_id)

  feedback.auto_paging_each do |f|
    puts "#{f.data.score}  #{f.data.comment}  #{f.info&.submitted_by&.metadata&.name}"
  end
  ```

  ```bash cURL theme={null}
  curl "https://api.cadenya.com/v1/workspaces/${WORKSPACE_ID}/agents/${AGENT_ID}/feedback" \
    -H "Authorization: Bearer ${CADENYA_API_KEY}"
  ```
</CodeGroup>

Each entry carries a `score` on `[-1.0, 1.0]`, an optional `comment`, and `info.submittedBy`, the profile that left it.

## It is flat: no per-variation attribution

This is the one thing to know. An entry tells you the score, the note, and who left it, but **not which objective or variation earned it**. There is no `objectiveId` or `variationId` on the row. So this endpoint answers "how is this agent doing overall?", not "which variation is winning?".

For attribution, reach for a different read:

* **Per variation:** [List variations](/docs/api-reference/agentvariationservice/list-variations) returns each variation's aggregate `score` and `feedbackCount`, which is what drives [weighted selection](/docs/guides/agents).
* **Per objective:** [List objective feedback](/docs/api-reference/objectiveservice/list-feedback-for-an-objective) returns the scores on one specific run.

## Search the comments

The `query` param does a free-text search over the comment text, so you can pull the feedback that mentions a theme:

```typescript theme={null}
const refundGripes = await client.agents.feedback.list(agentId, { workspaceId, query: 'refund' });
```

`limit` and `cursor` page the results the usual way.

## Related

<CardGroup cols={2}>
  <Card title="Submit feedback" icon="thumbs-up" href="/docs/api-reference/objectiveservice/submit-feedback-for-an-objective">
    Add a score to an objective, which surfaces here.
  </Card>

  <Card title="List variations" icon="sliders" href="/docs/api-reference/agentvariationservice/list-variations">
    The per-variation `score` this flat stream cannot give you.
  </Card>

  <Card title="List objective feedback" icon="list" href="/docs/api-reference/objectiveservice/list-feedback-for-an-objective">
    The scores on a single run.
  </Card>
</CardGroup>


## OpenAPI

````yaml get /v1/workspaces/{workspaceId}/agents/{agentId}/feedback
openapi: 3.1.0
info:
  title: Cadenya API
  description: API for the Cadenya Agent Runtime platform.
  version: '1.0'
servers:
  - url: https://api.cadenya.com
    description: Production server
security:
  - bearerAuth: []
tags:
  - name: AIProviderKeyService
  - name: APIKeyService
    description: |-
      Issue, rotate, disable, and revoke a workspace's API keys. Every key
       belongs to exactly one workspace; the system-managed global account key is
       managed via GlobalAPIKeyService instead.
  - name: AccountService
    description: >-
      Manage the authenticated account. Accounts are the top-level
      organizational
       unit and contain one or more workspaces.
  - name: AgentScheduleService
    description: >-
      Manage recurring schedules attached to agents. Schedules trigger
      objectives
       on a cadence defined by AgentScheduleSpec.Schedule.
  - name: AgentService
    description: >-
      Manage AI agents within a workspace. Agents define AI behavior and tool
      access.
  - name: AgentVariationService
    description: >-
      Manage variations of an agent and their tool, sub-agent, and memory layer
      assignments.
  - name: GlobalAPIKeyService
    description: |-
      Manage the account's system-provisioned global API key. The global key is
       the only key that spans every workspace; it is created by the system and
       cannot be deleted, so the surface is retrieve, rotate, and the
       disable/enable kill switch.
  - name: MemoryService
    description: >-
      Manage memory layers and their entries. Layers are named containers that
      can
       be composed into an objective's memory cascade; entries are the keyed values
       within a layer. System-managed layers (e.g., episodic layers created by the
       runtime) cannot be mutated through this API.
  - name: ModelService
    description: |-
      Manage LLM models available to a workspace. Models represent provider and
       family pairs (e.g., "anthropic/claude-sonnet-4.6"). Workspaces are seeded
       with the supported models and you can enable or disable each one.
  - name: ObjectiveEventStreamsService
  - name: ObjectiveService
  - name: ProfilesService
    description: |-
      Operations on profiles, the account-level principals (users, API keys,
       system) that authenticate against the API.
  - name: SearchService
  - name: TenantService
    description: >-
      Read and erase tenants and the subjects under them. Tenants and subjects
      are
       created by assertion — on objective creation or widget session mint — never
       directly, so this service has no create or update: it exists to enumerate what
       assertions have produced, and to destroy it on request.
  - name: ToolService
    description: >-
      Manage tool sets and the tools they contain. Tool sets group related
      tools,
       and tools define specific capabilities available to agents.

       When a tool set is managed, only API key actors can modify its tools; human
       (profile) actors cannot.
  - name: UploadService
    description: |-
      Issue short-lived presigned URLs for direct client-to-object-storage
       uploads. Created uploads can be referenced by id when creating or updating
       resources that accept binary content (e.g., MemoryEntry).
  - name: WidgetService
    description: |-
      Manage embeddable chat widgets. A widget binds an agent to a globally
       unique hostname with a per-widget origin allowlist; browsers reach it with
       session tokens minted via WidgetSessionService.
  - name: WidgetSessionService
    description: >-
      Mint and manage widget sessions. Session creation is server-to-server
      only:
       the customer's backend authenticates its visitor, asserts tenant/subject
       context, attaches any per-visitor secrets, and receives a short-lived
       bearer token the browser uses against the widget host.
  - name: WorkspaceAdminService
    description: >-
      Administer workspaces across the account: create and archive workspaces
      and
       manage their membership. These operations are account-scoped and require the
       admin role (a token whose profile holds the WorkOS admin role); they live
       under /v1/account/workspaces rather than the workspace-scoped /v1/workspaces
       tree so an admin can manage any workspace in the account, including ones they
       are not themselves a member of.
  - name: WorkspaceSecretService
  - name: WorkspaceService
    description: |-
      Manage workspaces within an account. Workspaces provide organizational
       grouping and isolation for resources such as agents, tools, and API keys.

       This is the workspace-scoped, end-user surface. Administrative operations
       (create / archive workspaces, manage members) live in WorkspaceAdminService
       under /v1/account/workspaces and require the admin role.
paths:
  /v1/workspaces/{workspaceId}/agents/{agentId}/feedback:
    get:
      tags:
        - AgentService
        - Agents
      summary: List feedback for an agent
      description: >-
        Lists feedback submitted across all objectives belonging to an agent.
        Supports search by comment, sentiment filter, agent variation filter,
        and creation date range. Results are ordered by creation time, newest
        first.
      operationId: AgentService_ListAgentFeedback
      parameters:
        - name: workspaceId
          in: path
          required: true
          schema:
            type: string
            example: workspace_01HXKD2E5NQM3T9AYWCF133E3Q
        - name: agentId
          in: path
          description: >-
            The ID of the agent. Supports "external_id:" prefix for external
            IDs.
          required: true
          schema:
            example: agent_01HXKD2E5NQM3T9AYWCFMGWT9Y
            type: string
        - name: limit
          in: query
          description: Maximum number of results to return.
          schema:
            type: integer
            format: int32
        - name: cursor
          in: query
          description: Pagination cursor from previous response.
          schema:
            type: string
        - name: query
          in: query
          description: >-
            Free-text search applied to the feedback comment. Case-insensitive
            substring match.
          schema:
            type: string
        - name: sentiment
          in: query
          description: >-
            Filter by sentiment. UNSPECIFIED returns feedback regardless of
            score.
          schema:
            enum:
              - FEEDBACK_SENTIMENT_UNSPECIFIED
              - FEEDBACK_SENTIMENT_POSITIVE
              - FEEDBACK_SENTIMENT_NEGATIVE
            type: string
            format: enum
        - name: agentVariationId
          in: query
          description: >-
            Optional filter to limit results to feedback on objectives run by a
            single
             agent variation. Supports "external_id:" prefix for external IDs.
          schema:
            type: string
        - name: createdAfter
          in: query
          description: Inclusive lower bound on feedback creation time.
          schema:
            type: string
            format: date-time
        - name: createdBefore
          in: query
          description: Exclusive upper bound on feedback creation time.
          schema:
            type: string
            format: date-time
        - name: labels
          in: query
          description: |-
            Filters by metadata labels. Comma-separated key=value pairs,
             e.g. "env=prod,team=ai". A resource matches only if every pair
             matches exactly (AND semantics).
          schema:
            type: string
        - name: includeInfo
          in: query
          description: When set to true you may use more of your alloted API rate-limit
          schema:
            type: boolean
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ListAgentFeedbackResponse'
        default:
          description: Default error response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Status'
      x-codeSamples:
        - lang: JavaScript
          source: |-
            import Cadenya from '@cadenya/cadenya';

            const client = new Cadenya({
              apiKey: process.env['CADENYA_API_KEY'], // This is the default and can be omitted
            });

            // Automatically fetches more pages as needed.
            for await (const objectiveFeedback of client.agents.feedback.list(
              'agent_01HXKD2E5NQM3T9AYWCFMGWT9Y',
              { workspaceId: 'workspace_01HXKD2E5NQM3T9AYWCF133E3Q' },
            )) {
              console.log(objectiveFeedback.data);
            }
        - lang: Python
          source: |-
            import os
            from cadenya import Cadenya

            client = Cadenya(
                api_key=os.environ.get("CADENYA_API_KEY"),  # This is the default and can be omitted
            )
            page = client.agents.feedback.list(
                agent_id="agent_01HXKD2E5NQM3T9AYWCFMGWT9Y",
                workspace_id="workspace_01HXKD2E5NQM3T9AYWCF133E3Q",
            )
            page = page.items[0]
            print(page.data)
        - lang: Go
          source: "package main\n\nimport (\n\t\"context\"\n\t\"fmt\"\n\t\"go.cadenya.com/cadenya-go\"\n\t\"go.cadenya.com/cadenya-go/option\"\n)\n\nfunc main() {\n\tclient := cadenya.NewClient(\n\t\toption.WithAPIKey(\"My API Key\"),\n\t)\n\tpage, err := client.Agents.Feedback.List(\n\t\tcontext.TODO(),\n\t\t\"agent_01HXKD2E5NQM3T9AYWCFMGWT9Y\",\n\t\tcadenya.AgentFeedbackListParams{\n\t\t\tWorkspaceID: cadenya.String(\"workspace_01HXKD2E5NQM3T9AYWCF133E3Q\"),\n\t\t},\n\t)\n\tif err != nil {\n\t\tpanic(err.Error())\n\t}\n\tfmt.Printf(\"%+v\\n\", page)\n}\n"
        - lang: Ruby
          source: |-
            require "cadenya"

            cadenya = Cadenya::Client.new(api_key: "My API Key")

            page = cadenya.agents.feedback.list(
              "agent_01HXKD2E5NQM3T9AYWCFMGWT9Y",
              workspace_id: "workspace_01HXKD2E5NQM3T9AYWCF133E3Q"
            )

            puts(page)
        - lang: CLI
          source: |-
            cadenya agents:feedback list \
              --api-key 'My API Key' \
              --workspace-id workspace_01HXKD2E5NQM3T9AYWCF133E3Q \
              --agent-id agent_01HXKD2E5NQM3T9AYWCFMGWT9Y
components:
  schemas:
    ListAgentFeedbackResponse:
      type: object
      properties:
        items:
          type: array
          items:
            $ref: '#/components/schemas/ObjectiveFeedback'
        pagination:
          $ref: '#/components/schemas/Page'
      description: Response for listing feedback across an agent.
    Status:
      type: object
      properties:
        code:
          type: integer
          description: >-
            The status code, which should be an enum value of
            [google.rpc.Code][google.rpc.Code].
          format: int32
        message:
          type: string
          description: >-
            A developer-facing error message, which should be in English. Any
            user-facing error message should be localized and sent in the
            [google.rpc.Status.details][google.rpc.Status.details] field, or
            localized by the client.
        details:
          type: array
          items:
            $ref: '#/components/schemas/GoogleProtobufAny'
          description: >-
            A list of messages that carry the error details.  There is a common
            set of message types for APIs to use.
      description: >-
        The `Status` type defines a logical error model that is suitable for
        different programming environments, including REST APIs and RPC APIs. It
        is used by [gRPC](https://github.com/grpc). Each `Status` message
        contains three pieces of data: error code, error message, and error
        details. You can find out more about this error model and how to work
        with it in the [API Design
        Guide](https://cloud.google.com/apis/design/errors).
    ObjectiveFeedback:
      required:
        - metadata
        - data
      type: object
      properties:
        metadata:
          $ref: '#/components/schemas/OperationMetadata'
        data:
          $ref: '#/components/schemas/ObjectiveFeedbackData'
        info:
          $ref: '#/components/schemas/ObjectiveFeedbackInfo'
      description: >-
        ObjectiveFeedback represents feedback submitted for an objective's
        execution.
         Feedback is used to score agent variations and improve agent performance over time.
    Page:
      type: object
      properties:
        nextCursor:
          type: string
      description: >-
        Page carries cursor-based pagination state. There is no total: the
        cursor
         walks the result set without ever counting it, and a count would cost a second
         query on every list.
    GoogleProtobufAny:
      type: object
      properties:
        '@type':
          type: string
          description: The type of the serialized message.
      additionalProperties: true
      description: >-
        Contains an arbitrary serialized message along with a @type that
        describes the type of the serialized message.
    OperationMetadata:
      required:
        - id
        - accountId
        - workspaceId
        - profileId
        - createdAt
      type: object
      properties:
        id:
          readOnly: true
          type: string
          description: >-
            Unique identifier for the operation (prefixed ULID, e.g.,
            "obj_01HXK...")
        accountId:
          readOnly: true
          example: account_01HXKD2E5NQM3T9AYWCFTJHJVF
          type: string
          description: >-
            Account this operation belongs to for multi-tenant isolation
            (prefixed ULID)
        workspaceId:
          readOnly: true
          example: workspace_01HXKD2E5NQM3T9AYWCF133E3Q
          type: string
          description: >-
            Workspace this operation belongs to for organizational grouping
            (prefixed ULID)
        labels:
          type: object
          additionalProperties:
            type: string
          description: |-
            Key-value pairs for categorization and filtering. Values are 0-63
             alphanumeric characters with "-", "_", or "." allowed between; keys
             follow the same shape and additionally accept an optional DNS-subdomain
             prefix (e.g. "cadenya.com/") of at most 253 characters.
             Examples: {"priority": "high", "source": "api", "workflow": "onboarding"}
        createdAt:
          readOnly: true
          type: string
          description: |-
            Timestamp when this operation was created
             ULID includes timestamp information, but this explicit field enables easier querying
          format: date-time
        externalId:
          type: string
          description: >-
            External ID for the operation (e.g., a workflow ID from an external
            system)
        profileId:
          readOnly: true
          example: profile_01HXKD2E5NQM3T9AYWCFS0AP08
          type: string
          description: >-
            ID of the actor (user or service account) that created this
            operation
      description: >-
        Metadata for ephemeral operations and activities (e.g., objectives,
        executions, runs)
    ObjectiveFeedbackData:
      type: object
      properties:
        score:
          type: number
          description: >-
            A score between -1.0 and 1.0 representing the quality of the
            objective's execution.
             -1.0 is the worst possible score, 0.0 is neutral, and 1.0 is the best.
          format: float
        comment:
          type: string
          description: Optional human-readable comment explaining the feedback
    ObjectiveFeedbackInfo:
      type: object
      properties:
        submittedBy:
          readOnly: true
          allOf:
            - $ref: '#/components/schemas/Profile'
          description: The profile that submitted the feedback
        objective:
          readOnly: true
          allOf:
            - $ref: '#/components/schemas/BareMetadata'
          description: The objective the feedback was submitted for.
        agentVariation:
          readOnly: true
          allOf:
            - $ref: '#/components/schemas/BareMetadata'
          description: >-
            The agent variation that executed the objective this feedback is
            about.
    Profile:
      required:
        - metadata
        - spec
      type: object
      properties:
        metadata:
          $ref: '#/components/schemas/AccountResourceMetadata'
        spec:
          $ref: '#/components/schemas/ProfileSpec'
      description: |-
        A profile identifies a user or non-human principal (such as an API key)
         at the account level. Profiles are account-scoped and can be granted access
         to multiple workspaces.
    BareMetadata:
      type: object
      properties:
        id:
          readOnly: true
          type: string
        name:
          readOnly: true
          type: string
          description: >-
            Human-readable name of the referenced resource, populated by the
            server
             on reads for convenience. Absent on references to resources that do not
             have a name (e.g., objective tasks).
      description: |-
        BareMetadata contains the minimal metadata for a resource: the ID and an
         optional human-readable name. These are used for reference fields where the
         full metadata (account scoping, timestamps, labels, external IDs) is not
         needed — e.g., the tool references inside an agent variation spec or the
         tools assigned to an objective. Both fields are server-populated; clients
         provide IDs through sibling fields rather than by constructing a
         BareMetadata themselves.
    AccountResourceMetadata:
      required:
        - id
        - accountId
        - name
        - profileId
      type: object
      properties:
        id:
          readOnly: true
          type: string
          description: >-
            Unique identifier for the resource (prefixed ULID, e.g.,
            "apikey_01HXK...")
        accountId:
          readOnly: true
          example: account_01HXKD2E5NQM3T9AYWCFTJHJVF
          type: string
          description: >-
            Account this resource belongs to for multi-tenant isolation
            (prefixed ULID)
        name:
          type: string
          description: >-
            Human-readable name for the resource (e.g., "Customer Support
            Agent", "Email Tool")
             Required for resources that users interact with directly
        externalId:
          type: string
          description: >-
            External ID for the resource (e.g., a workflow ID from an external
            system)
        labels:
          type: object
          additionalProperties:
            type: string
          description: |-
            Key-value pairs for categorization and filtering. Values are 0-63
             alphanumeric characters with "-", "_", or "." allowed between; keys
             follow the same shape and additionally accept an optional DNS-subdomain
             prefix (e.g. "cadenya.com/") of at most 253 characters.
             Examples: {"environment": "production", "team": "platform", "version": "v2"}
        profileId:
          readOnly: true
          example: profile_01HXKD2E5NQM3T9AYWCFS0AP08
          type: string
        createdAt:
          readOnly: true
          type: string
          format: date-time
      description: >-
        AccountResourceMetadata is used to represent a resource that is
        associated to an account but not to a workspace.
    ProfileSpec:
      required:
        - type
      type: object
      properties:
        email:
          type: string
          description: >-
            Email address of the profile. Required and unique within an account
            for
             user profiles.
        name:
          type: string
          description: Display name (e.g., "Bobby Tables").
        type:
          enum:
            - PROFILE_TYPE_UNSPECIFIED
            - PROFILE_TYPE_USER
            - PROFILE_TYPE_API_KEY
            - PROFILE_TYPE_SYSTEM
          type: string
          description: >-
            Whether this profile represents a human user, an API key, or a
            system
             principal.
          format: enum
      description: Configuration for a profile.
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT

````