Introduction
Detectors are the building blocks of judges. Each detector analyzes specific aspects of content and can be configured with custom parameters. When creating a judge, you specify which detectors to use and their configurations.Configuration Format
When creating a judge using the v1 endpoint, detectors are configured in thedetectors array:
Available Detectors
Content Quality Detectors
| Detector | Description |
|---|---|
audio_noise | Detects background noise and audio quality issues |
image_sharpness | Detects blurry or out-of-focus images |
image_specs | Validates image dimensions and aspect ratios |
lighting | Analyzes lighting quality in visual content |
video_quality | Validates video technical specifications |
video_specs | Checks video dimensions, duration, and frame rate |
Content Matching Detectors
| Detector | Description |
|---|---|
audio_matching | Matches audio against reference content |
splitscreen_video_matching | Matches split-screen video content |
video_matching | Matches video against reference content |
video_matching_description | Matches video against text description |
Content Analysis Detectors
| Detector | Description |
|---|---|
content_quality | Evaluates overall content quality |
language | Detects and validates content language |
sentiment | Analyzes emotional tone and sentiment |
transcript_policy | Checks transcript against policy guidelines |
transcript_product | Detects product mentions in transcripts |
Visual Analysis Detectors
| Detector | Description |
|---|---|
background | Analyzes background elements |
framing | Evaluates shot composition and framing |
image_ip_infringement | Checks for potential IP violations |
overlays | Detects text overlays and graphics |
product_application | Detects product usage demonstrations |
subtitles | Detects subtitle presence |
wardrobe | Analyzes clothing and appearance |
Audio Analysis Detectors
| Detector | Description |
|---|---|
pronunciation | Checks brand/product name pronunciation |
voice_over | Detects voice-over narration |
Metadata Detectors
| Detector | Description |
|---|---|
title_and_description | Analyzes the content title and description for topic, mentions, and hashtags |
transition_detection | Detects scene transitions and cuts |
Reference Content
Some detectors require reference content (e.g., reference videos, audio files) for comparison. Reference content must be uploaded to Google Cloud Storage and provided asgs:// URIs.
Detectors Requiring Reference Content
- audio_matching - Requires
reference_audio - video_matching - Requires
reference_video - splitscreen_video_matching - Requires at least one of
source_video_referenceorbottom_content_reference - pronunciation - Optional
brand_audio_urlandproduct_audio_url
Uploading Reference Content
- Use the
/v1/judges/reference_contentendpoint to get a pre-signed upload URL - Upload your reference file to the provided URL
- Use the returned
reference_content_uriin 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 endpoint for full examples
- Review detector-specific configuration schemas for required and optional parameters