Ingest a step's named results (ADR-0040/0042): the trusted per-Pod egress sidecar POSTs `{ name: value, … }` here, authenticated by a fence-scoped token, and the control plane persists them to `step_runs.results`. The untrusted step never calls this — only the sidecar holds the token.
POST
/v1/runs/{id}/steps/{step}/results
const url = 'https://example.com/v1/runs/example/steps/example/results';const options = {method: 'POST'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://example.com/v1/runs/example/steps/example/results404 when no token secret is configured; 401 on a bad/missing token; 404 for an unknown step; 413 for an over-large body. The write is idempotent on the fence (a re-drive overwrites deterministically, ADR-0021).
Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”id
required
string
Run id
step
required
string
Step id
Responses
Section titled “Responses”Results recorded
Bad or missing token
No such step, or results ingest disabled