fix: broken links

Author: palashgo

src/content/changelog/ai-gateway/2025-01-07-aig-provider-deepseek.mdx

@@ -6,7 +6,7 @@ products:
 date: 2025-01-02
 ---
 
-[**AI Gateway**](/ai-gateway/) now supports [**DeepSeek**](/ai-gateway/providers/deepseek/), including their cutting-edge DeepSeek-V3 model. With this addition, you have even more flexibility to manage and optimize your AI workloads using AI Gateway. Whether you're leveraging DeepSeek or other providers, like OpenAI, Anthropic, or [Workers AI](/workers-ai/), AI Gateway empowers you to:
+[**AI Gateway**](/ai-gateway/) now supports [**DeepSeek**](/ai-gateway/usage/providers/deepseek/), including their cutting-edge DeepSeek-V3 model. With this addition, you have even more flexibility to manage and optimize your AI workloads using AI Gateway. Whether you're leveraging DeepSeek or other providers, like OpenAI, Anthropic, or [Workers AI](/workers-ai/), AI Gateway empowers you to:
 
 - **Monitor**: Gain actionable insights with analytics and logs.
 - **Control**: Implement caching, rate limiting, and fallbacks.
@@ -31,4 +31,4 @@ curl https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/deepseek/cha
 }'
 ```
 
-For detailed setup instructions, see our [DeepSeek provider documentation](/ai-gateway/providers/deepseek/).
+For detailed setup instructions, see our [DeepSeek provider documentation](/ai-gateway/usage/providers/deepseek/).

src/content/changelog/ai-gateway/2025-01-26-worker-binding-methods.mdx

@@ -16,7 +16,7 @@ With the new AI Gateway binding methods, you can now:
 
 - Send feedback and update metadata with `patchLog`.
 - Retrieve detailed log information using `getLog`.
-- Execute [universal requests](/ai-gateway/universal/) to any AI Gateway provider with `run`.
+- Execute [universal requests](/ai-gateway/usage/universal/) to any AI Gateway provider with `run`.
 
 For example, to send feedback and update metadata using `patchLog`:
 

src/content/changelog/ai-gateway/2025-02-04-aig-provider-cartesia-eleven-cerebras.mdx

@@ -6,15 +6,15 @@ products:
 date: 2025-02-05
 ---
 
-[AI Gateway](/ai-gateway/) has added three new providers: [Cartesia](/ai-gateway/providers/cartesia/), [Cerebras](/ai-gateway/providers/cerebras/), and [ElevenLabs](/ai-gateway/providers/elevenlabs/), giving you more even more options for providers you can use through AI Gateway. Here's a brief overview of each:
+[AI Gateway](/ai-gateway/) has added three new providers: [Cartesia](/ai-gateway/usage/providers/cartesia/), [Cerebras](/ai-gateway/usage/providers/cerebras/), and [ElevenLabs](/ai-gateway/usage/providers/elevenlabs/), giving you more even more options for providers you can use through AI Gateway. Here's a brief overview of each:
 
-- [Cartesia](/ai-gateway/providers/cartesia/) provides text-to-speech models that produce natural-sounding speech with low latency.
-- [Cerebras](/ai-gateway/providers/cerebras/) delivers low-latency AI inference to Meta's Llama 3.1 8B and Llama 3.3 70B models.
-- [ElevenLabs](/ai-gateway/providers/elevenlabs/) offers text-to-speech models with human-like voices in 32 languages.
+- [Cartesia](/ai-gateway/usage/providers/cartesia/) provides text-to-speech models that produce natural-sounding speech with low latency.
+- [Cerebras](/ai-gateway/usage/providers/cerebras/) delivers low-latency AI inference to Meta's Llama 3.1 8B and Llama 3.3 70B models.
+- [ElevenLabs](/ai-gateway/usage/providers/elevenlabs/) offers text-to-speech models with human-like voices in 32 languages.
 
 ![Example of Cerebras log in AI Gateway](~/assets/images/ai-gateway/cerebras2.png)
 
-To get started with AI Gateway, just update the base URL. Here's how you can send a request to [Cerebras](/ai-gateway/providers/cerebras/) using cURL:
+To get started with AI Gateway, just update the base URL. Here's how you can send a request to [Cerebras](/ai-gateway/usage/providers/cerebras/) using cURL:
 
 ```bash title="Example fetch request"
 curl -X POST https://gateway.ai.cloudflare.com/v1/ACCOUNT_TAG/GATEWAY/cerebras/chat/completions \

