Skip to main content
GET
The rich, single-call view of a benchmark run. Unlike status (a lightweight progress poll), this returns the aggregated metric as a percentage plus a per-task breakdown with traces. It works mid-run (partial, reflecting progress) and after completion.

Authentication

All requests require a BLACKBOX API key as a Bearer token. A run is only readable by the user that created it. See Authentication.

Headers

string
required
API Key of the form Bearer <api_key>.

Path Parameters

string
required
The id returned by Run Benchmarks.

Response

number
The headline score — resolved / total × 100 (2 decimal places). Prefers the recorded final rate; falls back to live counters mid-run.
number | null
Fraction 0..1 recorded on completion (null until then).
string
What the percentage measures — e.g. accuracy (QA) or resolved_rate (SWE).
string
The runtime that actually ran — "claude", "codex", or "grok".
object
{ resolved, total, completed, failed } counters.
object
Per-status tally: { resolved, unresolved, errored, pending, running }.
object
Latency rollup: { totalDurationMs, avgTaskMs, slowestTaskMs, fastestTaskMs } — your “where did it lag” signal.
array
One object per instance, with the trace fields:
array
The failed/errored tasks only, slowest first — each with instanceId, status, durationMs, error, and grade. The “what did it miss / where did it lag” view.
object
Inline log for tracking, so you can follow a run without a second call:

What you can answer by id

Benchmark Logs & Status

Poll status and stream the full logs (live, then replayed from the DB).