> For the complete documentation index, see [llms.txt](https://docs.aviator.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aviator.co/verify/reference/configuration-reference.md).

# Configuration reference

This page is the umbrella reference for Verify configuration. Per-concept references live on their own pages and are linked from here.

### Per-repo: `verify.yaml`

The root of all per-repo configuration. Edit it in the Aviator dashboard under **Verify → Settings → Verify** with the repository selected — it is not a file you commit to the repo. Each save is versioned, and earlier versions can be restored from the editor's history.

#### Top-level keys

| Key              | Type | Default | Description                                                                             |
| ---------------- | ---- | ------- | --------------------------------------------------------------------------------------- |
| `verify`         | map  | none    | Root key. All Verify configuration nests under it.                                      |
| `verify.preview` | list | none    | One or more preview definitions. See [Preview YAML](/verify/reference/preview-yaml.md). |

Example:

```yaml
verify:
  preview:
    - name: default
      image: api-preview
      port: 8000
      setup: .aviator/scripts/preview-setup.sh
      secrets:
        - DB_PASSWORD
        - STRIPE_KEY
```

Unknown keys are rejected: saving fails with a validation error rather than silently ignoring them. A common mistake is starting the document at `preview:` — it must nest under `verify:`.

### Per-repo: preview block

Detailed in its own reference page:

→ [Preview YAML reference](/verify/reference/preview-yaml.md)

### Account-level settings

Configure in **Verify → Settings**. These apply across the account rather than per repository.

#### Sandbox

Set under **Verify → Settings → Sandbox**.

| Setting                       | Type     | Default         | Description                                                                   |
| ----------------------------- | -------- | --------------- | ----------------------------------------------------------------------------- |
| **Sandbox Timeout (minutes)** | integer  | `60`            | How long a sandbox stays active. Accepts 1–240.                               |
| **Sandbox Image**             | template | Aviator default | The image sandboxes boot from. Custom images are registered on the same page. |

When the timeout expires, the sandbox is torn down and the preview link stops resolving. See [Managing previews](/verify/how-to-guides/managing-previews.md).

### Invariants

Invariants have their own configuration surface in **Settings → Invariants**. Field-level reference and writing guidance are on the concept and tutorial pages:

* [Concepts: Invariants](/verify/concepts/invariants.md) — sources, categories, selection
* [Setting up org invariants](/verify/setting-up-org-invariants.md) — step-by-step setup

### MCP

The MCP install and tool surface are on a dedicated reference page:

→ [MCP tools](/verify/reference/mcp-tools.md)

### See also

* [Preview YAML reference](/verify/reference/preview-yaml.md)
* [MCP tools](/verify/reference/mcp-tools.md)
* [Spec format](/verify/reference/spec-format.md)
* [Concepts: Invariants](/verify/concepts/invariants.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.aviator.co/verify/reference/configuration-reference.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.