Why does key creation or balance access return 403?

Ask an existing administrator to check the project and setup credentials, then confirm the new key has only billing:read. Ordinary member or voice-call access is not financial read access. Do not upgrade the monitoring key to admin/owner or submit the temporary management key.

What causes 401, 404 or a Project ID mismatch?

Check expiry, revocation and whether the key's creator still belongs to the project. The ID and key must belong to the same Deepgram project. Paste the whole secret without Token; a Quota Monitor project ID, API Key ID, Cookie or temporary voice JWT is not a substitute.

Why total several balances instead of using the first or monthly spend?

A project can return several balances. We sum every distinct USD amount exactly, without estimating from spend: 20 + 4.5 displays $24.5. We do not infer cash/promotional categories, eligibility or expiry, and do not combine different projects.

What if the list is empty, units differ or the console disagrees?

Empty lists, duplicate IDs, non-USD entries, missing values and error responses fail the entire read. No partial total or zero is invented. Check the project and last successful time; old snapshots are retained. Verify official posting and contract restrictions, and report only redacted errors and times.

What about 429, sync failures or regional requirements?

Retry later after 429; do not repeatedly refresh. We use only the global api.deepgram.com management endpoint and make no regional-residency guarantee. If your organization prohibits that destination, do not submit credentials. Top-ups, voice calls and permission changes are outside monitoring.

Deepgram Balance: Check Credits & Set Up a Read-Only API Key

Awaiting live-account verification

Guide updated 2026-10-11

Implemented from official balance and permission references; live-account verification is pending. Signed-in setup, scoped-key access, console navigation and balance reconciliation have not been tested. Automated tests are not live verification.

Required credentials: Deepgram API Key
Monitoring currency: USD · US dollars
What is monitored: Deepgram project credit balance; The exact sum of all distinct balance_id entries' USD amount values from GET https://api.deepgram.com/v1/projects/{project_id}/balances. No usage estimate. Funds are shared by keys and voice services within that Deepgram project, not a separate Quota Monitor project wallet.

How to check your Deepgram balance manually

Sign in to Deepgram Console and select the paying project in Projects at the top left.
Open that project's Billing and read USD Credits, not monthly spending, unit prices or another project's promotion.
If necessary, purchase directly on Deepgram and confirm posting. Check other projects separately and do not count the same wallet once per key.

Open official Deepgram page

Connect Deepgram to Quota Monitor

1. Select the Deepgram project that pays for your app
Sign in to Deepgram Console. Use Projects at the top left to select the project running your voice application, then review its Billing balance. You do not need a new Deepgram project for monitoring.
Check: project name and USD Credits match. These funds belong to that Deepgram project, not every project in the account. Signed-in navigation still needs live verification.
Open official Deepgram page(opens in a new tab)
2. Have an existing administrator prepare setup access
An existing administrator of that project should perform setup. If no approved management credential is available, open Settings → API Keys → Create a New API Key. Name it Quota Monitor setup, choose Admin under Permissions and a short Expiration, then Create Key. Save the one-time secret and select Got it.
Check: this temporary Admin key stays in your local setup tools. It has broad permissions: never submit it to Quota Monitor, an agent or an online request-testing site. Ask an existing administrator rather than elevating your role; leave application keys unchanged.
Open official Deepgram page(opens in a new tab)
3. Find the exact Project ID
Copy Project ID if the console shows it. Otherwise use a local HTTP client with cloud sync and request logging disabled: create a GET request to https://api.deepgram.com/v1/projects, add Authorization with Token followed by one space and the management key, and leave the body empty.
Check: match the target name in the returned projects array and copy its project_id. Ask the administrator to resolve duplicate names; do not pick the first item blindly. This is not a Quota Monitor project ID or API Key ID. This setup-only lookup does not add project:read to the monitoring key.
Open official Deepgram page(opens in a new tab)
04
4. Create a dedicated billing:read key
In that local client, create a POST request to https://api.deepgram.com/v1/projects/PROJECT_ID/keys, replacing PROJECT_ID. Keep the management key in the Token Authorization header and set Content-Type to application/json. Choose a raw JSON body, paste the snippet below and send once.
Check: the successful response has a new key and scopes containing only billing:read. Do not copy usage:write/keys:write from a generic example or add admin/owner. Store the new secret in a password manager. This least-privilege flow awaits live verification; if denied, investigate with your administrator rather than substituting the management key.
Read-only key creation JSON body
```
{
  "comment": "Quota Monitor",
  "scopes": ["billing:read"]
}
```
Copies the complete JSON without keys or account details.
Open official Deepgram page(opens in a new tab)
5. Test read access and remove the temporary Admin key
Create GET https://api.deepgram.com/v1/projects/PROJECT_ID/balances with no body. Replace Authorization with Token followed by the new billing:read key. Check that balances contains balance_id, amount and USD (or usd) units for each entry.
Check: after the new key works, delete only Quota Monitor setup in Settings → API Keys and clear the old credential from local requests. Do not delete application keys. An empty list or 403 is not evidence of zero funds; use the troubleshooting below.
Open official Deepgram page(opens in a new tab)
6. Add Deepgram inside your Quota Monitor project
Open your project → add provider connection → add new connection. Select Deepgram (USD), give it a recognizable name, enter the target Deepgram Project ID and the dedicated read-only Deepgram API Key, then save.
Check: paste just the secret, without Token/Bearer, quotes or line breaks. Both fields are masked and encrypted together; only the key suffix is displayed. No custom URL or extra filter is needed. For MCP, use the secure entry link, not an agent message.
7. Sync and reconcile the USD balance
Wait for first sync or select Query latest balance. Check the new successful timestamp and compare Billing in the same Deepgram project. Two amount entries of 20 and 4.5 USD should display $24.5, not $0.245.
Check: project, currency and query time match. Multiple Quota Monitor projects can share the same Deepgram funds; do not add duplicates. If values differ, report only redacted amounts, errors and time—not keys, full IDs, purchase orders or raw responses.
Open official Deepgram page(opens in a new tab)
8. Add funds on Deepgram when needed
Select Open provider on the card. Re-select the correct Deepgram project and open Billing; an authorized payer can review and complete the official purchase flow or contact the contract administrator.
Check: the payment has posted before syncing again. Connecting monitoring does not require a purchase or automatic payments. Promotional or contract Credits can have restrictions; verify these on Deepgram instead of treating the balance as a full availability guarantee.
Open official Deepgram page(opens in a new tab)
9. Replace or revoke the monitoring key
Create a replacement billing:read key as above, add a replacement connection and verify it. Remove project references to the old connection, delete it, then select the old dedicated key's trash icon in the Deepgram project's Settings → API Keys.
Check: revoke only the monitoring key, not application keys. Deleting a connection here does not revoke its Deepgram key. Removing a key's creator from the project can invalidate it. Track expiry and rotate as needed; plan a replacement window if connection slots are full.
Open official Deepgram page(opens in a new tab)

