Start release check
Start a release check: an orchestrated pre-release report that runs your regression suite and/or an autonomous exploratory change review, then compiles the results into a single report.
Request at least one of a regression suite (regression) or an exploratory
change review (prUrl or changes). All testing and analysis runs on
QA.tech — it does not consume the caller’s tokens or credits.
Returns 202 immediately. Poll get_release_check until status is
completed (or failed) to read the compiled report.
Body
Request body for starting a release check.
The calling agent describes the release and its intended changes; QA.tech runs an autonomous launch-review agent that tests the current state of the app against an end-user launch checklist, verifies the intended changes, and synthesizes an informational launch-readiness report (Lighthouse-style: it scores the app and highlights what needs attention, it does not block a release). All testing and analysis runs on QA.tech and does not consume the caller's tokens.
Provide at least one of changes, regression, or prUrl so the agent has
something concrete to review.
Human-readable name for this release, e.g. 'v2.3.0' or 'June checkout revamp'.
Short description of what this release contains.
Free-text focus areas, risk areas, or instructions for the review.
The intended changes in this release (user prompts, PR descriptions, tickets). The review agent verifies each one behaves as described.
Regression baseline to run as part of the check.
Optional pull request URL to enrich the review with diffs and deployment info. Requires vcsProviderId.
VCS provider for prUrl.
github, gitlab Per-application environment overrides identifying the build/URL under review.
Target a specific project by its prefixed short ID (proj-slug_shortId or proj_shortId), as returned by the projects API. Required for organization-scoped API keys; project-scoped keys may only pass their own project's short ID.
^proj(-.+_.+|_.+)$Response
The request has been accepted for processing, but processing has not yet completed.
Lightweight response returned immediately after starting a release check.
^rc(-.+_.+|_.+)$Dashboard URL for the release check's launch-readiness report.
Lifecycle status of a release check.
pending, running, completed, failed Short ID of the launch-review conversation driving this check.
^chat(-.+_.+|_.+)$