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

# Detectors Overview

> Available detectors and their configurations

## Introduction

Detectors are the building blocks of judges. Each detector analyzes specific aspects of content and can be configured with custom parameters.

## Configuration Format

When creating a judge using the v1 endpoint, detectors are configured in the `detectors` array:

```json theme={null}
{
  "name": "My Judge",
  "description": "Judge description",
  "content_type": "video",
  "detectors": [
    {
      "detector_name": "video_specs",
      "config": {
        "min_width": 1920,
        "min_height": 1080,
        "min_fps": 24
      }
    },
    {
      "detector_name": "audio_noise",
      "config": {}
    }
  ]
}
```

## Available Detectors

### Content Matching Detectors

| Detector                     | Description                                                    |
| ---------------------------- | -------------------------------------------------------------- |
| `audio_matching`             | Checks whether audio matches reference audio                   |
| `podcast_video_matching`     | Matches podcast/talk-show clips against reference episodes     |
| `splitscreen_video_matching` | Checks split-screen content against references or descriptions |
| `video_matching`             | Checks whether video matches reference videos                  |
| `video_matching_description` | Checks whether video content matches a description             |

### Content Analysis Detectors

| Detector                | Description                                                   |
| ----------------------- | ------------------------------------------------------------- |
| `language`              | Checks detected language against an allowed list              |
| `sentiment`             | Checks sentiment and prohibited content in transcripts        |
| `title_and_description` | Checks title and description for required elements            |
| `transcript_policy`     | Checks transcripts for required and prohibited language       |
| `transcript_product`    | Counts brand and product mentions in transcripts              |
| `clipper_demographics`  | Extracts demographic data from social media screen recordings |

### Video Visual Analysis Detectors

| Detector               | Description                                           |
| ---------------------- | ----------------------------------------------------- |
| `background`           | Assesses background conditions in the video           |
| `framing`              | Checks whether framing meets composition expectations |
| `lighting`             | Evaluates lighting balance across video frames        |
| `overlays`             | Checks for required or disallowed overlays            |
| `product_application`  | Checks whether a product is being applied             |
| `subtitles`            | Checks for subtitle presence                          |
| `transition_detection` | Counts scene transitions                              |
| `video_quality`        | Evaluates overall video quality                       |
| `video_specs`          | Validates video dimensions and duration               |
| `wardrobe`             | Checks wardrobe and beauty rule compliance            |

### Image Visual Analysis Detectors

| Detector                | Description                                 |
| ----------------------- | ------------------------------------------- |
| `image_ip_infringement` | Flags potential IP concerns in images       |
| `image_sharpness`       | Evaluates image sharpness                   |
| `image_specs`           | Validates image dimensions and aspect ratio |

### Audio Analysis Detectors

| Detector        | Description                                   |
| --------------- | --------------------------------------------- |
| `audio_noise`   | Evaluates background noise and speech clarity |
| `pronunciation` | Evaluates brand and product pronunciation     |
| `voice_over`    | Detects voice-over narration                  |

## Reference Content

Some detectors require reference content (for example, reference videos or audio) for comparison. Reference content must be uploaded to Google Cloud Storage and provided as `gs://` URIs.

### Detectors Requiring Reference Content

* **audio\_matching** - Requires `reference_audio`
* **podcast\_video\_matching** - Requires `reference_videos`
* **video\_matching** - Requires `reference_videos`
* **splitscreen\_video\_matching** - Requires at least one of `top_content_references` or `bottom_content_references`
* **pronunciation** - Optional `brand_audio_url` and `product_audio_url`

### Uploading Reference Content

1. Use the `/v1/judges/reference_content` endpoint to get a pre-signed upload URL
2. Upload your reference file to the provided URL
3. Use the returned `reference_content_uri` in your detector configuration

## Configuration Validation

* Detector names must be valid (from the list above)
* Required configuration keys must be provided for each detector
* Reference content URIs must use the `gs://` scheme
* File extensions for reference content must match allowed types

## Next Steps

* See individual detector documentation for detailed configuration options
* Check the [Create Judge](/api-docs/api-reference/judges/create-judge) endpoint for full examples
* Review detector-specific configuration schemas for required and optional parameters