Skip to main content
PATCH
/
evaluations
/
trace-scores
/
{score_id}
Update Trace Score
curl --request PATCH \
  --url https://api.pandaprobe.com/evaluations/trace-scores/{score_id} \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "value": "<string>",
  "reason": "<string>",
  "metadata": {}
}
'
{
  "id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "trace_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "name": "<string>",
  "value": "<string>",
  "created_at": "<string>",
  "project_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "eval_run_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "author_user_id": "<string>",
  "reason": "<string>",
  "environment": "<string>",
  "config_id": "<string>",
  "metadata": {},
  "updated_at": "<string>"
}

Documentation Index

Fetch the complete documentation index at: https://docs.pandaprobe.com/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

​
score_id
string<uuid>
required

Body

application/json

Editable fields for a trace score.

All fields are optional -- only provided fields are updated. status is set to SUCCESS automatically on save, and source is changed to ANNOTATION to indicate human edit. updated_at is also set automatically.

​
value
string | null

New score value (e.g. '0.9' for NUMERIC, 'true' for BOOLEAN).

​
reason
string | null

Updated reason or annotation note.

​
metadata
Metadata · object

Updated metadata object (replaces existing).

Response

Successful Response

Full trace score representation used by both list and detail endpoints.

​
id
string<uuid>
required
​
trace_id
string<uuid>
required
​
name
string
required
​
value
string | null
required
​
status
enum<string>
required

Outcome of a trace score evaluation attempt.

Available options:
SUCCESS,
FAILED,
PENDING
​
source
enum<string>
required

Who produced the score judgment (not how it arrived).

AUTOMATED -- the eval system's LLM judge produced this score ANNOTATION -- a human assigned this score manually PROGRAMMATIC -- external code submitted this score via API/SDK

Available options:
AUTOMATED,
ANNOTATION,
PROGRAMMATIC
​
created_at
string
required
​
project_id
string<uuid>
required
​
data_type
enum<string>
required

Data type for a trace score value.

Available options:
NUMERIC,
BOOLEAN,
CATEGORICAL
​
eval_run_id
string<uuid> | null
required
​
author_user_id
string | null
required
​
reason
string | null
required
​
environment
string | null
required
​
config_id
string | null
required
​
metadata
Metadata · object
required
​
updated_at
string
required