Deepfake Detection
Analyze audio, images, and video for synthetic tampering. Submit media for detection and retrieve structured metrics and visualizations.
For a single-file request, you can also opt in to Resemble watermark detection and SynthID by setting detect_watermark: true. Watermark evidence is returned separately and never changes the deepfake verdict.
Choose an Integration
Media can be referenced by a public HTTPS url or by a media_token issued from the Secure Upload API. Use a secure upload when you prefer not to host the source file publicly — the API reads it once via the signed token, which expires 1 hour after issuance.
Request Schema
Face-only Video Analysis
Set face_only: true to focus visual video detection on faces by masking non-face regions before analysis. Face-only mode is effective only for video inputs that run visual analysis (modality: "all" or modality: "video"). Audio, image, and audio-only video requests are accepted, but their effective value is false.
Face-only mode does not disable audio analysis or select which video components run. Use modality for that. It also does not change billing or the structure of detection verdicts and reports. Detection responses expose the effective setting in face_only for auditing.
Optional Watermark Analysis
Set detect_watermark: true on a single audio, image, or video detection to run the same decode detectors as the standalone Watermark API:
- Audio checks Resemble Perth v1, Resemble Perth v2, and SynthID.
- Image and video check the Resemble image/video watermark detector and SynthID.
The option defaults to false. When omitted or false, no Watermark job is created, no extra charge is added, and the watermark response field is omitted. When enabled, the existing Watermark detection charge is added to the request; SynthID does not add a separate charge.
Watermark analysis uses the standalone source limits: 25 MB for audio and image, and 100 MB for video. It is not supported for batch or zip submissions.
Response Shapes
For an otherwise successful Detect with watermark analysis, item.status remains processing until the nested Watermark job is terminal. A core detection failure still reports failed. A failed Watermark job is reported in item.watermark without failing an otherwise successful deepfake detection. Intelligence remains independently asynchronous unless its own wait behavior is requested.
Legacy Response Fields
Use the endpoints below to submit jobs and retrieve detection results for each modality.
Related Endpoints
- Create Detection - Submit a detection job
- Streaming Audio Detection - Analyze live audio over a WebSocket
- Batch Detection - Submit up to 50 files as one job
- Get Detection - Retrieve a single detection result
- List Detects - Retrieve all detection results with pagination
