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

# Validate

Validate a config schema against the same server rules as [`miru release create`](/references/cli/release-create), without creating anything.

### API key scopes

If validating from a [CI pipeline](/developers/ci/overview), the following API key scope is required:

* `config_schemas:read`

### Usage

<Tabs>
  <Tab title="Single File Schema">
    ```bash theme={null}
    miru schema validate ./path/to/schema.json
    ```
  </Tab>

  <Tab title="Multi-File Schema">
    <CodeGroup>
      ```bash Files theme={null}
      miru schema validate first.cue second.cue
      ```

      ```bash Glob theme={null}
      miru schema validate ./motion-control/*.cue
      ```
    </CodeGroup>
  </Tab>
</Tabs>

**Arguments**

<ParamField path="file" type="string" required>
  One or more schema files.

  The files must form exactly one schema. Several files are one schema when they belong to one [CUE package](/cfg-mgmt/primitives/schemas/languages/cue). Schemas must be annotated the same way they are for a [release](/cfg-mgmt/primitives/schemas/overview#schema-annotations).

  Examples: `./path/to/schema.json`, `first.cue second.cue`
</ParamField>

### Examples

```bash theme={null}
$ miru schema validate ./path/to/schema.json

✓ Schema Valid
```