Skip to main content
FastDrop lets you search across all transcribed videos in a batch using keyword, semantic, or hybrid search. Search is free (0 credits per query) after the initial transcription cost.

How it works

  1. Transcribe your videos using the /transcribe endpoint or include transcribe in batch capabilities
  2. Search the batch using POST /v1/batch/{id}/search
Each transcribed video is broken into timestamped segments. When you search, FastDrop finds the segments that match your query and returns them with the video filename, timestamps, and a relevance score.
Search works on any transcribed batch. Classification is not required. You can transcribe and search without ever running classify.

Search modes

Keyword

Full-text search using PostgreSQL with language-aware stemming. Best for finding exact phrases, names, or specific terms.

Semantic

Embedding-based similarity search. Understands meaning, not just words. Best for finding topics discussed in different phrasing.

Hybrid (default)

Combines keyword and semantic search with score fusion (0.4 keyword + 0.6 semantic). Best overall accuracy for most queries.
When videos are transcribed with translation enabled, each segment is stored in both the source language and English. This means you can:
  • Search Arabic footage using English queries
  • Search Japanese interviews for English keywords
  • Find content across languages in a single query
Semantic search searches all languages by default. Keyword search works across both source and translated text.

Credit costs

Code examples

Search a batch

Example response

Response fields

What works well

  • Finding specific topics discussed across many videos
  • Locating quotes or key moments by content
  • Searching multilingual footage in English
  • Building searchable archives of interviews, lectures, or meetings

Limitations

  • Search requires transcription first — silent or music-only videos won’t have searchable content
  • Domain-specific jargon may affect keyword search accuracy
  • Semantic search works best with natural language queries, not single keywords

Error responses