Skip to main content

​
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, which owns the exact request and response fields. For the customer task path, follow Connect an output check. For the endpoint request and response shape, read the verifier-dock contract.

​
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 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 for the supported key-entry path. Never send the endpoint key in a REST registration body.