What the packet contains
GET /api/v1/runs/{run_id}/defensibility-packet returns packet version 1:
What is withheld, and what is not
- Withheld: the body of every model call. The call is attested by its stage so the chain is complete, but the prompt and completion are Nexio’s engine implementation and are not part of the packet.
- Not redacted: everything else. The redaction step in the packet is not active today, so
fields_redactedis always0and external-call evidence, output, provenance, warnings, event attributes and submitter labels appear as recorded. They can contain personal or restricted data. Store and send the packet with the same care as the run’s input. The data use sheet labels event attributes, structured event errors and external-call evidence as “Export redacted”; that label names the intended export, and the redaction step behind it does nothing today, so this paragraph describes the packet as it is now.
Get a packet
vendor-intake engine from Declared-contract engines. The run made no model or external calls and recorded no provenance map. The timeline is cut to the two stage events the declared-contract runner records, ENRICH and COMPOSE.
Errors
Credentials and retention
The packet accepts the organization key, or a scoped key that holdsruns:defensibility:read (a capability separate from runs:read) and is bound to the run’s engine. The run must be in the key’s environment.
A daily job deletes runs created more than 90 days ago, together with their packet evidence. The exception is a run Nexio flags to be kept indefinitely; there is no API or portal control for that flag, so ask Nexio. Export the packet within the 90 days if you need it later.
Run trace (portal)
The portal shows the same evidence, and more, on the run’s Trace tab: the run’s events with their timings, token counts and cost, and a viewer for recorded request and response bodies. The trace needs the portal permissionruns:trace, which comes with a team member’s role. There is no public API route for the trace and it cannot be granted to an API key. Use the defensibility packet for anything you need outside the portal.
Supersession
Supersession attaches a corrected result to a run that was already delivered, while keeping the original. A superseded run sends arun.superseded webhook only when the engine’s configuration sets notify_on_supersede: true (which configuration version Nexio checks is in Configuration) and an active webhook endpoint in the run’s environment subscribes to run.superseded.
Built, not yet enabled as a customer feature: there is no public route and no portal control to supersede or to read a supersession.
Runs
What each run status carries.
Get run defensibility packet
Endpoint reference.