Join a video meeting as an AI bot with voice, avatar, and screenshare across four operating modes.
Design & media
gladia-audio-intelligence
Try itConfigure and use Gladia audio intelligence features: speaker diarization, translation, sentiment analysis, named entity recognition (NER), PII redaction, subtitles (SRT/VTT), summarization, custom vocabulary, and audio-to-LLM. Use when the user asks about any audio intelligence feature, enabling features on pre-recorded or live transcription, understanding which features are available in each mode, or combining multiple features. Always prefer the official SDK; fall back to raw REST only when SDK cannot satisfy the requirement.
What it does
Gladia's audio intelligence features extract structured data and insights from transcripts. They work on top of the base transcription — most are enabled by adding options to the call (pre-recorded) or the config (live).
The skill document
Audio Intelligence
Gladia's audio intelligence features extract structured data and insights from transcripts. They work on top of the base transcription — most are enabled by adding options to the transcribe() call (pre-recorded) or the startSession() config (live).
SDK-first: always use the official SDK — see gladia-sdk-integration for policy, setup, and fallback criteria.
When to Use
- User asks about a specific feature: diarization, translation, PII redaction, sentiment, NER, subtitles, summarization, etc.
- Enabling or configuring one or more audio intelligence features on pre-recorded or live transcription
- Understanding which features are available in live vs pre-recorded mode
- Combining multiple features in a single transcription job
When NOT to use: For basic transcription without audio intelligence features, go directly to gladia-pre-recorded-transcription or gladia-live-transcription. For gotchas and errors related to specific features, see gladia-troubleshooting.
References
Consult these resources as needed:
- ./references/live-audio-intelligence.md -- Detailed config and WebSocket responses for all live-mode features
- ./references/pre-recorded-audio-intelligence.md -- Detailed config and response structures for all pre-recorded audio intelligence features
- ../gladia-pre-recorded-transcription/SKILL.md -- Pre-recorded transcription workflow and options
- ../gladia-live-transcription/SKILL.md -- Live transcription session config and event handling
- ../gladia-sdk-integration/SKILL.md -- SDK setup, client initialization, and SDK vs raw API decision guide
- ../gladia-troubleshooting/SKILL.md -- Common errors, gotchas, and verification checklist
Feature Availability
| Feature | Pre-recorded | Live | Config key |
|---|---|---|---|
| Speaker diarization | Yes | No | diarization |
| Translation | Yes | Yes | translation |
| Sentiment analysis | Yes | Yes | sentiment_analysis |
| Named entity recognition | Yes | Yes | named_entity_recognition |
| Subtitles (SRT/VTT) | Yes | No | subtitles |
| Custom vocabulary | Yes | Yes | custom_vocabulary |
| PII redaction | Yes | No | pii_redaction |
| Chapterization | Yes | Yes | chapterization (post-process) |
| Summarization | Yes | Yes | summarization (post-process) |
| Audio-to-LLM | Yes | No | audio_to_llm |
| Custom spelling | Yes | Yes | custom_spelling |
| Custom metadata | Yes | Yes | custom_metadata |
Live features split into two groups: real-time (results stream during the session) and post-processing (results arrive after stopRecording()). See ./references/live-audio-intelligence.md for details.
Quick Config Examples
Code examples assume GladiaClient is already initialized — see gladia-sdk-integration for setup.
Speaker Diarization (pre-recorded only)
const result = await client.preRecorded().transcribe("audio.mp3", {
diarization: true,
diarization_config: { number_of_speakers: 2 },
});
// Each utterance includes a `speaker` field (0-indexed integer)
result = client.prerecorded().transcribe("audio.mp3", {
"diarization": True,
"diarization_config": {"number_of_speakers": 2},
})
Translation (pre-recorded and live)
Pre-recorded:
const result = await client.preRecorded().transcribe("audio.mp3", {
translation: true,
translation_config: { target_languages: ["fr", "es"] },
});
result = client.prerecorded().transcribe("audio.mp3", {
"translation": True,
"translation_config": {"target_languages": ["fr", "es"]},
})
Live (result streams as translation WebSocket events — see live-audio-intelligence.md):
const session = client.liveV2().startSession({
// ... audio format options ...
realtime_processing: {
translation: true,
translation_config: { target_languages: ["fr"] },
},
});
from gladiaio_sdk import LiveV2InitRequest, LiveV2RealtimeProcessing
session = client.live().start_session(
LiveV2InitRequest(
# ... audio format options ...
realtime_processing=LiveV2RealtimeProcessing(
translation=True,
translation_config={"target_languages": ["fr"]},
),
)
)
Summarization (pre-recorded and live)
Pre-recorded:
const result = await client.preRecorded().transcribe("audio.mp3", {
summarization: true,
summarization_config: { type: "bullet_points" },
});
Live (arrives after stopRecording() as post_summarization event):
const session = client.liveV2().startSession({
// ... audio format options ...
post_processing: {
summarization: true,
summarization_config: { type: "bullet_points" },
},
});
session.on("message", (msg) => {
if (msg.type === "post_summarization") console.log(msg.data.results);
});
For full per-feature config options and response structures, see:
- Pre-recorded: ./references/pre-recorded-audio-intelligence.md
- Live: ./references/live-audio-intelligence.md
Common Mistakes
code_switching: truewith emptylanguages: triggers evaluation across 100+ languages and causes frequent misdetections. Always provide 3-5 expected languages.- Custom vocabulary
intensityabove 0.6: values over 0.6 cause false positives where unrelated words get replaced. Keep at 0.4-0.6 and usepronunciationsfor better results. - Expecting diarization, PII redaction, subtitles, or audio-to-LLM in live mode: these four features are pre-recorded only.
- Enabling many features simultaneously without considering cost/latency: each enabled feature adds processing time. Enable only what you need; combine
diarization + summarization + translationonly when all are required.
For the full gotcha list, see gladia-troubleshooting.
Further Reading
Related skills
Stores durable facts in a categorized, plain-markdown vault on disk, alongside your agent's built-in memory.
Generate and edit Draw.io, Mermaid, and Excalidraw diagrams from natural language using a structured JSON spec.
Fetch raw ad creative, app, ranking, and revenue data from AdMapix as structured JSON.
Find why your productivity system keeps failing, then apply the smallest fix — capacity math, bottleneck routing, durable local notes.
Run Git operations — commits, branches, merges, rebases, conflict resolution, and recovery — with safety rules enforced.
More from gladiaio
Browse all skillsGladia speech-to-text reference: endpoints, workflows, model guidance, and SDK-first integration patterns.
Transcribe pre-recorded audio files or URLs with Gladia. Use when the user needs batch/async transcription, speaker diarization, subtitles (SRT/VTT), PII redaction, translation, NER, summarization, audio-to-LLM, or any audio intelligence on pre-recorded content. Always prefer the official SDK; fall back to raw REST only when SDK cannot satisfy the requirement.
Install and configure the official Gladia SDKs (@gladiaio/sdk for JS/TS, gladiaio-sdk for Python). Use when the user asks about SDK setup, client initialization, API key configuration, choosing between JS and Python, browser usage, retry/timeout settings, error handling, or SDK vs raw API decisions. The SDK is the recommended default for all Gladia integrations.
Real-time speech-to-text streaming with Gladia via WebSocket. Use when the user needs live transcription, builds a voice agent, meeting recorder, call center integration, live subtitles, or any application streaming audio for low-latency partial and final transcripts. Always prefer the official SDK; fall back to raw WebSocket/REST only when SDK cannot satisfy the requirement.
Diagnose and fix common Gladia API issues. Use when the user encounters errors (401, 403, 429), unexpected behavior, poor transcription quality, billing conf...
Terminal transcription of audio files and URLs with the Gladia CLI (gladia speech-to-text). Use when the user has gladia-cli installed, wants shell-based transcription, or asks an agent to transcribe audio then answer questions about the content. For audio intelligence features not available as CLI flags, use the SDK skills instead.