What Quota Monitor reads from Deepgram

Uses only the global management endpoint api.deepgram.com, with no custom URL or regional fallback. Do not connect if credentials or billing metadata must stay in a particular region. No audio or transcripts are uploaded.
Cash, promotional eligibility, contract restrictions and expiry are not split out. Book Credits are not withdrawable cash or proof of access to every voice service, model or post-paid credit line. Never sum duplicate wallets for the same upstream project.
Values are already USD: no division by 100 or repeated cost deduction. Explicit zero and negatives are kept. Empty lists, missing fields, duplicate balance IDs, non-USD units and errors fail the whole read rather than publishing zero or a partial total.
The amount is the last successful official query, not a zero-delay billing guarantee. Quota Monitor never creates upstream keys, invokes voice services, buys Credits or changes payment settings. The one-time key creation below is performed by you or your existing administrator.
The dashboard shows the latest successful snapshot. Manual refresh queries the provider again but cannot eliminate upstream billing delays. An old balance is not a new result after a failed query.

Deepgram FAQ and troubleshooting

Why does key creation or balance access return 403?: Ask an existing administrator to check the project and setup credentials, then confirm the new key has only billing:read. Ordinary member or voice-call access is not financial read access. Do not upgrade the monitoring key to admin/owner or submit the temporary management key.
What causes 401, 404 or a Project ID mismatch?: Check expiry, revocation and whether the key's creator still belongs to the project. The ID and key must belong to the same Deepgram project. Paste the whole secret without Token; a Quota Monitor project ID, API Key ID, Cookie or temporary voice JWT is not a substitute.
Why total several balances instead of using the first or monthly spend?: A project can return several balances. We sum every distinct USD amount exactly, without estimating from spend: 20 + 4.5 displays $24.5. We do not infer cash/promotional categories, eligibility or expiry, and do not combine different projects.
What if the list is empty, units differ or the console disagrees?: Empty lists, duplicate IDs, non-USD entries, missing values and error responses fail the entire read. No partial total or zero is invented. Check the project and last successful time; old snapshots are retained. Verify official posting and contract restrictions, and report only redacted errors and times.
What about 429, sync failures or regional requirements?: Retry later after 429; do not repeatedly refresh. We use only the global api.deepgram.com management endpoint and make no regional-residency guarantee. If your organization prohibits that destination, do not submit credentials. Top-ups, voice calls and permission changes are outside monitoring.

Official Deepgram references

Prepared by Quota Monitor, not an official provider tutorial. Interfaces and permissions may change; check official pages. Verification is limited to the scope stated here.