Jobs & image delivery

Poll job status, follow progress events, cancel work, and download chart images.

Job status

GET/v1/analysis/runs/{id}

Jobs move from queued to running, then completed, failed, cancelled or interrupted. A disconnected caller does not cancel the job. Prefer: wait=5 waits briefly for a result; it is not a model execution deadline.

Poll, then download the chart

curl "$AGENT_CHARTING_URL/v1/analysis/runs/$RUN_ID" \
  -H "Authorization: Bearer $AGENT_CHARTING_API_KEY"

# Use the image.url from the completed response
curl "$AGENT_CHARTING_URL/v1/artifacts/$IMAGE_ID" \
  -H "Authorization: Bearer $AGENT_CHARTING_API_KEY" \
  --output chart.png

Progress and cancellation

GET/v1/analysis/runs/{id}/events

Use Server-Sent Events for persisted progress and terminal states. Reconnect with Last-Event-ID. Progress summaries do not expose private internal reasoning.

Keep one progress stream per job and close it after a terminal state. By default, the service allows eight streams per workspace and 64 per process. A slow or disconnected stream can reconnect from its last event; the job keeps running independently.

POST/v1/analysis/runs/{id}/cancel

Cancel explicitly with an authenticated POST. Render metadata is available at GET /v1/charts/renders/{id}.

Retention and restart behavior

Jobs and image artifacts expire after seven days by default. Download and store images you need longer. Queued jobs resume after restart; in-flight jobs become interrupted and are not silently replayed, because the provider may already have consumed inference.