Allowing customers to create their own accounts and integrate them with third party apps

[DrifterAtSea]

Currently I am building a voice agent and will need to create one key per customer. But this solution means that I end up paying the bill for all the customers. A better solution is to let my customers sign up directly with Deepgram and simply authorize apps to use their account. This way, the customer pays for their own account directly and uses as much as they want. At the same time, they can share their account with diverse apps allowing them to have better control over how much of Deepgram's services they use. They can always switch from one app to a competing app if they find a better one that is cheaper, provided the third party app allows them to also obtain access to the customer's Deepgram account.

This approach is totally in line with how Google allows third party apps to gain access to a customer's account. A customer can authorize an app to have access to Google Drive files or other services.

By offloading the cost of the Voice Agent to the customer, the third party app can focus on providing a cost for their app that is not dependent on the cost of an LLM or voice agent or even how these service charge. For example, an app could charge the customer a fixed recurring subscription fee to use their app. The customer would end up paying this fee plus the amount they owe Deepgram. But the third party app isn't responsible for handling the charges for Deepgram's usage. That usage goes straight to the customer's credit card on Deepgram's service.

Without this model, third party apps are required to pay a usage fee and cannot support a subscription fee because some customers will end up using Deepgram a lot while others will use it as little as possible (because they have a lower budget). So having fixed subscription fees to cover this broad range of usage doesn't make sense.

[deepgram-community[bot]]

Thanks for asking your question. Please be sure to reply with as much detail as possible so the community can assist you efficiently.
_{Consider joining our Discord community for more opportunity to engage with your fellow Deepgram users. You can earn points which can be redeemed for cool stuff by being active in our communities!}

[deepgram-community[bot]]

Hey there! It looks like you haven't connected your GitHub account to your Deepgram account. You can do this at https://community.deepgram.com - being verified through this process will allow our team to help you in a much more streamlined fashion.

[deepgram-community[bot]]

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?

• The programming language you are working in (e.g. JavaScript, Python).
• The deepgram product you are using (e.g Speech to Text, Agent API)
• A request ID that triggered your error or issue.

[lukeocodes]

This appears to be a request for us to offer an OIDC implementation so users can identify their Deepgram account and authorize your app's access to their account so that billing occurs to your users directly

I do not believe this is on our roadmap. But, we do offer the ability for you to create multiple API keys on a single project, so that you can encapsulate usage by customer and pass on the costs to them. This is generally how other clients have tackled this problem

[DrifterAtSea]

The only reason others tackle the problem this way is because that is all you are offering them, which is very limited.

[deepgram-community[bot]]

Thanks for the feedback

This message was sent by luke from Deepgram, via our community automation.