Skip to content

Commit d22193e

Browse files
URL added
1 parent 1a23fdd commit d22193e

File tree

1 file changed

+4
-5
lines changed

1 file changed

+4
-5
lines changed

src/content/docs/ai-gateway/configuration/fallbacks.mdx

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -3,10 +3,9 @@ pcx_content_type: configuration
33
title: Fallbacks
44
sidebar:
55
order: 2
6-
76
---
87

9-
import { Render } from "~/components"
8+
import { Render } from "~/components";
109

1110
Specify model or provider fallback with your [Universal endpoint](/ai-gateway/providers/universal/) to specify what to do if a request fails.
1211

@@ -25,15 +24,15 @@ graph TD
2524
D --> E[Return Response]
2625
```
2726

28-
<br/>
27+
<br />
2928

3029
You can add as many fallbacks as you need, just by adding another object in the array.
3130

3231
<Render file="universal-gateway-example" />
3332

34-
## Response Header(cf-aig-step)
33+
## Response header(cf-aig-step)
3534

36-
When using the Universal Endpoint 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.
35+
When using the [Universal Endpoint](ai-gateway/providers/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.
3736

3837
- `cf-aig-step:0` – The first (primary) model was used successfully.
3938
- `cf-aig-step:1` – The request fell back to the second model.

0 commit comments

Comments
 (0)