> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getmillwork.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Output-check REST reference

> Find the generated REST operations for registering, reading, testing, updating, and retiring an output check.

## Register and test a check

Use these REST operations to manage an **output check** (a `verifier` in the API).
This list is generated from the [OpenAPI contract](/openapi/solverapi.openapi.json),
which owns the exact request and response fields. For the customer task path,
follow [Connect an output check](/guides/connect-an-output-check). For the
endpoint request and response shape, read the
[verifier-dock contract](/contracts/verifier-dock/v1.json).

| What you can do       | Method and path                             | Operation ID                         |
| --------------------- | ------------------------------------------- | ------------------------------------ |
| List output checks    | `GET /v1/verifiers`                         | `getVerifiers`                       |
| Register output check | `POST /v1/verifiers`                        | `postVerifiers`                      |
| Get output check      | `GET /v1/verifiers/{verifierId}`            | `getVerifiersByVerifierId`           |
| Update output check   | `PATCH /v1/verifiers/{verifierId}`          | `patchVerifiersByVerifierId`         |
| Retire output check   | `DELETE /v1/verifiers/{verifierId}`         | `deleteVerifiersByVerifierId`        |
| Read connection state | `GET /v1/verifiers/{verifierId}/connection` | `getVerifiersByVerifierIdConnection` |
| Test output check     | `POST /v1/verifiers/{verifierId}/test`      | `postVerifiersByVerifierIdTest`      |

## Use a registered check on a run

Pass the registered `verifier_id` in the body of `POST /v1/executions`
alongside a live task, policy, and saved model. The
[live-run procedure](/guides/connect-an-output-check#use-the-check-on-a-live-run)
explains approval, cost, and receipt inspection. An Echo test run cannot use
an output check.

A protected connection uses private key entry. The generated specification
covers the public operations listed above; follow the
[protected connection steps](/guides/connect-an-output-check#connect-a-protected-endpoint)
for the supported key-entry path. Never send the endpoint key in a REST
registration body.