# Feedback

## Submit feedback for an objective

`$ cadenya objectives:feedback create`

**post** `/v1/objectives/{objectiveId}/feedback`

Submits feedback for an objective's execution. Feedback scores are used by the agent variation scoring system to evaluate and rank variation performance.

### Parameters

- `--objective-id: string`

  The ID of the objective. Supports "external_id:" prefix for external IDs.

- `--data: object { attributes, comment, score }`

### Returns

- `objective_feedback: object { data, metadata, info }`

  ObjectiveFeedback represents feedback submitted for an objective's execution.
  Feedback is used to score agent variations and improve agent performance over time.

  - `data: object { attributes, comment, score }`

    - `attributes: optional map[string]`

      Arbitrary key-value pairs to identify the source of the feedback.
      Since the submitting profile is typically an API key, use this to pass through
      application-specific identifiers (e.g., {"user_id": "usr_123", "session_id": "abc"}).

    - `comment: optional string`

      Optional human-readable comment explaining the feedback

    - `score: optional number`

      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.

  - `metadata: object { id, name }`

    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.

    - `id: optional string`

    - `name: optional string`

      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).

  - `info: optional object { submittedBy }`

    - `submittedBy: optional object { metadata, spec }`

      Profile represents a human user at the account level.
      Profiles are account-scoped resources that can be associated with multiple workspaces
      through the Actor model. Authentication for profiles is handled via SSO/OAuth (WorkOS).

      - `metadata: object { id, accountId, name, 3 more }`

        AccountResourceMetadata is used to represent a resource that is associated to an account but not to a workspace.

        - `id: string`

          Unique identifier for the resource (prefixed ULID, e.g., "apikey_01HXK...")

        - `accountId: string`

          Account this resource belongs to for multi-tenant isolation (prefixed ULID)

        - `name: string`

          Human-readable name for the resource (e.g., "Customer Support Agent", "Email Tool")
          Required for resources that users interact with directly

        - `profileId: string`

        - `externalId: optional string`

          External ID for the resource (e.g., a workflow ID from an external system)

        - `labels: optional map[string]`

          Arbitrary key-value pairs for categorization and filtering
          Examples: {"environment": "production", "team": "platform", "version": "v2"}

      - `spec: object { type, email, name }`

        ProfileSpec contains the profile-specific fields

        - `type: "PROFILE_TYPE_USER" or "PROFILE_TYPE_API_KEY" or "PROFILE_TYPE_SYSTEM"`

          Type is the type of profile. User's are humans, API keys are computers. You know the deal.

          - `"PROFILE_TYPE_USER"`

          - `"PROFILE_TYPE_API_KEY"`

          - `"PROFILE_TYPE_SYSTEM"`

        - `email: optional string`

          Email address of the user (required, unique per account)

        - `name: optional string`

          Display name for the user (e.g., "Bobby Tables")

### Example

```cli
cadenya objectives:feedback create \
  --api-key 'My API Key' \
  --objective-id objectiveId \
  --data '{}'
```

#### Response

```json
{
  "data": {
    "attributes": {
      "foo": "string"
    },
    "comment": "comment",
    "score": 0
  },
  "metadata": {
    "id": "id",
    "name": "name"
  },
  "info": {
    "submittedBy": {
      "metadata": {
        "id": "id",
        "accountId": "accountId",
        "name": "name",
        "profileId": "profileId",
        "externalId": "externalId",
        "labels": {
          "foo": "string"
        }
      },
      "spec": {
        "type": "PROFILE_TYPE_USER",
        "email": "email",
        "name": "name"
      }
    }
  }
}
```

## List feedback for an objective

`$ cadenya objectives:feedback list`

**get** `/v1/objectives/{objectiveId}/feedback`

Lists all feedback submitted for an objective

### Parameters

- `--objective-id: string`

  The ID of the objective. Supports "external_id:" prefix for external IDs.

- `--cursor: optional string`

  Pagination cursor from previous response

- `--limit: optional number`

  Maximum number of results to return

