Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
Deepgram (BYOK) icon

Deepgram (BYOK)

Read your Deepgram projects, models, usage, billing breakdown, balances, purchases and request history with BYOK

Unify Dynamics LLC

Tools9read-only
Sign-inBYOKbring your own key
Key keptNeverused for one call only
PriceFreeoptional Pro limits
ProviderDeepgramunofficial, not affiliated
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

Which Deepgram projects does my key belong to?
Tools called
list_projects
What is the name of my Deepgram project?
Tools called
get_project
Which Deepgram speech-to-text models support streaming?
Tools called
list_speech_to_text_models
Which Deepgram text-to-speech voices are available?
Tools called
list_text_to_speech_models
How much Deepgram credit do I have left?
Tools called
get_balances
What Deepgram credits have I bought?
Tools called
list_purchases

About

Deepgram (BYOK) lets an AI assistant read your own Deepgram data through the Deepgram API with a key you supply (API key (with usage and billing scopes for those tools)). Read-only: 9 tools (list_projects, get_project, list_speech_to_text_models, list_text_to_speech_models, get_balances, list_purchases, get_usage_breakdown, get_billing_breakdown, list_requests). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.deepgram.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Deepgram. Deepgram and its logos are trademarks of their owners and are used only to say which service the connector works with.

Sources: Live from the Deepgram API (api.deepgram.com) with a BYOK key; documentation: https://developers.deepgram.com/reference/manage/projects/list. Endpoints checked against that documentation on 2026-10-16.

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.

What it can do

9 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Read your data9 tools
  • List projectsList the Deepgram projects the key can access with id and name.
  • Get projectGet one Deepgram project by id: name and model-improvement opt-out flag.
  • List speech to text modelsList Deepgram speech-to-text models with architecture, version, languages and whether they support batch and streaming.
  • List text to speech modelsList Deepgram text-to-speech voices and models with architecture, version, languages and accent or age metadata.
  • Get balancesShow the prepaid credit balances of a Deepgram project with amount and units.
  • List purchasesList credit purchases (orders) of a Deepgram project with amount, units, type and dates.
  • Get usage breakdownShow Deepgram usage for a date range: hours, requests, tokens and text-to-speech characters, optionally grouped by endpoint, model, method and more.
  • Get billing breakdownShow Deepgram billing in dollars for a date range, optionally grouped by line item, deployment, tags or accessor.
  • List requestsList recent Deepgram API requests of a project with id, time, path, deployment, HTTP-style status code and API key id.

Information

PublisherUnify Dynamics LLC
CategoryDeveloper tools
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://byok-deepgram.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide
FunctionOther
LayerDeep connectors

Connect it to your agent

Three ways in, the same 9 tools.

MCP (Claude, Cursor, Windsurf, VS Code, any MCP client)https://byok-deepgram.connectorbay.com/mcp
RESTPOST https://byok-deepgram.connectorbay.com/v1/tools/<tool>
OpenAI function callinghttps://connectorbay.com/openai/byok-deepgram.json
OpenAI-compatible chathttps://connectorbay.com/v1/chat/completions · how it works
  • Add the MCP URL in your client's connector, MCP or integration settings (streamable HTTP, no OAuth).
  • Key: send your API key (with usage and billing scopes for those tools) in the X-Upstream-Key header (get one at console.deepgram.com).
  • Ask a question; the agent picks the right tool and answers from the live data.

Deepgram connector: questions and answers

What is the Deepgram connector?

