From 831445ad78f03197a108e5074afff71448d18f12 Mon Sep 17 00:00:00 2001 From: Ram Sharma Date: Wed, 18 Dec 2024 02:26:25 -0800 Subject: [PATCH] Update assistant-setup-inbound.mdx (#105) [Docs] small fix - fix broken link to provider keys --- .../snippets/quickstart/dashboard/assistant-setup-inbound.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fern/snippets/quickstart/dashboard/assistant-setup-inbound.mdx b/fern/snippets/quickstart/dashboard/assistant-setup-inbound.mdx index 62526a0..b444737 100644 --- a/fern/snippets/quickstart/dashboard/assistant-setup-inbound.mdx +++ b/fern/snippets/quickstart/dashboard/assistant-setup-inbound.mdx @@ -55,14 +55,14 @@ - Before we proceed, we can set our [provider key](customization/provider-keys) for OpenAI (this is just your OpenAI secret key). + Before we proceed, we can set our [provider key](https://docs.vapi.ai/customization/provider-keys) for OpenAI (this is just your OpenAI secret key). You can see all of your provider keys in the "Provider Keys" dashboard tab. You can also go directly to [dashboard.vapi.ai/keys](https://dashboard.vapi.ai/keys). - Vapi uses [provider keys](customization/provider-keys) you provide to communicate with LLM, TTS, & STT vendors on your behalf. It is most ideal that we set keys for the vendors we intend to use ahead of time. + Vapi uses [provider keys](https://docs.vapi.ai/customization/provider-keys) you provide to communicate with LLM, TTS, & STT vendors on your behalf. It is most ideal that we set keys for the vendors we intend to use ahead of time.