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

# Live API schema

> Retrieve the authenticated reference generated by your deployment.

## Retrieve the schema

Alignr generates its OpenAPI reference from the running application. The developer reference is authenticated; it is not an anonymous public schema.

```bash theme={null}
curl --fail-with-body \
  'https://api.alignr.io/api/v1/developer/openapi.json' \
  --header "Authorization: Bearer $ALIGNR_API_KEY" \
  --output alignr-openapi.json
```

The schema includes `x-ledgr-permission` for route-level permissions and `x-ledgr-destructive` for operations marked as potentially destructive. A null permission extension does not mean an operation is public: authentication and operation-specific checks still apply.

## Inspect authentication and MCP

```bash theme={null}
curl --fail-with-body \
  'https://api.alignr.io/api/v1/developer/auth' \
  --header "Authorization: Bearer $ALIGNR_API_KEY"

curl --fail-with-body \
  'https://api.alignr.io/api/v1/developer/mcp' \
  --header "Authorization: Bearer $ALIGNR_API_KEY"
```

The MCP reference reports whether the server is enabled and lists tools, arguments and scopes. Use it to confirm the capabilities of the deployment you are connecting to.

## API explorer

Open [Alignr’s developer page](https://app.alignr.io/developer) while signed in for the in-product API reference. Never embed a private key in a documentation site to make an authenticated schema publicly fetchable.