deepgram-transcribe
Transcribe audio and video recordings (meetings, calls, interviews) with Deepgram and get a Markdown transcript plus the raw JSON response.
For meeting.m4a you get meeting.json (the full Deepgram response, never your API key) and
meeting.md (frontmatter, optional summary and topics, speaker-labelled timestamped transcript).
Install
uvx deepgram-transcribe --help # run without installing
uv tool install deepgram-transcribe # installs the `dgt` command
Requires Python 3.11+. Both dgt and deepgram-transcribe are installed.
API key
Get a key from the Deepgram console, then provide it in one of these ways (highest precedence first):
--api-keyon the command line- the
DEEPGRAM_API_KEYenvironment variable api_keyin the config file
export DEEPGRAM_API_KEY=your-key
Usage
Transcribe recordings (globs are expanded by the tool; quote them so ** works):
dgt run meeting.m4a
dgt run --output-dir ~/Transcripts "recordings/**/*.mp3"
dgt meeting.m4a # shortcut for `run`
dgt run --summarize --topics --language en call.wav
dgt run --keyterm Reaktor --param tier=enhanced meeting.m4a
Re-render Markdown from saved JSON, without calling the API:
dgt render meeting.json
dgt render --force --date 2026-10-07 *.json
Common options: --output-dir DIR, --force (overwrite; otherwise files with existing outputs are
skipped), --date mtime|now|YYYY-MM-DD, --config PATH, -q/--quiet, -v/--verbose.
Run dgt run --help for the full list of Deepgram flags (--model, --language, --diarize,
--smart-format, --paragraphs, --keyterm, --redact, --param KEY=VALUE, ...).
Exit codes: 0 success or skipped, 1 at least one file failed, 2 usage or config error.
Config file
Location: $XDG_CONFIG_HOME/deepgram-transcribe/config.toml, falling back to
~/.config/deepgram-transcribe/config.toml. A missing file is fine.
api_key = "..." # optional
output_dir = "~/Transcripts" # optional
date = "mtime" # optional
timeout = 600 # optional, seconds
[deepgram] # defaults for any Deepgram query param
model = "nova-3"
language = "multi"
keyterm = ["Reaktor", "Hermes"]
Precedence per option: CLI flag > config [deepgram] > built-in default.
English-only features
--summarize, --topics, --intents and --sentiment only work for English. They are sent only
when the effective language starts with en and language detection is off. With the default
language = "multi" they are dropped with a warning, so pass --language en to use them.
More
Full behaviour is described in the spec. Licensed under MIT.
Metadata
Release files for deepgram-transcribe 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| deepgram_transcribe-0.1.0.tar.gz | 65.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| deepgram_transcribe-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 83.8 kB
Release files / deepgram_transcribe-0.1.0.tar.gz
| Download URL | deepgram_transcribe-0.1.0.tar.gz |
|---|---|
| Size | 65.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
16f4d32b4bc76cd0b54da0b755a1a345c9f33213e53466c2f5b7ee389eab5308
|
|
BLAKE2b-256 checksum How to use checksums |
9e928242c9bbaecba6c28709b2aaf903a25a1b449b376f5c7741c0cafbf5b33e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 9, 2026.
Transparency logRelease files / deepgram_transcribe-0.1.0-py3-none-any.whl
| Download URL | deepgram_transcribe-0.1.0-py3-none-any.whl |
|---|---|
| Size | 18.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3498ecb620d9ce4ff31f5465c74d57eee2e55334240790eed4db1e055249e02b
|
|
BLAKE2b-256 checksum How to use checksums |
42ee3b39f77fa495cc874df410019ccfe03916eb8b469d8ed9ee6bcac61bd1b1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 9, 2026.
Transparency log