Skip to main content
GET
Get Run Defensibility Packet
This route exposes a broader restricted-data surface than ordinary polling. A scoped key must have runs:defensibility:read, must be bound to the run’s engine, and must belong to the run’s canonical named environment. The default runtime capability set does not include packet access.

Contents

The version 1 packet can contain:
  • run identity, submitter reference, engine/config lineage, timestamps, status, warnings, structured errors, and cost rollup
  • the customer-visible output and per-element provenance map
  • redacted external-call request and response evidence
  • the run event timeline and its lineage fields
  • aggregate model call, token, cache, and cost summaries
  • a redaction count and explicit provenance coverage marker
Raw model-call prompt and completion blobs are withheld. Each model call remains attested by pipeline stage with a null body in the customer-facing packet. External-call evidence, output, provenance, warnings, event attributes, and submitter labels may contain restricted data. Store and transmit the packet accordingly.

Errors

Retention

The packet is assembled from run-bound evidence. Non-flagged runs and their packet evidence use the platform’s 90-day default retention window and purge together. Authorized internal preservation flags can retain a run longer.

Authorizations

Authorization
string
header
required

Send the credential as Authorization: Bearer <key>.

Scoped partner credentials use the exclusive nxsk_v1_... namespace. Each scoped key is bound at issuance to one organization, one canonical named environment, an explicit engine set, and a least-privilege capability set. A malformed, unknown, rotated, or revoked nxsk_ key fails closed and is never retried as a legacy key.

Capabilities used by this API are runs:write, runs:read, engines:read, catalog:read, webhooks:manage, runs:defensibility:read, runs:test, conversations:use, and conversations:export. Operation descriptions name the required capability. Grandfathered nx_live_... and nx_test_... keys retain their existing broad access during the compatibility window.

Path Parameters

run_id
string<uuid>
required

Response

The customer-facing defensibility packet.

version
string
required
Example:

"1"

run
object
required

Run identity and lineage (id, engine, version, status, timestamps).

provenance_coverage
enum<string>
required

none for runs predating provenance capture; an absent map must not read as sourced-clean.

Available options:
present,
none
model_calls
object[]
required

Stage attestation that a model call ran, without the prompt or completion body.

external_calls
object[]
required

Enrichment calls that fed the run, with their payloads.

events
object[]
required

The run event timeline.

redaction
object
required
output
object

The customer-visible output of the run.

provenance
object

Per-element provenance map, present when the run recorded one.

llm_summary
object

Aggregate model cost and token usage for the run.