fix: Resolve PR #616 review comments - update links to Model Catalog

- Fix SDK docs (c-sharp.mdx, node.mdx) to link to /product/model-catalog instead of /product/ai-gateway/virtual-keys
- Update changelog apr.mdx to link to integrations page for provider access permissions

Author: roh26it

api-reference/sdk/c-sharp.mdx

@@ -170,7 +170,7 @@ Console.WriteLine(response.Value.Content[0].Text);
 ```
 
 <Tip>
-Add providers in the [Model Catalog](/product/ai-gateway/virtual-keys) to get a provider slug (e.g., `@openai-prod`). The legacy `x-portkey-virtual-key` header is still supported.
+Add providers in the [Model Catalog](/product/model-catalog) to get a provider slug (e.g., `@openai-prod`). The legacy `x-portkey-virtual-key` header is still supported.
 </Tip>
 </Tab>
 

api-reference/sdk/node.mdx

@@ -63,14 +63,14 @@ const response = await portkey.chat.completions.create({
 console.log(response.choices[0].message.content);
 ```
 
-<Info>Add providers in the [Model Catalog](/product/ai-gateway/virtual-keys) to get a provider slug (e.g., `@openai-prod`). You can also use a [Config](/api-reference/inference-api/config-object) for advanced routing.</Info>
+<Info>Add providers in the [Model Catalog](/product/model-catalog) to get a provider slug (e.g., `@openai-prod`). You can also use a [Config](/api-reference/inference-api/config-object) for advanced routing.</Info>
 
 ## Authentication & Configuration
 
 The SDK requires:
 - **Portkey API Key**: Your Portkey API key (env var `PORTKEY_API_KEY` recommended)
 - **Provider Authentication**:
-  - **Provider Slug**: Add a provider in [Model Catalog](/product/ai-gateway/virtual-keys) and use its slug (recommended)
+  - **Provider Slug**: Add a provider in [Model Catalog](/product/model-catalog) and use its slug (recommended)
   - **Config**: The [Config object](/api-reference/inference-api/config-object) or config slug for advanced routing
   - **Provider Slug + Auth Headers**: Useful if you do not want to save your API keys to Portkey and make direct requests.
 

changelog/2025/apr.mdx

@@ -189,7 +189,7 @@ Access audio models via Groq
 
 We've made significant improvements to our documentation:
 
-- **Provider access permissions**:  Defining who can view and manage providers within workspaces. [Learn more](https://portkey.ai/docs/product/administration/configure-virtual-key-access-permissions)
+- **Provider access permissions**:  Defining who can view and manage providers within workspaces. [Learn more](https://portkey.ai/docs/product/model-catalog/integrations)
 - **API keys access**: Control how workspace managers and members interact with API keys within their workspaces. [Learn more](https://portkey.ai/docs/product/administration/configure-api-key-access-permissions)