Waive a run gate
Override a FAILING run’s release gate until an expiry you name. This does NOT make the run pass: the run keeps its result, the waiver is a separate audited record, and every surface that honors it — the GitHub Check Run and the CLI’s eval gate — reports the gate as waived, by whom, why, and until when.
Requires the manage tier; whoever launched the run gets no exception for having launched it. reason is stored UNREDACTED and readable by anyone who can see the suite, for as long as the suite exists.
400 covers five distinct refusals, each with a message written for the caller: the suite belongs to no organization, the reason is blank, the reason exceeds 500 characters, the expiry is not in the future, or the expiry is more than 30 days out. 403 means the caller can see the suite but lacks the manage tier — deliberately not collapsed to 404, which would send a legitimate member hunting for a run sitting in front of them.
Authorizations
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
ID of the hosted project that contains the server.
Eval run ID, as returned by POST /eval-runs.
Body
Response
The waiver was granted.
The result of granting or revoking a waiver. conflict and already_revoked are IDEMPOTENT no-op successes, not failures.
conflict — a waiver was already in force, and waiver is that EXISTING one rather than a second row. already_revoked — this waiver had already been revoked, and waiver reports the original revocation rather than restamping it, so the record of who actually ended it survives a second call.
created, conflict, revoked, already_revoked GitHub Check Runs brought back in line by this write. A published check is a persisted verdict, not a live read, so 0 on a repository with checks connected means the status that gates the merge did not move.
An audited, time-boxed override of an eval run's release gate. A waiver never changes the run's own result — the run keeps its verdict and every surface that honors the waiver says so out loud, which is what makes "no silent waiver" checkable rather than promised.

