Deepgram project usage digest
Read-only Deepgram usage and balance workflow. It reads one project, usage fields, usage breakdown, and balances for the selected date range, then summarizes usage, feature mix, model mix, and outstanding balances. It never creates keys, changes members, mutates projects, exports purchases, creates self-hosted credentials, starts transcription, or calls arbitrary Deepgram routes.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (14 steps)
project
?
fields
?
breakdown
?
balances_raw
?
usage_rows_raw
default
Apply default
balances_all
default
Apply default
usage_rows
slice
Take a subset of
balances
slice
Take a subset of
usage_row_count
count
Count items in usage rows raw
balance_count
count
Count items in balances all
summarize
?
usage_table
to_table
Format results as a data table
balance_table
to_table
Format results as a data table
card
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
end
setting
=
focus
setting
=
Summarize Deepgram project identity, usage volume, request mix, feature and model signals, date range caveats, and outstanding balances. Use only the Deepgram responses.
start
setting
=
deepgram
setting
=
grouping
setting
=
endpoint
row limit
setting
=
25
max length
setting
=
900
project id
setting
=
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.