Get an iteration's step results
One row per authored test step, in order, with status (ok/fail/skipped/pending), a reason, and any evidence (screenshots, replay-video offset, widget tool calls). The fastest way to see which step failed and why. Unlike /trace, a missing trace is not a 404 — step verdicts still return, just without evidence.
Authorizations
MCPJam API key (sk_…). Create one at Settings → API keys. Guest sessions cannot use the API, and API keys cannot manage other API keys.
Path Parameters
ID of the hosted project that contains the server.
Eval run ID, as returned by POST /eval-runs.
Iteration ID, as returned by the run's iterations list.
Response
The ordered step results as a page envelope.
Authored steps in order with their verdict.
Whether the evidence read behind these verdicts completed. resolved means it did (a step may still have produced no evidence); unavailable means it failed and the verdicts are all that could be served. Absent on a deployment that predates the marker.
resolved, unavailable 
