Skip to content

[AI Gateway] Clarify BYOK authorization headers - #33520

Draft
Michael-WhiteCapData wants to merge 1 commit into
cloudflare:productionfrom
Michael-WhiteCapData:docs/clarify-ai-gateway-byok-auth
Draft

Michael-WhiteCapData wants to merge 1 commit into
cloudflare:productionfrom
Michael-WhiteCapData:docs/clarify-ai-gateway-byok-auth

Conversation

@Michael-WhiteCapData

Copy link
Copy Markdown

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 Authorization and uses cf-aig-authorization for the gateway.

Fixes #33517.

Documentation checklist

  • The change adheres to the documentation style guide.
  • If a larger change - such as adding a new page- an issue has been opened in relation to any incorrect or out of date information that this PR fixes.

@github-actions github-actions Bot added size/s product:ai-gateway AI Gateway: https://developers.cloudflare.com/ai-gateway/ labels Sep 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

product:ai-gateway AI Gateway: https://developers.cloudflare.com/ai-gateway/ size/s

Projects

None yet

Development

Successfully merging this pull request may close these issues.

AI Gateway BYOK docs: unclear that any Authorization header (even a placeholder) bypasses key injection; DeepSeek provider page missing BYOK example

1 participant