Skip to main content
GET
Get the pre-run disclosure for a suite launch plan

Authorizations

Authorization
string
header
required

MCPJam API key (sk_…). Create one at Settings → API keys. Guest sessions cannot use the API, and API keys cannot manage other API keys.

Path Parameters

projectId
string
required

ID of the hosted project that contains the server.

suiteId
string
required

Eval suite ID, as returned by POST /eval-runs.

Query Parameters

caseIds
string

Comma-separated test case IDs to narrow the disclosure to, instead of the whole suite.

environmentId
string

One attached environment to disclose for. Mutually exclusive with environmentIds and host.

environmentIds
string

Comma-separated attached environment IDs to disclose for, mirroring a multi-target launch. Mutually exclusive with environmentId and host.

host
string

One attached host to disclose for, mirroring a host-targeted launch — the engine and sandbox facts come from that host's own config. Mutually exclusive with environmentId/environmentIds: a launch plan resolves on exactly one axis.

Response

The pre-run disclosure.

What happens to a run's content: computed once by the backend and projected identically by the pre-run dialog, the CLI, MCP tools, and the eval.run.launched audit row. execution is present ONLY when a launch plan resolved; executionAbsence exactly when it is absent, naming WHICH of two reasons (ingested-run — MCPJam did not execute this; plan-unresolved — a run that WILL execute and WILL call models, just not derivable yet). analysis is ALWAYS present, even without execution: stored evidence still reaches the judges.

contractVersion
integer
required
computedAt
integer
required

Epoch ms. Excluded from digest, so identical facts digest identically regardless of when they were computed.

digest
string
required

SHA-256 hex over the canonical JSON of the facts (excluding digest/computedAt and each managed rail's observedAt).

analysis
object[]
required
capture
object
required

Capture level, reporting mode, and redaction facts (fixed for this contract version).

retention
object
required

Plan retention policy, whether it is actually enforced, and what that means today (kept-indefinitely vs swept-after-policy-days).

region
object
required

{ stated: false, reason } unless a BYOK base URL carries a derivable region token.

subprocessors
object[]
required
execution
object

Present exactly when a launch plan resolved.

executionAbsence
object

Present exactly when execution is absent.