Deepgram
Urgent: Unclear Charges, Tariff Mismatch, and Request for Full Review & Refund (Project ID: 21035f03-f8a7-45fc-b99c-6fc7f80f8cce) #1522
Replies: 4 comments 1 reply
-
|
Thanks for asking your question. Please be sure to reply with as much detail as possible so the community can assist you efficiently. |
Beta Was this translation helpful? Give feedback.
-
|
It looks like we're missing some important information to help debug your issue. Would you mind providing us with the following details in a reply?
|
Beta Was this translation helpful? Give feedback.
-
|
It is not related to programming language |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Hi, I'm from Deepgram's console team. You had 2 big requests that contributed to this charge on top of a few smaller requests.
Why were these billed on 1/26 if the requests happened on 1/22 and 1/25 respectively? First these requests needed to complete (in both cases they started on one day and finished on another). Then, after a request is completed, we process the usage and bill you for it some time after your request completes. The billing time is what is reflected in the spend charts, where as you will see the time the request was made in the logs. So although you were billed on 1/26 this is for usage on previous days. In the console links above you should be able to see the cost per request as well as other metadata associated with the request, maybe this will help you investigate any business logic changes you ant to make. Deepgram charges by websocket duration for agent requests so it is important to close connections when not in use. If you have any other connections in progress I would recommend closing them now to avoid any additional unexpected charges.
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello Deepgram Support Team,
I am writing to raise a serious billing concern regarding my Deepgram project.
Project ID: 21035f03-f8a7-45fc-b99c-6fc7f80f8cce
Date of charges: January 26, 2026
Charged amount: ~$500 USD
Issue Summary
According to your dashboard, I was charged approximately $500 USD for Voice Agent (Standard LLM / DG TTS) usage in a single day.
However:
Our internal logs clearly show only 7 completed calls
There is no traffic volume that could reasonably justify this charge
The effective rate applied does not match the published pricing
There is no transparent breakdown explaining how this amount was calculated
At the moment, it is completely unclear what exactly was billed:
No per-call cost
No duration-based explanation
No LLM / TTS / agent-session separation
No correlation with actual usage
Why this is critical
This is not the first time we experience unexplained charges of this nature.
Such billing behavior makes it impossible to:
Trust cost predictability
Accurately estimate operational expenses
Safely run production workloads
What I am requesting
A full billing and technical review of the project
A detailed charge breakdown, including:
Per-call duration
Voice Agent session lifecycle
LLM usage
TTS usage
Any background / idle / session-based billing
An explanation of why the charged rates do not match the stated tariffs
A full refund of the charged amount, as the billing does not correspond to actual usage
Confirmation of how such charges can be prevented in the future
Additional notes
The logs show normal behavior and a very small number of calls
No load testing or high-volume scenarios were executed
No abnormal retries or looping behavior on our side
Please treat this issue as urgent.
Until this is resolved, continuing to use Deepgram in production is not viable for us.
I expect a detailed explanation and resolution, including the refund, as soon as possible.
Kind regards,
Ruslan Vaskevych
Beta Was this translation helpful? Give feedback.
All reactions