Skip to main content

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:

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 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 endpoint for full examples
  • Review detector-specific configuration schemas for required and optional parameters