### Returns

- `ListObjectiveFeedbackResponse: object { items, pagination }`

  Response for listing feedback

  - `items: optional array of ObjectiveFeedback`

    - `data: object { attributes, comment, score }`

      - `attributes: optional map[string]`

        Arbitrary key-value pairs to identify the source of the feedback.
        Since the submitting profile is typically an API key, use this to pass through
        application-specific identifiers (e.g., {"user_id": "usr_123", "session_id": "abc"}).

      - `comment: optional string`

        Optional human-readable comment explaining the feedback

      - `score: optional number`

        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.

    - `metadata: object { id, name }`

      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.

      - `id: optional string`

      - `name: optional string`

        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).

    - `info: optional object { submittedBy }`

      - `submittedBy: optional object { metadata, spec }`

        Profile represents a human user at the account level.
        Profiles are account-scoped resources that can be associated with multiple workspaces
        through the Actor model. Authentication for profiles is handled via SSO/OAuth (WorkOS).

        - `metadata: object { id, accountId, name, 3 more }`

          AccountResourceMetadata is used to represent a resource that is associated to an account but not to a workspace.

          - `id: string`

            Unique identifier for the resource (prefixed ULID, e.g., "apikey_01HXK...")

          - `accountId: string`

            Account this resource belongs to for multi-tenant isolation (prefixed ULID)

          - `name: string`

            Human-readable name for the resource (e.g., "Customer Support Agent", "Email Tool")
            Required for resources that users interact with directly

          - `profileId: string`

          - `externalId: optional string`

            External ID for the resource (e.g., a workflow ID from an external system)

          - `labels: optional map[string]`

            Arbitrary key-value pairs for categorization and filtering
            Examples: {"environment": "production", "team": "platform", "version": "v2"}

        - `spec: object { type, email, name }`

          ProfileSpec contains the profile-specific fields

          - `type: "PROFILE_TYPE_USER" or "PROFILE_TYPE_API_KEY" or "PROFILE_TYPE_SYSTEM"`

            Type is the type of profile. User's are humans, API keys are computers. You know the deal.

            - `"PROFILE_TYPE_USER"`

            - `"PROFILE_TYPE_API_KEY"`

            - `"PROFILE_TYPE_SYSTEM"`

          - `email: optional string`

            Email address of the user (required, unique per account)

          - `name: optional string`

            Display name for the user (e.g., "Bobby Tables")

  - `pagination: optional object { nextCursor, total }`

    - `nextCursor: optional string`

    - `total: optional number`

### Example

```cli
cadenya objectives:feedback list \
  --api-key 'My API Key' \
  --objective-id objectiveId
```

#### Response

```json
{
  "items": [
    {
      "data": {
        "attributes": {
          "foo": "string"
        },
        "comment": "comment",
        "score": 0
      },
      "metadata": {
        "id": "id",
        "name": "name"
      },
      "info": {
        "submittedBy": {
          "metadata": {
            "id": "id",
            "accountId": "accountId",
            "name": "name",
            "profileId": "profileId",
            "externalId": "externalId",
            "labels": {
              "foo": "string"
            }
          },
          "spec": {
            "type": "PROFILE_TYPE_USER",
            "email": "email",
            "name": "name"
          }
        }
      }
    }
  ],
  "pagination": {
    "nextCursor": "nextCursor",
    "total": 0
  }
}
```

## Domain Types

### Objective Feedback

