Get Result
Retrieve a test result by ID
Authorizations
API Key Authentication. It should be included in the header of each request.
Path Parameters
A unique integer value identifying this result.
Response
Name of the result
Example: "Test Result 1"
255Name of the agent associated with this result
The agent version (history record) this result ran against, or null.
Current status of the result
running- Runningcompleted- Completedfailed- Failedpending- Pendingin_progress- In Progressevaluating- Evaluatingin_queue- In Queuetimeout- Timeoutcancelled- Cancelledscaling_up- Scaling Up
running, completed, failed, pending, in_progress, evaluating, in_queue, timeout, cancelled, scaling_up Number of runs that fully met their expected outcomes with a score of 100
Total number of runs that had expected outcomes defined
Success rate of the test runs
Whether this test was run in text mode instead of voice mode
Example: true or false
Whether this result was created by a scheduled cronjob
Run objects keyed by run ID string (e.g. {"12345": {...}}). The list endpoint returns runs as an array of summaries instead.
Overall evaluation of the test runs Example:
Total duration of the test runs for this result
Example: 22:30
Total number of test runs associated with this result
Example: 10
Number of test runs that have completed successfully
Example: 10
Number of test runs that were marked as successful
Example: 10
Number of test runs that failed or encountered errors
Example: 10
List of run IDs that got connected successfully (have transcript data). Returns empty list if no connected runs.
List of run IDs that failed infrastructure issues metric (score=0). Returns null if metric not found, empty list if metric exists but no failures.
List of run IDs that failed expected outcome metric (score=0). Returns null if metric not found, empty list if metric exists but no failures.
List of run IDs that completed successfully. Returns empty list if no successful runs.
List of scenario names used in the test runs for this result Example: ```
List of critical categories for this result Example:
Failed reasons of the test runs Example:
LLM-generated narrative summary of the result, structured for the Results-page UI. Example:
Generation state of the async AI summary, derived so the UI can show a reliable state instead of guessing from an empty ai_summary. completed = summary populated; skipped_no_failures = no failed runs, nothing to summarize; pending = there are failed runs but the summary isn't ready yet (still generating).
LLM-suggested next steps to fix the issues found in this result, ordered by impact. Example:
Per-rubric-rule performance breakdown. One entry per rule in the project's rubric_config: metric name, aggregated value across the result's runs, and whether that aggregate meets the rule's conditions.
Run Execution Type
Snapshot of the override-relevant request payload (personality_ids, frequency, concurrency_limit, connection-specific overrides, etc.).
Timestamp when this test result was created
Example: 2021-01-01 00:00:00
Timestamp when this test result was last updated
Example: 2021-01-01 00:00:00