Resume a stopped readiness run
Runs again a run that stopped on the server before it finished, which the run detail reports as resumable: true. The server is graded with the caller’s credentials, so only the person who started the run can resume it. The run keeps the inputs it started with, and the request has no body. Poll the run detail as after a start. When the saved server is gone, no longer authorizes the caller, or now has a different URL, the run fails with that reason.
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
Response
The run was resumed and is executing.
The 202 receipt. Poll the run detail; do not re-POST.
The run's status when the start returned. pending for a fresh start; for a deduped start, whatever the existing run is already at — which may be completed, because a replayed idempotency key can name a run that finished long ago.
pending, running, completed, failed, cancelled 
