evals

Get Probe Context

Side-context for the probe edit page: recent runs + suite membership.

Powers the "History & membership" section at the bottom of ProbeForm:

  • recent_runs: last 10 runs of this probe (reverse-chrono), each with its single eval_run_results row's rubric_pass so the UI can render pass/fail dots without a second roundtrip. Run rows that haven't completed (no result yet) report rubric_pass: null and the UI shows them as in-flight.
  • pass_rate: {passed, total, pct} computed over the same set so the header can show "7/10 passing (70%)" without the UI doing math.
  • suites: every eval_suite this probe is currently in, either via explicit_probe_ids OR via tag_query overlap with the probe's tags.

Single endpoint over two reasons: one network round-trip from the edit page, and the two slices conceptually answer the same question — "where does this probe live in the broader testing fabric?"

get/v1/admin/eval/probes/{probe_id}/context

Path parameters

probe_idstring required

Response

Successful Response

{"stackTrail":"paths:/v1/admin/eval/probes/{probe_id}/context:get:responses:200:content:application/json:schema","oasType":"schema","type":"unknown"}

Changes

No recorded changes to this endpoint across all 1 revision of this API.