[AI Gateway] Clarify BYOK authorization headers - #33520
superhighfives merged 2 commits into
Conversation
|
@Michael-WhiteCapData This draft pull request has had no activity for 3 days. It will close after 7 days of inactivity. Transition to ready for review if ready. A codeowner can comment |
Review✅ No issues found in commit Code ReviewThis code review is in beta and may not always be helpful — use your judgment. No code review issues found. ConventionsNo convention issues found. Style Guide ReviewNo style-guide issues found. CommandsOnly codeowners can run commands. Post a comment with the command to trigger it.
|
|
Thanks for taking the time to contribute this, @Michael-WhiteCapData. The information looks great, and super useful. I'd love to get this information incorporated into the article, rather than where it's currently sitting at the bottom. Happy to take this over, unless you wanted to take a pass? |
|
Thanks! I took a pass and incorporated the header behavior directly into the Update your applications instructions, then removed the separate callout. The DeepSeek BYOK request remains alongside the other provider examples. The documentation checks and full local build pass. |
Summary
Clarifies that AI Gateway substitutes a stored provider key only when the provider authorization header is absent. Adds a DeepSeek BYOK request example that omits
Authorizationand usescf-aig-authorizationfor the gateway.Fixes #33517.
Documentation checklist