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

# Score one result

> Writes a verdict onto a result. Scoring under a different `judged_by` adds a verdict rather than replacing the first, so two judges on one run can be compared instead of one silently overwriting the other. The run's totals follow.



## OpenAPI

````yaml /api/statisfy-api.openapi.json post /v1/evaluations/results/score
openapi: 3.1.0
info:
  description: >-
    The agent-first Statisfy API. Authenticate with an API key (`Authorization:
    Bearer stfy_live_…`), then call `GET /v1/meta/capabilities` to discover
    every operation and its schemas.
  title: Statisfy API
  version: 1.0.0
servers:
  - url: https://api.statisfy.com
    description: Production
security: []
paths:
  /v1/evaluations/results/score:
    post:
      tags:
        - evaluations
      summary: Score one result
      description: >-
        Writes a verdict onto a result. Scoring under a different `judged_by`
        adds a verdict rather than replacing the first, so two judges on one run
        can be compared instead of one silently overwriting the other. The run's
        totals follow.
      operationId: evaluations_score
      requestBody:
        content:
          application/json:
            schema:
              additionalProperties: false
              properties:
                judged_by:
                  description: >-
                    Who formed this verdict. Scoring with a different name adds
                    a verdict rather than replacing the first, so two judges on
                    one run stay comparable.
                  maxLength: 100
                  minLength: 1
                  title: Judged By
                  type: string
                passed:
                  anyOf:
                    - type: boolean
                    - type: 'null'
                  default: null
                  description: Defaults to `scores.passed`.
                  title: Passed
                reason:
                  anyOf:
                    - type: string
                    - type: 'null'
                  default: null
                  description: Defaults to `scores.reason`.
                  title: Reason
                result_id:
                  description: >-
                    The result being scored, from GET
                    /v1/evaluations/runs/{run_id}/results.
                  title: Result Id
                  type: string
                scores:
                  additionalProperties: true
                  description: >-
                    The verdict, in whatever shape the judge uses. `passed` and
                    `score_1_5` are read for the run's totals; everything else
                    is kept as sent.
                  title: Scores
                  type: object
              required:
                - result_id
                - scores
                - judged_by
              type: object
        required: true
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Result'
          description: Successful Response
      security:
        - HTTPBearer: []
components:
  schemas:
    Result:
      properties:
        case_id:
          title: Case Id
          type: string
        defer_reason:
          anyOf:
            - type: string
            - type: 'null'
          title: Defer Reason
        deferred:
          default: false
          description: >-
            The worker handed the thread to a human instead of answering.
            Reactive runs only.
          title: Deferred
          type: boolean
        error:
          anyOf:
            - type: string
            - type: 'null'
          description: >-
            The session's own failure. Distinct from a failing verdict: this
            case produced nothing to judge.
          title: Error
        id:
          title: Id
          type: string
        judged_by:
          anyOf:
            - type: string
            - type: 'null'
          title: Judged By
        output:
          anyOf:
            - additionalProperties: true
              type: object
            - type: 'null'
          description: >-
            What the worker did, in the shape its mode produces. Proactive:
            `acted`, any `drafts` it composed, and its own `summary`. Reactive:
            `answered`, the `reply` text, the two ways a reply can be withheld —
            `held_by_guardrail` (the platform stopped it) and `no_reply` (the
            worker judged the thread needed none) — and `loop_in`: the part of
            the ask handed to a person while the reply goes out (`note` for
            them, a follow-up `draft` they finish, and the guardrail's `flag` on
            it), null when nothing was left for a person. A `loop_in` is a
            hand-off as much as `deferred` is. Results recorded before loop-ins
            were (16 Nov 2026) have no `loop_in` key: there, its absence does
            not mean nobody was looped in.
          title: Output
        passed:
          anyOf:
            - type: boolean
            - type: 'null'
          description: null means nobody has scored this one yet.
          title: Passed
        reason:
          anyOf:
            - type: string
            - type: 'null'
          title: Reason
        scores:
          anyOf:
            - additionalProperties: true
              type: object
            - type: 'null'
          title: Scores
        tool_calls:
          anyOf:
            - items:
                additionalProperties: true
                type: object
              type: array
            - type: 'null'
          description: >-
            What it read to get there — the evidence a verdict about grounding
            has to be checked against.
          title: Tool Calls
        trace_id:
          anyOf:
            - type: string
            - type: 'null'
          title: Trace Id
        turns:
          anyOf:
            - type: integer
            - type: 'null'
          title: Turns
      required:
        - id
        - case_id
      title: Result
      type: object
  securitySchemes:
    HTTPBearer:
      scheme: bearer
      type: http
      description: >-
        An API key, sent as `Authorization: Bearer stfy_live_…`. See
        [Authentication](/rest-api/authentication) for how to get one and which
        scopes it needs.

````

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