Clarification Required on Call Cost and Speech-to-Text (STT) Billing Structure
I am writing to seek urgent clarification regarding the cost breakdown in my recent call usage, as I am facing confusion with your pricing system, specifically concerning the Speech-to-Text (STT) component.
have noted the standard call cost, which I understand to be $0.05 per minute.
However, I have also observed a separate charge for STT (Speech-to-Text) within the VAPI call cost breakdown. This is confusing for me because I am under the impression that the STT service is handled by my own configured external provider.
Specifically:
My current configuration utilizes an Azure Transcriber connected via my own API key.
Therefore, I anticipate that all Speech-to-Text processing costs should be billed directly to my Azure account, not through VAPI.
I urgently request clarification on the following points:
Why is the STT charge being deducted on the VAPI side when I am using a self-managed external transcriber (Azure)?
Is it possible that VAPI is providing and charging for a separate, default STT service, even when an external API key is configured?
Could you please confirm the exact service or process that is incurring this specific STT charge in my usage report?
Thank you for your prompt attention to this matter and for clarifying the billing details, especially concerning the unexpected STT charge.
have noted the standard call cost, which I understand to be $0.05 per minute.
However, I have also observed a separate charge for STT (Speech-to-Text) within the VAPI call cost breakdown. This is confusing for me because I am under the impression that the STT service is handled by my own configured external provider.
Specifically:
My current configuration utilizes an Azure Transcriber connected via my own API key.
Therefore, I anticipate that all Speech-to-Text processing costs should be billed directly to my Azure account, not through VAPI.
I urgently request clarification on the following points:
Why is the STT charge being deducted on the VAPI side when I am using a self-managed external transcriber (Azure)?
Is it possible that VAPI is providing and charging for a separate, default STT service, even when an external API key is configured?
Could you please confirm the exact service or process that is incurring this specific STT charge in my usage report?
Thank you for your prompt attention to this matter and for clarifying the billing details, especially concerning the unexpected STT charge.
