Start a Muse connector readiness run
Grades the saved server against Meta’s Muse connector guidelines and returns 202 with a run id. Free: Muse readiness has no AI observations, so the body has no field that can spend, and no submission mode, which belongs to the OpenAI plugin directory. The submission-ready verdict stays incomplete on a hosted run, because Muse’s submission requirements are declared by the submitter and only the CLI accepts a submission profile. Meta reviews every submission by hand, so ready is a preflight, not a prediction of approval.
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.
ID of the server inside the project.
Body
Deduplicates a retried POST. More load-bearing here than usual: a readiness run dials a third party's server, and a retried start that created a second run would do that twice.
200Response
The run was accepted and is executing.
The 202 receipt. Poll the run detail; do not re-POST.
claude, openai, muse 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 This request replayed an existing run rather than starting one.

