Scripts and CI

Start Mo after your deployment is ready and export the findings for your script or CI job to review. Use a Momentic API key to authenticate.

Start a session

For coding agents, keep the requested interface. Otherwise, use the hosted Momentic MCP with an existing Connector for private targets, or the qa CLI when a new tunnel is needed. An agent that can’t run commands on the machine that reaches the target asks you to start the tunnel there, then uses hosted tools with that Connector, or the CLI if you asked for it or the agent has no hosted tools. A blocked hosted session reports the blocker without switching interfaces. For scripts and continuous integration (CI) jobs, use the HTTP API below and keep MOMENTIC_API_KEY in your CI secret store. When a tunnel is needed, start it with the CLI, save the session ID and URL, then use qa wait and qa report to collect findings. Start a web session over HTTP with a Momentic API key. This request returns sessionId and webUrl:

curl --fail-with-body https://api.momentic.ai/v1/mo/sessions \
  -H "Authorization: Bearer $MOMENTIC_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"message":"Test checkout on https://preview.example.com. Do not submit payment or place an order."}'

Start a PR session

Both start endpoints accept an optional top-level slackChannel, such as "C0123ABC" or "#checkout-qa", to deliver reports and requests for input to that channel. Connect the Momentic Slack app and invite it to the channel first. An unknown channel or missing bot membership rejects the start before a session is created. With the CLI, pass --slack-channel '#checkout-qa' to qa start. Send the provider and PR reference to /v1/mo/pr-sessions. GitHub is the supported PR provider. previewUrl is optional; supply it when your script or coding agent knows which deployment to test:

curl --fail-with-body https://api.momentic.ai/v1/mo/pr-sessions \
  -H "Authorization: Bearer $MOMENTIC_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "message": "Test the PR changes. Do not submit payment.",
    "pullRequest": {
      "provider": "github",
      "kind": "number",
      "owner": "acme",
      "repo": "shop",
      "number": 412
    },
    "previewUrl": "https://preview.example.com"
  }'

A PR start requires a preview URL, supplied as previewUrl or discovered for the current PR commit. A saved environment does not replace it. If discovery finds no usable preview, supply previewUrl before starting.

Wait and fetch the report

For either start route, keep the returned sessionId. Poll GET /v1/mo/sessions/:sessionId/status every 10 seconds with the same API key:

SESSION_ID="<session-id>"
curl --fail-with-body "https://api.momentic.ai/v1/mo/sessions/$SESSION_ID/status" \
  -H "Authorization: Bearer $MOMENTIC_API_KEY"

Read canonicalDisplayState when present, otherwise displayState. Keep polling while that state is running, waiting_on_agents, or checking. For needs_you, open webUrl, answer the pending questions, then resume polling. On a failed request, stop and resolve the error rather than treating missing status as completion. When Mo is ready, fetch GET /v1/mo/sessions/:sessionId/report:

curl --fail-with-body "https://api.momentic.ai/v1/mo/sessions/$SESSION_ID/report" \
  -H "Authorization: Bearer $MOMENTIC_API_KEY" \
  -o mo-report.json

For other idle or stopped states, inspect reason and nextAction; the report may be partial. Review the report’s findings, verdicts, and coverage gaps before deciding whether the app met your criteria. A settled session is not proof that the app passed. For recurring testing, configure a Mo schedule with a prompt and environment. Each scheduled run starts a new session. Copy its session ID from the schedule’s past-run link or session URL, then use the HTTP recipe above. See Mo integrations for other connections.

Get started

Essential guidelines

Set up Mo

Integrations

Working with Mo

Start a session

Start a PR session

Wait and fetch the report