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

# Validate API

> Request a validation, inspect a run, and read results through the Remyx API.

Use the API to request and inspect validations for connected repositories.

The API requires the documented authentication scheme and the appropriate `evals:read` or `evals:write` scope.

## Endpoints

The endpoint definitions below describe accepted requests, status responses, run fields, artifacts, and errors.

For a first run in GitHub, see [Validate](https://docs.remyx.ai/platform/agents/validate.md). For manual configuration, see [Validation spec](https://docs.remyx.ai/platform/agents/validate-spec.md).

### Runs

[Request a validation](https://docs.remyx.ai/api-reference/validate-request.md) · [Get a run](https://docs.remyx.ai/api-reference/validate-get-run.md) · [List results and artifacts](https://docs.remyx.ai/api-reference/validate-results.md)

### Model

```
GET    /api/v1.0/validate/model?repo=owner/name   # which provider would design a validation for this repo, and where that choice came from
GET    /api/v1.0/validate/settings?repo=          # the account's Validate settings; with repo, that repo's row and the effective source
PUT    /api/v1.0/validate/settings                # {repo?, installation_id?, model_provider?, model?, settings?}; omit both scopes for the account default; null clears a field
DELETE /api/v1.0/validate/settings?repo=          # remove a repo override, or the account default without repo
```

`PUT` returns `400 {code: "provider_not_connected", available_providers}` when the provider is not connected on the account, and `403 {code: "not_owner"}` for an installation setting from someone other than the installation's owner.

### Specs

```
GET  /api/v1.0/validate/specs          # runs grouped by spec_hash, each with the reconstructed .remyx/validation.yaml
POST /api/v1.0/validate/specs/push     # commit an edited spec back as remyx-ai[bot], always on a new branch with a PR
POST /api/v1.0/validate/specs/lint     # check a draft spec with the same parser a run uses; returns what the engine understood
```

### Summary, signals, entitlement

```
GET  /api/v1.0/validate/summary?repo=        # verdict, calibration, and spend rollup behind the Studio Validations view
POST /api/v1.0/validate/signals              # production evidence for a validated change, scored against its offline prediction
GET  /api/v1.0/validate/entitlement?repo=    # would a validation be admitted now, on what basis, how many are left; the refusal line and checkout link when not
```

`/validate/grants` and `/validate/proposals/<id>/{context, report}` and `/validate/runs/<id>/{fix-context, fix-report}` are service-only: they serve the proposer and fix jobs and the Remyx team.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.