The multimodal warehouse · Audio
Find what was said, and when, in every recording.
Calls, podcasts and broadcasts become searchable segments with their transcript and sound. They sit in the same warehouse as your video and documents, so a call can be joined to the account it came from and a jingle can be found inside every video it plays in.
From $25/mo. Index once. Query every way.
| segment | A stretch of audio cut at the pause | 02:10 to 02:31 |
| transcript | “I was charged twice for the same order” | 02:12 to 02:18 |
| sound | A CLAP embedding of how it sounds | 02:10 to 02:31 |
| metadata | call_id and account_id, as you supplied them | fields |
One warehouse
Your audio files sit beside every other file you own.
Each file is broken into rows that point back to the file they came from. Video scenes, images, audio segments and document blocks live in one namespace, so a question can start in one kind of file and finish in another.
Joins your audio files make
Put the customer's account record next to every call that mentions a refund.
call segmentsyour SQL table
Runs on the SQL lookup stageDid the agent say what the approved script says?
call transcriptsscript documents
Runs on the Cross compare stageFind our jingle in every video it plays in.
a sound markvideo audio tracks
Runs on the Feature search stageWhat you can ask
Ask in plain words, or with a file.
› customer asks for a refund
Segments where it was said, with timestamps
› the episode where they discuss pricing
Transcript matches across the archive
› this 5 second sound
Every recording it appears in
› calls from enterprise accounts last week
Semantic matches filtered by your fields
Start in one click
Point it at your audio files
An empty namespace
Connect the bucket your audio files already live in and pick the extractors. Studio indexes it and your first query runs against your own files.
Create a namespace →In code
One call to search what was indexed.
The extractors that turn audio files into rows:
- Multimodal →Segments, Whisper transcripts and embeddings
- Audio fingerprint →Sound marks, jingles and duplicates
- Text →Embeddings for transcripts and notes
from mixpeek import Mixpeek
client = Mixpeek(api_key="YOUR_API_KEY")
# Create a collection with audio feature extractors
collection = client.collections.create(
name="podcast-archive",
namespace="podcasts",
extractors=[
{
"type": "audio_transcription",
"model": "whisper-large-v3",
"config": {
"language": "en",
"diarize": True,
"word_timestamps": True
}
},
{
"type": "audio_embedding",
"model": "clap-large",
"config": {
"segment_duration": 30
}
}
]
)
# Upload audio files to trigger processing
client.buckets.upload(
bucket="my-bucket",
files=["episode_042.mp3", "episode_043.mp3"],
collection=collection.id
)
# Search across transcripts and audio embeddings
results = client.retrievers.execute(
namespace="podcasts",
stages=[
{
"type": "feature_search",
"method": "hybrid",
"query": {
"text": "discussion about machine learning in healthcare",
"modalities": ["text", "audio"]
},
"limit": 20
},
{
"type": "filter",
"conditions": {
"metadata.speaker_count": {"$gte": 2}
}
},
{
"type": "rerank",
"model": "cross-encoder",
"limit": 5
}
]
)
for result in results:
print(f"Episode: {result.metadata['filename']}")
print(f"Timestamp: {result.metadata['start_time']}s")
print(f"Speaker: {result.metadata['speaker']}")
print(f"Transcript: {result.content}")Questions
What people ask about audio search
What is an audio search API?
An audio search API enables developers to index and search audio content programmatically. Instead of manually listening to recordings, you can transcribe speech, extract audio features, and build searchable indexes that support text queries over transcripts, speaker-based filtering, audio similarity search, and event detection. Mixpeek provides a complete audio search infrastructure that handles transcription, embedding generation, indexing, and retrieval in a single platform.
How does speech-to-text search work in Mixpeek?
Mixpeek uses production-grade ASR (automatic speech recognition) models like Whisper to transcribe audio into text with word-level timestamps and speaker labels. The transcriptions are indexed into Mixpeek Vector Store namespaces alongside audio embeddings. When you search, Mixpeek's retriever pipelines combine keyword matching over transcripts with vector similarity over audio embeddings, returning precise audio segments with timestamps.
What audio formats does Mixpeek support?
Mixpeek supports all common audio formats including MP3, WAV, FLAC, AAC, OGG, M4A, WMA, and AIFF. Audio files are uploaded to Mixpeek buckets and processed by feature extractors running on Ray GPU clusters. The platform handles format conversion, sample rate normalization, and channel mixing automatically during ingestion.
Can I search for specific speakers across audio files?
Yes. Mixpeek extracts speaker embeddings during ingestion using speaker diarization models. These embeddings are stored as searchable vectors in your namespace. You can find all segments spoken by a specific person across your entire audio collection, cluster unknown speakers, and filter search results by speaker identity using retriever pipeline stages.
How is Mixpeek different from Deepgram or AssemblyAI?
Deepgram and AssemblyAI are transcription services -- they convert speech to text but leave search infrastructure to you. Mixpeek is a complete search platform: it handles transcription, audio embedding generation, vector indexing, and composable retriever pipelines out of the box. Mixpeek also supports multimodal search, so you can search across audio, video, images, and documents in a single query.
Does Mixpeek support real-time audio processing?
Mixpeek supports both real-time and batch audio processing. For real-time use cases, collection triggers automatically process new audio files as they arrive in your bucket. For batch processing, you can submit large volumes of audio files and Mixpeek's Ray clusters scale horizontally to process them in parallel with progress tracking.
Can I detect non-speech audio events?
Yes. Beyond speech transcription, Mixpeek's audio feature extractors can classify non-speech audio events such as music, alarms, applause, machinery sounds, environmental noise, and more. These events are indexed as metadata on audio segments, enabling you to filter and search by event type in your retriever pipelines.
How does audio search integrate with video search in Mixpeek?
Mixpeek treats audio and video as complementary modalities within a unified namespace. When you process a video file, Mixpeek extracts both visual features (frames, objects, scenes) and audio features (transcripts, speaker embeddings, audio events) and indexes them together. A single retriever query can search across both the audio track and visual content of your video collection simultaneously.
Put your audio files in the warehouse.
Index them once, then ask them anything, alone or joined to the rest of your files.
Other file types:VideoImagesDocumentsHow the warehouse works