Get provenance
Inspect a consistent versioned snapshot of recorded run evidence.
Credential scopes: runs:read
Resource authority: Run submitter or current model owner/co-admin; model-administrator reads are audited. Connector administration and model execution grants alone confer no scientific read access.
Retry: Repeat GET using the same resource identity; each request rechecks current credential and resource authority.
Guards: No mutation or execution authority is granted.
Retain: Run identity; opaque cursor where returned.
Specific failures: 403 insufficient_scope; 404 not_found: missing or unauthorized resource
Next action: Inspect current state; follow exact referenced artifact identities. Worked workflow
A consistent snapshot of recorded acceptance, scientific definition, execution receipts, exact verified input/output versions and direct upstream producers. In-progress runs accumulate evidence. Contains no storage locators, credentials or temporary transfer authorization. The submitter retains historical access after model-grant revocation. Current model owners/co-admins may read with an audit record; removing that administrative membership removes its read authority. Historical storage availability does not govern metadata retrieval.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Run identity readable by its submitter or current model owner/co-admin.
Responses
Section titled “Responses”Version-1 provenance JSON; deterministic while recorded facts are unchanged.
Versioned JSON document; the download endpoint serializes this same document. Stable ordering and the absence of an inspection timestamp make unchanged evidence byte-for-byte reproducible. In-progress runs accumulate more facts.
object
object
Set only after confirmed termination (or cancellation before assignment).
The retained actor may be an connector administrator for queued-only cutover.
Creator cancellation covers pending and running work. Connector context-cutover cancellation is queued-only and retains the actual actor and reason.
Public execution state. Delegated preparation and collection are running.
A request does not confirm termination. Completion can win a cancellation race.
Immutable registered scientific contract, including schemas and examples. Identity labels are provider claims, not independent software attestation.
object
Enumeray’s interpretation of schema restrictions and input/output values. This is independent of the wrapper protocol and JSON Schema dialect.
A named example validated at registration and preserved for discovery.
object
Up to eight optional diagnostics, keyed by [a-z][a-z0-9_-]{0,63}. Paths are confined to the run workspace; diagnostics are independent of results.
object
object
Public projection of the original claim receipt and immutable backend handle. Process sessions, journal IDs and provider-local launch selectors are omitted.
object
Identity claims derived from the retained scientific definition. They do not independently attest the provider’s installed software.
object
Requirements derived from an immutable context and scientific contract. These are execution needs, not observations of backend support.
object
Execution mechanisms, independent of the wrapper’s request/result protocol.
Accepted file dependencies, ordered by declared input name.
Immutable verified file evidence. Availability is deliberately separate: an expired file does not rewrite the exact version used or produced by a run.
object
object
Only sha256 is supported.
Only full_object is supported; multipart checksums are not accepted.
Canonical base64 of the 32-byte SHA-256 digest.
Declared input/output position, independent of the artifact logical name.
Null for user uploads; direct producer identity for model-to-model reuse. Follow the same authorized producer provenance route for further ancestry.
object
object
Verified files included in the committed result, ordered by output name. Empty until finalization. Pending uploads are not execution results.
Immutable verified file evidence. Availability is deliberately separate: an expired file does not rewrite the exact version used or produced by a run.
object
object
Only sha256 is supported.
Only full_object is supported; multipart checksums are not accepted.
Canonical base64 of the 32-byte SHA-256 digest.
Declared input/output position, independent of the artifact logical name.
Null for user uploads; direct producer identity for model-to-model reuse. Follow the same authorized producer provenance route for further ancestry.
object
object
Immutable publication facts and separately attributed connector observation.
object
Model-provider claims retained verbatim, not independent attestation.
object
Creator-private result and file manifest; also visible to the owning connector.
object
object
Closed immutable collection reference used by scientific inputs and results.
object
object
Closed public stored-file reference, never a path or transfer capability.
object
object
Private bounded failure details, never included in diagnostics or tracing.
object
At most 2048 UTF-8 bytes. Only tab and newline control characters allowed.
Original committed acknowledgement, independent of later inspection time.
object
True only after this result and every file pin have committed. It permits removal of provider work files, never deletion of API-retained artifacts. Historical receipts and operator resolutions carry no cleanup authority.
object
Immutable submission intent. Candidate trials retain author/compute authority checks.
Public execution state. Delegated preparation and collection are running.
Headers
Section titled “Headers”No-store
Always present. A fresh server-generated UUID for this request; incoming IDs are ignored. On errors, this equals the response body’s request_id.
Query parameters are not accepted.
The common JSON body for errors returned by the HTTP application.
object
Stable machine-readable error code.
Bounded corrections for authorized scientific-schema failures only. Absent on other failures. The complete validation error body is <=4608 bytes.
object
More violations exist than fit in this response.
At most eight violations, in validator traversal order.
A schema failure without submitted values or arbitrary property names.
object
Fixed guidance; actual bounds and allowed values remain in the publication schema.
JSON Pointer relative to inputs; the empty string denotes its root.
Only ordinary, explicitly declared property names and array indices appear.
Example
/valueThe position stops at a safe ancestor instead of naming the exact field.
Stable categories independent of the validator’s free-form diagnostics.
Safe explanation without internal errors or submitted input values.
Matches the response’s x-request-id header.
Headers
Section titled “Headers”No-store
Always present. A fresh server-generated UUID for this request; incoming IDs are ignored. On errors, this equals the response body’s request_id.
Active user credential required.
The common JSON body for errors returned by the HTTP application.
object
Stable machine-readable error code.
Bounded corrections for authorized scientific-schema failures only. Absent on other failures. The complete validation error body is <=4608 bytes.
object
More violations exist than fit in this response.
At most eight violations, in validator traversal order.
A schema failure without submitted values or arbitrary property names.
object
Fixed guidance; actual bounds and allowed values remain in the publication schema.
JSON Pointer relative to inputs; the empty string denotes its root.
Only ordinary, explicitly declared property names and array indices appear.
Example
/valueThe position stops at a safe ancestor instead of naming the exact field.
Stable categories independent of the validator’s free-form diagnostics.
Safe explanation without internal errors or submitted input values.
Matches the response’s x-request-id header.
Headers
Section titled “Headers”No-store
Always present. A fresh server-generated UUID for this request; incoming IDs are ignored. On errors, this equals the response body’s request_id.
The credential does not permit this operation (insufficient_scope).
The common JSON body for errors returned by the HTTP application.
object
Stable machine-readable error code.
Bounded corrections for authorized scientific-schema failures only. Absent on other failures. The complete validation error body is <=4608 bytes.
object
More violations exist than fit in this response.
At most eight violations, in validator traversal order.
A schema failure without submitted values or arbitrary property names.
object
Fixed guidance; actual bounds and allowed values remain in the publication schema.
JSON Pointer relative to inputs; the empty string denotes its root.
Only ordinary, explicitly declared property names and array indices appear.
Example
/valueThe position stops at a safe ancestor instead of naming the exact field.
Stable categories independent of the validator’s free-form diagnostics.
Safe explanation without internal errors or submitted input values.
Matches the response’s x-request-id header.
Headers
Section titled “Headers”No-store
Always present. A fresh server-generated UUID for this request; incoming IDs are ignored. On errors, this equals the response body’s request_id.
Invalid, unknown or unauthorized run.
The common JSON body for errors returned by the HTTP application.
object
Stable machine-readable error code.
Bounded corrections for authorized scientific-schema failures only. Absent on other failures. The complete validation error body is <=4608 bytes.
object
More violations exist than fit in this response.
At most eight violations, in validator traversal order.
A schema failure without submitted values or arbitrary property names.
object
Fixed guidance; actual bounds and allowed values remain in the publication schema.
JSON Pointer relative to inputs; the empty string denotes its root.
Only ordinary, explicitly declared property names and array indices appear.
Example
/valueThe position stops at a safe ancestor instead of naming the exact field.
Stable categories independent of the validator’s free-form diagnostics.
Safe explanation without internal errors or submitted input values.
Matches the response’s x-request-id header.
Headers
Section titled “Headers”No-store
Always present. A fresh server-generated UUID for this request; incoming IDs are ignored. On errors, this equals the response body’s request_id.
413: the request body exceeds the configured size limit.
The common JSON body for errors returned by the HTTP application.
object
Stable machine-readable error code.
Bounded corrections for authorized scientific-schema failures only. Absent on other failures. The complete validation error body is <=4608 bytes.
object
More violations exist than fit in this response.
At most eight violations, in validator traversal order.
A schema failure without submitted values or arbitrary property names.
object
Fixed guidance; actual bounds and allowed values remain in the publication schema.
JSON Pointer relative to inputs; the empty string denotes its root.
Only ordinary, explicitly declared property names and array indices appear.
Example
/valueThe position stops at a safe ancestor instead of naming the exact field.
Stable categories independent of the validator’s free-form diagnostics.
Safe explanation without internal errors or submitted input values.
Matches the response’s x-request-id header.
Headers
Section titled “Headers”No-store
Always present. A fresh server-generated UUID for this request; incoming IDs are ignored. On errors, this equals the response body’s request_id.
Provenance records unavailable.
The common JSON body for errors returned by the HTTP application.
object
Stable machine-readable error code.
Bounded corrections for authorized scientific-schema failures only. Absent on other failures. The complete validation error body is <=4608 bytes.
object
More violations exist than fit in this response.
At most eight violations, in validator traversal order.
A schema failure without submitted values or arbitrary property names.
object
Fixed guidance; actual bounds and allowed values remain in the publication schema.
JSON Pointer relative to inputs; the empty string denotes its root.
Only ordinary, explicitly declared property names and array indices appear.
Example
/valueThe position stops at a safe ancestor instead of naming the exact field.
Stable categories independent of the validator’s free-form diagnostics.
Safe explanation without internal errors or submitted input values.
Matches the response’s x-request-id header.
Headers
Section titled “Headers”No-store
Always present. A fresh server-generated UUID for this request; incoming IDs are ignored. On errors, this equals the response body’s request_id.
default
Section titled “default”An HTTP request failed; inspect the stable error code and request ID.
The common JSON body for errors returned by the HTTP application.
object
Stable machine-readable error code.
Bounded corrections for authorized scientific-schema failures only. Absent on other failures. The complete validation error body is <=4608 bytes.
object
More violations exist than fit in this response.
At most eight violations, in validator traversal order.
A schema failure without submitted values or arbitrary property names.
object
Fixed guidance; actual bounds and allowed values remain in the publication schema.
JSON Pointer relative to inputs; the empty string denotes its root.
Only ordinary, explicitly declared property names and array indices appear.
Example
/valueThe position stops at a safe ancestor instead of naming the exact field.
Stable categories independent of the validator’s free-form diagnostics.
Safe explanation without internal errors or submitted input values.
Matches the response’s x-request-id header.
Headers
Section titled “Headers”No-store
Always present. A fresh server-generated UUID for this request; incoming IDs are ignored. On errors, this equals the response body’s request_id.
Documentation 205dcb3116ea · public sources 8c70356d340f · built .Download documentation identity.