- `objective_feedback: object { data, metadata, info }`

  ObjectiveFeedback represents feedback submitted for an objective's execution.
  Feedback is used to score agent variations and improve agent performance over time.

  - `data: object { attributes, comment, score }`

    - `attributes: optional map[string]`

      Arbitrary key-value pairs to identify the source of the feedback.
      Since the submitting profile is typically an API key, use this to pass through
      application-specific identifiers (e.g., {"user_id": "usr_123", "session_id": "abc"}).

    - `comment: optional string`

      Optional human-readable comment explaining the feedback

    - `score: optional number`

      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.

  - `metadata: object { id, name }`

    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.

    - `id: optional string`

    - `name: optional string`

      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).

  - `info: optional object { submittedBy }`

    - `submittedBy: optional object { metadata, spec }`

      Profile represents a human user at the account level.
      Profiles are account-scoped resources that can be associated with multiple workspaces
      through the Actor model. Authentication for profiles is handled via SSO/OAuth (WorkOS).

      - `metadata: object { id, accountId, name, 3 more }`

        AccountResourceMetadata is used to represent a resource that is associated to an account but not to a workspace.

        - `id: string`

          Unique identifier for the resource (prefixed ULID, e.g., "apikey_01HXK...")

        - `accountId: string`

          Account this resource belongs to for multi-tenant isolation (prefixed ULID)

        - `name: string`

          Human-readable name for the resource (e.g., "Customer Support Agent", "Email Tool")
          Required for resources that users interact with directly

        - `profileId: string`

        - `externalId: optional string`

          External ID for the resource (e.g., a workflow ID from an external system)

        - `labels: optional map[string]`

          Arbitrary key-value pairs for categorization and filtering
          Examples: {"environment": "production", "team": "platform", "version": "v2"}

      - `spec: object { type, email, name }`

        ProfileSpec contains the profile-specific fields

        - `type: "PROFILE_TYPE_USER" or "PROFILE_TYPE_API_KEY" or "PROFILE_TYPE_SYSTEM"`

          Type is the type of profile. User's are humans, API keys are computers. You know the deal.

          - `"PROFILE_TYPE_USER"`

          - `"PROFILE_TYPE_API_KEY"`

          - `"PROFILE_TYPE_SYSTEM"`

        - `email: optional string`

          Email address of the user (required, unique per account)

        - `name: optional string`

          Display name for the user (e.g., "Bobby Tables")

### Objective Feedback Data

- `objective_feedback_data: object { attributes, comment, score }`

  - `attributes: optional map[string]`

    Arbitrary key-value pairs to identify the source of the feedback.
    Since the submitting profile is typically an API key, use this to pass through
    application-specific identifiers (e.g., {"user_id": "usr_123", "session_id": "abc"}).

  - `comment: optional string`

    Optional human-readable comment explaining the feedback

  - `score: optional number`

    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.

### Objective Feedback Info

- `objective_feedback_info: object { submittedBy }`

  - `submittedBy: optional object { metadata, spec }`

    Profile represents a human user at the account level.
    Profiles are account-scoped resources that can be associated with multiple workspaces
    through the Actor model. Authentication for profiles is handled via SSO/OAuth (WorkOS).

    - `metadata: object { id, accountId, name, 3 more }`

      AccountResourceMetadata is used to represent a resource that is associated to an account but not to a workspace.

      - `id: string`

        Unique identifier for the resource (prefixed ULID, e.g., "apikey_01HXK...")

      - `accountId: string`

        Account this resource belongs to for multi-tenant isolation (prefixed ULID)

      - `name: string`

        Human-readable name for the resource (e.g., "Customer Support Agent", "Email Tool")
        Required for resources that users interact with directly

      - `profileId: string`

      - `externalId: optional string`

        External ID for the resource (e.g., a workflow ID from an external system)

      - `labels: optional map[string]`

        Arbitrary key-value pairs for categorization and filtering
        Examples: {"environment": "production", "team": "platform", "version": "v2"}

    - `spec: object { type, email, name }`

      ProfileSpec contains the profile-specific fields

      - `type: "PROFILE_TYPE_USER" or "PROFILE_TYPE_API_KEY" or "PROFILE_TYPE_SYSTEM"`

        Type is the type of profile. User's are humans, API keys are computers. You know the deal.

        - `"PROFILE_TYPE_USER"`

        - `"PROFILE_TYPE_API_KEY"`

        - `"PROFILE_TYPE_SYSTEM"`

      - `email: optional string`

        Email address of the user (required, unique per account)

      - `name: optional string`

        Display name for the user (e.g., "Bobby Tables")