API

Events and reviews

A completed area run exposes the exact matching events retained in its manifest. Reviews attach an operator verdict and note to that same record.

List run events#

request

curl "$PRAXIS_API/v1/runs/{run_id}/events" \
  -H "Authorization: Bearer $PRAXIS_API_KEY"

Each event includes its track ID, class label, event kind, timestamp, source frame, confidence, and evidence-image reference when available. The key needs theevents:read scope and must own the run.

Review one event#

request

curl -X POST "$PRAXIS_API/v1/runs/{run_id}/events/1/reviews" \
  -H "Authorization: Bearer $PRAXIS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"verdict":"confirmed","note":"Clear crossing"}'

event_numberintegerrequired

One-based event position in the retained result.

verdictstringrequired

confirmed, not_relevant, or unsure.

notestring

A short operator note retained with the review.

Saving a review updates the run manifest and rebuilds the Evidence Pack. A read-only share can inspect events and signed artifacts but cannot submit a review.

Prepared event shape#

The control below still uses the checked-in boulevard record so the response shape can be inspected without creating a compute run. It is not a request to the hosted API.

STATIC/challenge/zone.json