Month-end usage
Priya Sharma, finance manager at Acme Ltd, asked what Deepgram cost last month and where it went. Memtro gave the billed total in US dollars grouped by line item, and the audio hours behind it.
How many audio hours did we use this month, and what did they cost?
Deepgram connects Memtro to your speech AI account. It reads the projects the key can see, each project's request log with when, which endpoint and status, never what was said, usage by audio hours, requests, tokens and characters, billing in US dollars by line item, tag, key or deployment, balances, the public speech and voice models, and saved voice agent configurations. When asked, and once an administrator has granted the action by name, it can transcribe an audio file by URL, which Deepgram bills per audio hour, create, relabel or delete a voice agent configuration, and rename a project.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Deepgram tool, reads what it needs, and answers with the source cited.
These tools change something in Deepgram. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once Deepgram is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
How many audio hours did we use this month?
What were we billed last month, by model?
Which requests failed yesterday?
What is our outstanding balance?
Transcribe the call recording at this URL
Priya Sharma, finance manager at Acme Ltd, asked what Deepgram cost last month and where it went. Memtro gave the billed total in US dollars grouped by line item, and the audio hours behind it.
Dan Fletcher, product manager at Northwind, asked Memtro to transcribe a customer call recording from a shared link. Memtro sent it to Deepgram, which billed the project for the audio hours, and returned the transcript.
The teams that lean on Deepgram most, a question each of them asks, and what they connect beside it.
A record in Deepgram is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In the Deepgram Console, open your project → Settings → API Keys and create a new API key named Memtro.
Pick a role that can read usage and billing if you want those answered. Copy the key: it is shown once.
In Memtro, open Connections → Deepgram and paste it into API key. Fill in Project id if the key sees more than one project, and Region for transcription outside North America.
Ask your first question: how many audio hours did we use this month?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Deepgram tools are the same everywhere.
Only when you ask, and only what it has been granted: transcribe an audio file at a URL (billed per audio hour plus features); create a voice agent configuration; change a voice agent configuration's labels; delete a voice agent configuration (anything using its id stops working); rename a project. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
API key. In the Deepgram Console, open your project → Settings → API Keys and create a new API key named Memtro.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time