invalid links

Author: daisyfaithauma

public/__redirects

@@ -128,7 +128,7 @@
 /ai-gateway/integration/aig-workers-ai-binding/ /ai-gateway/integrations/aig-workers-ai-binding/ 301
 /ai-gateway/integration/ /ai-gateway/integrations/ 301
 /ai-gateway/providers/open-router/ /ai-gateway/providers/openrouter/ 301
-/ai-gateway/providers/universal/ /ai-gateway/universal/ 301
+/ai-gateway/providers/universal/ /ai-gateway/universal-endpoint/universal/ 301
 
 # agents
 /agents/capabilities/mcp-server/ /agents/model-context-protocol/ 301

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/universal-endpoint/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-05-aig-request-handling.mdx

@@ -8,7 +8,7 @@ date: 2025-02-06T11:00:00Z
 
 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/universal-endpoint/universal/) or directly to a [supported provider](/ai-gateway/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/docs/ai-gateway/configuration/fallbacks.mdx

@@ -7,7 +7,7 @@ sidebar:
 
 import { Render } from "~/components";
 
-Specify model or provider fallbacks with your [Universal endpoint](/ai-gateway/universal/) to handle request failures and ensure reliability.
+Specify model or provider fallbacks with your [Universal endpoint](/ai-gateway/universal-endpoint/universal/) to handle request failures and ensure reliability.
 
 Cloudflare can trigger your fallback provider in response to [request errors](#request-failures) or [predetermined request timeouts](/ai-gateway/configuration/request-handling#request-timeouts). The [response header `cf-aig-step`](#response-headercf-aig-step) indicates which step successfully processed the request.
 
@@ -38,7 +38,7 @@ You can add as many fallbacks as you need, just by adding another object in the
 
 ## Response header(cf-aig-step)
 
-When using the [Universal endpoint](/ai-gateway/universal/) with fallbacks, the response header `cf-aig-step` indicates which model successfully processed the request by returning the step number. This header provides visibility into whether a fallback was triggered and which model ultimately processed the response.
+When using the [Universal endpoint](/ai-gateway/universal-endpoint/universal/) with fallbacks, the response header `cf-aig-step` indicates which model successfully processed the request by returning the step number. This header provides visibility into whether a fallback was triggered and which model ultimately processed the response.
 
 - `cf-aig-step:0` – The first (primary) model was used successfully.
 - `cf-aig-step:1` – The request fell back to the second model.

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

@@ -123,7 +123,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/universal-endpoint/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`:
 
@@ -196,7 +196,7 @@ curl 'https://gateway.ai.cloudflare.com/v1/{account_id}/{gateway_id}' \
 
 #### Direct provider
 
-If set on a [provider](/ai-gateway/providers/) 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/universal-endpoint/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:
 

src/content/docs/ai-gateway/integrations/worker-binding-methods.mdx

@@ -148,7 +148,7 @@ const anthropic = createAnthropic({
 
 The `run` method allows you to execute universal requests. Users can pass either a single universal request object or an array of them. This method supports all AI Gateway providers.
 
-Refer to the [Universal endpoint documentation](/ai-gateway/universal/) for details about the available inputs.
+Refer to the [Universal endpoint documentation](/ai-gateway/universal-endpoint/universal/) for details about the available inputs.
 
 ```typescript
 const resp = await gateway.run({
@@ -164,7 +164,7 @@ const resp = await gateway.run({
 ```
 
 - **Returns**: `Promise<Response>`
-- **Example Use Case**: Perform a [universal request](/ai-gateway/universal/) to any supported provider.
+- **Example Use Case**: Perform a [universal request](/ai-gateway/universal-endpoint/universal/) to any supported provider.
 
 ## Conclusion