HTTP API v1

The HTTP API v1 exposes Autonomy's QA control plane to scripts, CI jobs, and services. It covers Test Cases, Test Plans, Runs, Environments, External Evidence, and Notes.

Set the base URL to your Convex site URL: the value of NEXT_PUBLIC_CONVEX_SITE_URL, such as https://your-deployment.convex.site. Do not use the .convex.cloud URL.

Every catalog operation uses the same route shape and a JSON object body:

POST <NEXT_PUBLIC_CONVEX_SITE_URL>/api/v1/<resource>.<verb>
Content-Type: application/json

For example, test_case.create is POST /api/v1/test_case.create and run.get is POST /api/v1/run.get. Responses are JSON.

The machine-readable OpenAPI 3.1 document is served by every deployment at GET /api/openapi.json. On a dedicated deployment, use GET <NEXT_PUBLIC_CONVEX_SITE_URL>/api/openapi.json instead.

HTTP API and MCP

HTTP and MCP are generated from the same operation catalog and therefore use the same arguments, return values, scopes, confirmation rules, and errors. MCP exposes 15 operations. The three Note operations are HTTP-only, so the HTTP API contains all 18 operations.

Use MCP when an AI assistant should operate Autonomy through its tool protocol. Use this HTTP API for scripts, CI pipelines, or systems that need direct JSON requests.

Start here

1. Authenticate each request.
2. Choose a route from the operation catalog.
3. For asynchronous Runs, follow the Run and External Evidence workflow.
4. Handle the closed set of structured errors.