# Scores and findings

> The number, and which rule broke on which turn. Two endpoints, one reader's job.

A score without its findings is a number nobody can act on. These two are meant to be read together.

## The endpoints

| | |
|---|---|
| `GET /v1/scores` | The numbers, cursor paged |
| `GET /v1/findings` | What each rule found, cursor paged |

```bash
curl "https://app.evidova.com/v1/scores?session_id=...&limit=50" \
  -H "authorization: Bearer ak_live_..."
```

## Filters both share

| | |
|---|---|
| session_id | One call or chat |
| dimension | One score area |
| client_id, channel | Whose customer, and voice or chat |
| from, to | The window to read |
| limit, cursor | 1 to 200, defaulting to 50, and the next_cursor from the last page |
| verdict | Findings only. What the rule concluded |
| overall | Scores only. The overall number rather than one area |

## What a score carries

| | |
|---|---|
| value | The number itself |
| dimension, outcome | Which score area, and what it came to |
| completeness | How much of the area was actually read |
| hard_cap_applied | True when one automatic fail held the number down on its own |
| rubric_version_id, instrument_version | What produced it |
| evaluated_at | When |

## What a finding carries

| | |
|---|---|
| question | The rule, as the plain question it asks |
| verdict, severity | What it concluded, and how much it matters |
| evidence_turns | The turns it is citing. This is the half that tells somebody what to fix |
| panel | What the second-reading judges said |
| critique, confidence | The reasoning, and how sure it was |
| check_id, rubric_version_id | Which rule, under which frozen set |

> **Note:** Always read `rubric_version_id` before you compare two scores. A score only compares with another frozen under the same rules, and mixing versions in one trend is the commonest way to draw a chart that means nothing.

---

Source: https://evidova.com/docs/api/scores