src/content/changelog/ai-gateway/2025-02-05-aig-request-handling.mdx

@@ -8,7 +8,7 @@ date: 2025-02-06
 
 AI Gateway adds additional ways to handle requests - [Request Timeouts](/ai-gateway/configuration/request-handling/#request-timeouts) and [Request Retries](/ai-gateway/configuration/request-handling/#request-retries), making it easier to keep your applications responsive and reliable.
 
-Timeouts and retries can be used on both the [Universal Endpoint](/ai-gateway/universal/) or directly to a [supported provider](/ai-gateway/providers/).
+Timeouts and retries can be used on both the [Universal Endpoint](/ai-gateway/usage/universal/) or directly to a [supported provider](/ai-gateway/usage/providers/).
 
 **Request timeouts**
 A [request timeout](/ai-gateway/configuration/request-handling/#request-timeouts) allows you to trigger [fallbacks](/ai-gateway/configuration/fallbacks/) or a retry if a provider takes too long to respond.

src/content/changelog/ai-gateway/2025-02-26-guardrails.mdx

@@ -5,7 +5,7 @@ date: 2025-02-26
 preview_image: ~/assets/images/changelog/ai-gateway/guardrails-social-preview.png
 ---
 
-[AI Gateway](/ai-gateway/) now includes [Guardrails](/ai-gateway/guardrails/), to help you monitor your AI apps for harmful or inappropriate content and deploy safely.
+[AI Gateway](/ai-gateway/) now includes [Guardrails](/ai-gateway/features/guardrails/), to help you monitor your AI apps for harmful or inappropriate content and deploy safely.
 
 Within the AI Gateway settings, you can configure:
 
@@ -15,4 +15,4 @@ Within the AI Gateway settings, you can configure:
 
 ![Guardrails in AI Gateway](~/assets/images/ai-gateway/Guardrails.png)
 
-Learn more in the [blog](https://blog.cloudflare.com/guardrails-in-ai-gateway/) or our [documentation](/ai-gateway/guardrails/).
+Learn more in the [blog](https://blog.cloudflare.com/guardrails-in-ai-gateway/) or our [documentation](/ai-gateway/features/guardrails/).

src/content/changelog/ai-gateway/2025-03-20-websockets.mdx

@@ -4,7 +4,7 @@ description: AI Gateway now supports end-to-end, client-to-provider WebSockets
 date: 2025-03-21
 ---
 
-We are excited to announce that [AI Gateway](/ai-gateway/) now supports real-time AI interactions with the new [Realtime WebSockets API](/ai-gateway/websockets-api/realtime-api/).
+We are excited to announce that [AI Gateway](/ai-gateway/) now supports real-time AI interactions with the new [Realtime WebSockets API](/ai-gateway/usage/websockets-api/realtime-api/).
 
 This new capability allows developers to establish persistent, low-latency connections between their applications and AI models, enabling natural, real-time conversational AI experiences, including speech-to-speech interactions.
 
@@ -36,4 +36,4 @@ ws.send(
 );
 ```
 
-Get started by checking out the [Realtime WebSockets API](/ai-gateway/websockets-api/realtime-api/) documentation.
+Get started by checking out the [Realtime WebSockets API](/ai-gateway/usage/websockets-api/realtime-api/) documentation.

src/content/changelog/ai-gateway/2025-06-03-aig-openai-compatible-endpoint.mdx

@@ -6,7 +6,7 @@ products:
 date: 2025-06-03
 ---
 
-Users can now use an [OpenAI Compatible endpoint](/ai-gateway/chat-completion/) in AI Gateway to easily switch between providers, while keeping the exact same request and response formats. We're launching now with the chat completions endpoint, with the embeddings endpoint coming up next.
+Users can now use an [OpenAI Compatible endpoint](/ai-gateway/usage/chat-completion/) in AI Gateway to easily switch between providers, while keeping the exact same request and response formats. We're launching now with the chat completions endpoint, with the embeddings endpoint coming up next.
 
 To get started, use the OpenAI compatible chat completions endpoint URL with your own account id and gateway id and switch between providers by changing the `model` and `apiKey` parameters.
 
@@ -26,6 +26,6 @@ const response = await client.chat.completions.create({
 console.log(response.choices[0].message.content);
 ```
 
-Additionally, the [OpenAI Compatible endpoint](/ai-gateway/chat-completion/) can be combined with our [Universal Endpoint](/ai-gateway/universal/) to add fallbacks across multiple providers. That means AI Gateway will return every response in the same standardized format, no extra parsing logic required!
+Additionally, the [OpenAI Compatible endpoint](/ai-gateway/usage/chat-completion/) can be combined with our [Universal Endpoint](/ai-gateway/usage/universal/) to add fallbacks across multiple providers. That means AI Gateway will return every response in the same standardized format, no extra parsing logic required!
 
-Learn more in the [OpenAI Compatibility](/ai-gateway/chat-completion/) documentation.
+Learn more in the [OpenAI Compatibility](/ai-gateway/usage/chat-completion/) documentation.

src/content/changelog/workers-ai/2025-02-25-json-mode.mdx

@@ -37,7 +37,7 @@ export default {
 		const client = new OpenAI({
 			apiKey: env.OPENAI_API_KEY,
 			// Optional: use AI Gateway to bring logs, evals & caching to your AI requests
-			// https://developers.cloudflare.com/ai-gateway/providers/openai/
+			// https://developers.cloudflare.com/ai-gateway/usage/providers/openai/
 			// baseUrl: "https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}/openai"
 		});
 

src/content/docs/agents/api-reference/using-ai-models.mdx

@@ -143,7 +143,7 @@ binding = "AI"
 
 ### Model routing
 
-You can also use the model routing features in [AI Gateway](/ai-gateway/) directly from an Agent by specifying a [`gateway` configuration](/ai-gateway/providers/workersai/) when calling the AI binding.
+You can also use the model routing features in [AI Gateway](/ai-gateway/) directly from an Agent by specifying a [`gateway` configuration](/ai-gateway/usage/providers/workersai/) when calling the AI binding.
 
 :::note
 

src/content/docs/ai-gateway/configuration/request-handling.mdx

@@ -34,7 +34,7 @@ A timeout is set in milliseconds. Additionally, the timeout is based on when the
 
 #### Universal Endpoint
 
-If set on a [Universal Endpoint](/ai-gateway/universal/), a request timeout specifies the timeout duration for requests and triggers a fallback.
+If set on a [Universal Endpoint](/ai-gateway/usage/universal/), a request timeout specifies the timeout duration for requests and triggers a fallback.
 
 For a Universal Endpoint, configure the timeout value by setting a `requestTimeout` property within the provider-specific `config` object. Each provider can have a different `requestTimeout` value for granular customization.
 
@@ -93,7 +93,7 @@ curl 'https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}' \
 
 #### Direct provider
 
-If set on a [provider](/ai-gateway/providers/) request, request timeout specifies the timeout duration for a request and - if exceeded - returns an error.
+If set on a [provider](/ai-gateway/usage/providers/) request, request timeout specifies the timeout duration for a request and - if exceeded - returns an error.
 
 For a provider-specific endpoint, configure the timeout value by adding a `cf-aig-request-timeout` header.
 
@@ -129,7 +129,7 @@ On the final retry attempt, your gateway will wait until the request completes,
 
 #### Universal endpoint
 
-If set on a [Universal Endpoint](/ai-gateway/universal/), a request retry will automatically retry failed requests up to five times before triggering any configured fallbacks.
+If set on a [Universal Endpoint](/ai-gateway/usage/universal/), a request retry will automatically retry failed requests up to five times before triggering any configured fallbacks.
 
 For a Universal Endpoint, configure the retry settings with the following properties in the provider-specific `config`:
 
@@ -202,7 +202,7 @@ curl 'https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}' \
 
 #### Direct provider
 
-If set on a [provider](/ai-gateway/universal/) request, a request retry will automatically retry failed requests up to five times. On the final retry attempt, your gateway will wait until the request completes, regardless of how long it takes.
+If set on a [provider](/ai-gateway/usage/universal/) request, a request retry will automatically retry failed requests up to five times. On the final retry attempt, your gateway will wait until the request completes, regardless of how long it takes.
 
 For a provider-specific endpoint, configure the retry settings by adding different header values: