AI video detection API
Detect signals of AI-generated visuals, audio and metadata in video.
Explore video API →API / v1
Detection APIs
Bring detection capabilities into your application with a single API token.
Explore API products, documentation and integration examples to find the detection service you need.
Developer dashboardAPI Usage Guide
1. One account. Clear limits.
- Only signed-in users can use the API.
- Up to 10 API tokens per account. View and copy keys in the dashboard, and enable, disable or set an expiry date for each token.
- All /api/v1 requests share one account limit: one admitted request every second, including submissions, reads, polling and retries. Future services share this limit.
- Detection runs asynchronously. Request frequency is independent of active task concurrency: Basic 1, Pro 2, Premium 3, shared with the website; up to 24 unfinished jobs per account.
- API jobs use credits. Video cost is one credit per started minute, based on server-verified duration.
- API results are independent of website video capacity, with no storage-count quota. Results are retained for six months after a task ends. History displays the latest 10,000 records, with 100 per page by default. Deleting a record does not refund completed detections.
2. Authentication & retries
Send Authorization: Bearer YOUR_TOKEN from your server. Keep tokens out of browsers, URLs and source control. Use one coordinated request queue if several processes share the account.
A 429 response includes Retry-After (seconds). Creation endpoints require an Idempotency-Key (1–128 letters, numbers, dots, underscores, colons or hyphens). Retry the same request with the same key; changing its payload returns 409. Keep keys after a timeout. Expired resources cannot be recreated with an old key.
Authorization: Bearer avd_…3. Billing & retention
Credits are reserved when a job is accepted, then charged on success. Failures release the reservation once. Actual refunds are recorded in your credit history; cancelling a queued job does not restore expired credits.
All accounts retain API results for six calendar months after a task ends, as indicated by expires_at, independently of website capacity or subscription changes. History displays the latest 10,000 records with 10, 20, 50 or 100 per page; at 100 per page there are at most 100 pages. Unexpired results outside the list remain accessible by task ID. Request logs include detection submissions, cancellations and failures after authentication; successful reads are not logged. Each account retains the latest 200 entries from the past three days, with 50 per page. Charges, refunds and essential deduplication records are retained independently long term. Expired results are cleaned up without deleting source videos.