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

# List guardrail validators and actions

> Returns the static catalog of guardrail validator types and enforcement actions.

Use `validators[].id` as `type` and `actions[].id` as `on_fail` when building entries in `PUT /applications/{applicationId}/guardrails`. Each catalog validator includes an `input` / `output` flag indicating where it may be used.

For `content-safety`, `validators[].config.categories` lists the available safety categories (`id`, `name`, `description`). When configuring an application via PUT, set `config.categories` to an array of selected category **id** strings (for example `["violent-crimes", "hate"]`). At least one category is required.

For `pii`, `validators[].config.entities` lists the available PII entity types (`id`, `name`, `description`, `group`). When configuring via PUT, set `config.entities` to an array of selected entity **id** strings (for example `["EMAIL_ADDRESS", "PHONE_NUMBER"]`). At least one entity is required.



## OpenAPI

````yaml /openapi.json get /guardrails/validators
openapi: 3.0.0
info:
  title: Trusys API
  version: 1.0.0
  description: >-
    Programmatic access to Trusys for integrating AI quality monitoring,
    evaluation, and guardrails into your own systems — without using the Trusys
    UI.


    **Typical integration flow**


    1. `POST /applications` — register your application and get an id.

    2. `PUT /applications/{id}/monitoring` and/or `PUT
    /applications/{id}/guardrails` — configure which metrics, security plugins,
    and guardrails apply.

    3. `POST /applications/{id}/evaluations` — submit prompt/response traces to
    be scored as your application runs.

    4. `GET /applications/{id}/traces`, `GET /applications/{id}/evaluations`,
    and `POST /applications/{id}/widget-data` — pull results, trends, and
    dashboard-equivalent chart data back into your own tools.


    All requests require an `x-api-key` header (see Authentication). All
    timestamps are ISO 8601 UTC. Paginated endpoints default to 20 items per
    page (max 100).
servers:
  - url: https://app.trusys.ai/api/external
security:
  - ApiKeyAuth: []
paths:
  /guardrails/validators:
    get:
      tags:
        - Guardrails
      summary: List guardrail validators and actions
      description: >-
        Returns the static catalog of guardrail validator types and enforcement
        actions.


        Use `validators[].id` as `type` and `actions[].id` as `on_fail` when
        building entries in `PUT /applications/{applicationId}/guardrails`. Each
        catalog validator includes an `input` / `output` flag indicating where
        it may be used.


        For `content-safety`, `validators[].config.categories` lists the
        available safety categories (`id`, `name`, `description`). When
        configuring an application via PUT, set `config.categories` to an array
        of selected category **id** strings (for example `["violent-crimes",
        "hate"]`). At least one category is required.


        For `pii`, `validators[].config.entities` lists the available PII entity
        types (`id`, `name`, `description`, `group`). When configuring via PUT,
        set `config.entities` to an array of selected entity **id** strings (for
        example `["EMAIL_ADDRESS", "PHONE_NUMBER"]`). At least one entity is
        required.
      operationId: listGuardrailsValidators
      responses:
        '200':
          description: Validator and action catalog.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GuardrailsValidatorsCatalogResponse'
              example:
                success: true
                data:
                  validators:
                    - id: pii
                      name: PII
                      input: true
                      output: true
                      description: Detects personally identifiable information
                  actions:
                    - id: mask
                      name: Mask
                      description: Trusys masks the unsafe portion.
        '401':
          $ref: '#/components/responses/Unauthorized'
components:
  schemas:
    GuardrailsValidatorsCatalogResponse:
      type: object
      properties:
        success:
          type: boolean
        data:
          type: object
          properties:
            validators:
              type: array
              items:
                type: object
            actions:
              type: array
              items:
                type: object
    ErrorResponse:
      type: object
      description: Standard error envelope for non-validation failures.
      properties:
        success:
          type: boolean
          example: false
          description: Always `false` for errors.
        message:
          type: string
          description: Human-readable explanation of the error.
      required:
        - success
        - message
  responses:
    Unauthorized:
      description: >-
        The API key is missing, invalid, or revoked. Verify the `x-api-key`
        header and that the key is active in Trusys settings.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
          example:
            message: Error while verifying api key
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: x-api-key
      description: >-
        Your Trusys API key. Create and manage keys in the Trusys UI under
        **Settings → API Keys**.


        Include the key on every request:


        ```

        x-api-key: <your-api-key>

        ```

````