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

# Account evaluations

> Review saved Account evaluations, including earlier decisions, and the exact signal findings and evidence behind each assessment.

Review the saved evaluations for one Account. Each evaluation keeps its own assessment and the signal findings that support it, matching the portal's evaluation and Findings sections. Earlier evaluations keep their own qualification and score.

Use an Account ID from [Accounts](https://docs.plyne.ai/signals/accounts.md). Compare an evaluation's `id` with the list record's `evaluation.id` to identify the selected evaluation. Results are ordered by evaluation saved time, newest first. An evaluated finding linked under another evaluation is shown within that evaluation's findings rather than repeated as a separate root evaluation.

```bash cURL theme={null}
curl --request POST \
  --url 'https://api.plyne.ai/v1/accounts/co_example_01/evaluations/search' \
  --header 'Authorization: Bearer plyne_...' \
  --header 'Content-Type: application/json' \
  --data '{ "cursor": { "limit": 50 } }'
```

The people, hiring events, and assessments in this response are illustrative.

```json 200 theme={null}
{
  "data": [
    {
      "id": "sig_example_01",
      "found_at": "2026-11-16T09:42:14.086180Z",
      "source_sheet": {
        "id": "sh_example_01",
        "name": "Cloud infrastructure hiring"
      },
      "signal_agent_id": "ag_example_01",
      "qualification": {
        "status": "qualified",
        "reason": "Stripe has an open Senior Backend Engineer role in this example.",
        "reasoning": "A backend engineering opening in the US matches the tracked hiring criteria. Hiring provides relevant context, but the available evidence supports a medium fit score.",
        "references": [
          {
            "type": "evidence",
            "label": "Senior Backend Engineer",
            "url": "https://example.com/jobs/senior-backend-engineer"
          }
        ]
      },
      "ai_score": {
        "value": 64,
        "fit": "medium",
        "reasoning": "A backend engineering opening in the US matches the tracked hiring criteria. Hiring provides relevant context, but the available evidence supports a medium fit score."
      },
      "findings": [
        {
          "id": "sig_example_01",
          "type": "hiring_signals",
          "name": "Hiring Activity",
          "summary": "Stripe has an open Senior Backend Engineer role in this example.",
          "reason": "",
          "found_at": "2026-11-16T09:42:14.086180Z",
          "observed_at": "2026-11-16T09:42:14.086180Z",
          "source_sheet": {
            "id": "sh_example_01",
            "name": "Cloud infrastructure hiring"
          },
          "signal_agent_id": "ag_example_01",
          "qualification": {
            "status": "qualified",
            "reason": "Stripe has an open Senior Backend Engineer role in this example.",
            "reasoning": "A backend engineering opening in the US matches the tracked hiring criteria. Hiring provides relevant context, but the available evidence supports a medium fit score.",
            "references": [
              {
                "type": "evidence",
                "label": "Senior Backend Engineer",
                "url": "https://example.com/jobs/senior-backend-engineer"
              }
            ]
          },
          "ai_score": {
            "value": 64,
            "fit": "medium",
            "reasoning": "A backend engineering opening in the US matches the tracked hiring criteria. Hiring provides relevant context, but the available evidence supports a medium fit score."
          },
          "references": [
            {
              "type": "evidence",
              "label": "Senior Backend Engineer",
              "url": "https://example.com/jobs/senior-backend-engineer"
            }
          ]
        }
      ],
      "findings_cursor": {
        "next": "",
        "has_more": false
      }
    }
  ],
  "cursor": {
    "next": "",
    "has_more": false
  }
}
```

## Request fields

| Field | Location | Meaning |
| - | - | - |
| `account_id` | Path | Required Account ID. |
| `sheet_ids` | Body | Optional source Sheet filters for evaluations. |
| `found_at` | Body | Evaluation saved-time range; inclusive `start_time`, exclusive `end_time`. |
| `cursor.limit` | Body | Evaluation page size; default 50, maximum 100. |
| `cursor.after` | Body | The previous evaluation response's `cursor.next`. Keep the entity and filters unchanged. |

Send `{}` for the first page without filters. Older evaluations are included without a date filter. Results contain saved evaluations, not an immutable revision of every scheduled check.

## Continue reading linked findings

Each evaluation includes at most five visible findings in `findings`, newest saved first. When `findings_cursor.has_more` is true, use [Account signal history](https://docs.plyne.ai/signals/account-signals.md):

```json Linked-finding continuation theme={null}
{
  "evaluation_id": "EVALUATION_ID_FROM_YOUR_RESPONSE",
  "cursor": { "after": "FINDINGS_CURSOR_NEXT_FROM_YOUR_RESPONSE", "limit": 50 }
}
```

Keep `evaluation_id` fixed and leave other filters unset when continuing the embedded preview. Evaluation cursors and finding cursors are separate and cannot be interchanged.

An independently evaluated finding can appear as the evaluation's own finding. A combined evaluation can link several findings. No findings are attached by matching summaries, names, dates, or scores. Missing or hidden findings are not replaced with another source's data.

For all saved findings, including those outside an evaluation, use signal history without `evaluation_id`. For field definitions, see the [Data Dictionary](https://docs.plyne.ai/api/data-dictionary.md).


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