Deepgram (BYOK) lets an AI assistant read your own Deepgram data through the Deepgram API with a key you supply (API key (with usage and billing… It is a hosted MCP server with 9 tools such as List projects, Get project, List speech to text models, List text to speech models, Get balances, List purchases, published by Unify Dynamics LLC. It is independent and not affiliated with Deepgram.

How do I connect Deepgram to Claude, ChatGPT or Cursor?

Add the MCP endpoint https://byok-deepgram.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-deepgram.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-deepgram.json.

Do I need a Deepgram account or API key?

Yes: this is a bring-your-own-key connector. Create a API key (with usage and billing scopes for those tools) at https://console.deepgram.com/ and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.

Is Deepgram read-only?

Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.

Is the Deepgram connector free?

Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.

More like this

More in Other

Fastly (BYOK)

Read your Fastly services, versions, domains, backends and historical delivery statistics with BYOK

Live · MCP + REST9 tools

Fathom Analytics (BYOK)

Read your Fathom Analytics sites, event definitions, current visitors and pageview or event aggregation reports with your own API token

Live · MCP + REST7 tools

Featherless (BYOK)

Read your Featherless AI plan limits, credit balance, spend and usage history and browse the model catalogue with your own API key

Live · MCP + REST6 tools

Figma Design System (BYOK)

Read your published Figma team libraries (components, component sets, styles), variables and dev resources with your own personal access token

Live · MCP + REST10 tools

Figma Library Analytics (BYOK)

Read usage and adoption analytics of your Figma design libraries (components, styles, variables) with your own personal access token

Live · MCP + REST6 tools

Figshare (BYOK)

Search public Figshare research data, papers and software, and read your own private items, collections and projects with your own personal token

Live · MCP + REST11 tools

Documentation

Back to top

Deepgram (BYOK) — connector documentation

  • MCP endpoint: https://byok-deepgram.connectorbay.com/mcp
  • REST API: POST https://byok-deepgram.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-deepgram.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Deepgram API key (with usage and billing scopes for those tools), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-deepgram.connectorbay.com/health · Tool schemas: https://byok-deepgram.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-deepgram · agent@connectorbay.com

What Deepgram (BYOK) is for

Deepgram (BYOK) lets an AI assistant read your own Deepgram data through the Deepgram API with a key you supply (API key (with usage and billing scopes for those tools)). Read-only: 9 tools (list_projects, get_project, list_speech_to_text_models, list_text_to_speech_models, get_balances, list_purchases, get_usage_breakdown, get_billing_breakdown, list_requests). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.deepgram.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Deepgram. Deepgram and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which Deepgram projects does my key belong to?"
  • "What is the name of my Deepgram project?"
  • "Which Deepgram speech-to-text models support streaming?"
  • "Which Deepgram text-to-speech voices are available?"
  • "How much Deepgram credit do I have left?"
  • "What Deepgram credits have I bought?"

What it does

  • list_projects: List the Deepgram projects the key can access with id and name.
  • get_project: Get one Deepgram project by id: name and model-improvement opt-out flag.
  • list_speech_to_text_models: List Deepgram speech-to-text models with architecture, version, languages and whether they support batch and streaming.
  • list_text_to_speech_models: List Deepgram text-to-speech voices and models with architecture, version, languages and accent or age metadata.
  • get_balances: Show the prepaid credit balances of a Deepgram project with amount and units.
  • list_purchases: List credit purchases (orders) of a Deepgram project with amount, units, type and dates.
  • get_usage_breakdown: Show Deepgram usage for a date range: hours, requests, tokens and text-to-speech characters, optionally grouped by endpoint, model, method and more.
  • get_billing_breakdown: Show Deepgram billing in dollars for a date range, optionally grouped by line item, deployment, tags or accessor.
  • list_requests: List recent Deepgram API requests of a project with id, time, path, deployment, HTTP-style status code and API key id. Transcripts are not returned.

BYOK key

You bring your own Deepgram API key (with usage and billing scopes for those tools) (https://console.deepgram.com/). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.deepgram.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Deepgram API (api.deepgram.com) with a BYOK key; documentation: https://developers.deepgram.com/reference/manage/projects/list. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Deepgram. Deepgram and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Deepgram account.

Built for: Worldwide. Languages: English.

Privacy policy

Back to top

Deepgram (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Deepgram (BYOK) is. Deepgram (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Deepgram data: Read your Deepgram projects, models, usage, billing breakdown, balances, purchases and request history with BYOK. You bring your own Deepgram API key (with usage and billing scopes for those tools); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Deepgram call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.deepgram.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Deepgram rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Deepgram receives. The request we make on your behalf, including the key and the arguments, under Deepgram's own terms and privacy policy. Deepgram acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Deepgram gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Deepgram data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Deepgram (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Deepgram at any time to end all access.

Children. Deepgram (BYOK) is a general-audience service operated by the adult using the assistant, under Deepgram's own age rules.

Changes. We will post changes here with a new effective date.

Terms of service

Back to top

Deepgram (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Deepgram (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. Deepgram (BYOK) provides: Read your Deepgram projects, models, usage, billing breakdown, balances, purchases and request history with BYOK. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
  2. Your own key, your own account. You must use your own Deepgram credentials and only access data you are allowed to access. Deepgram's terms apply to your use of Deepgram; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
  3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Deepgram. Deepgram and its logos are trademarks of their owners and are used only to say which service the connector works with.
  4. No advice, no guarantees. Output is the data Deepgram returns, lightly trimmed; it may be incomplete, delayed or changed by Deepgram. Check important facts at the source.
  5. Read-only. The Service does not create, change, send or delete anything in your Deepgram account.
  6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Deepgram's controls, or to attack any system.
  7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Deepgram may change or end its API at any time.
  8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
  9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Deepgram key.
  10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Deepgram takes on your account. Our total liability is limited to US $100.
  11. Governing law. California law; venue in San Mateo County, California.
  12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-deepgram

Deepgram (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Deepgram (BYOK) never asks for them.

Get Deepgram (BYOK)

Free · BYOK · Read-only

BYOK: bring your own keyThis connector uses your own Deepgram API key (with usage and billing scopes for those tools). Create one at https://console.deepgram.com/, with the fewest permissions it needs (read-only if the provider offers it). Your assistant sends it in the X-Upstream-Key header with every request. It is used for that one call only: never stored, logged or cached, and only ever sent to Deepgram. Revoke it at the provider whenever you like. Unofficial connector: not affiliated with Deepgram.