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 thedetectors array:
Available Detectors
Content Matching Detectors
Content Analysis Detectors
Video Visual Analysis Detectors
Image Visual Analysis Detectors
Audio Analysis Detectors
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 asgs:// 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_referencesorbottom_content_references - 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