Skip to main content

What You’ll Build

A complete deposition processing pipeline that:
  1. Transcribes audio with speaker identification
  2. Stores transcripts in a searchable vault
  3. Generates timelines of key testimony
  4. Cross-references witnesses to find contradictions
  5. Produces formatted impeachment reports
Time to complete: 30 minutes

Architecture

Prerequisites

  • Case.dev API key (get one here)
  • A vault for storing transcripts
  • Deposition audio files (MP3, M4A, WAV, etc.)

Step 1: Set Up Your Vault

Create a vault to hold all deposition transcripts for a case:

Step 2: Upload and Transcribe a Deposition

Upload the audio file to your vault, then transcribe with speaker labels:
Speaker labels are automatic. The transcription service identifies speakers by voice characteristics. Set speakers_expected for better accuracy when you know the number of participants.

Step 3: Store Transcript in the Vault

The vault-based transcription automatically stores the transcript. Now ingest it for semantic search:
For production, use webhooks instead of polling for both transcription and ingestion status changes.

Step 4: Batch Process Multiple Depositions

Process all depositions for a case in sequence:

Step 5: Generate a Testimony Timeline

Search across all depositions and build a chronological timeline of events:

Step 6: Find Contradictions Across Witnesses

Search for a topic and compare what different witnesses said:

Complete Example

Putting it all together:

Example Contradiction Report


Production Tips

Error Handling

Use Webhooks in Production

Instead of polling, subscribe to events for transcription and ingestion completion:
For long depositions (2+ hours), transcription may take several minutes. Webhooks prevent wasted polling requests.

Next Steps