docs: update AI Gateway docs to reflect Unified Billing support #232
+5
−5
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Remove outdated info about needing a provider API key - Clarify that Unified Billing allows using providers without separate API keys - Update secrets reference table
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
CLOUDFLARE_AI_GATEWAY_API_KEYis the AI Gateway authentication token for Unified BillingContext
The current docs state "You still need a provider API key (e.g., your Anthropic API key) — the gateway forwards it to the upstream provider." This is no longer accurate with Unified Billing, which allows using Anthropic, OpenAI, and other providers directly through AI Gateway without needing separate provider API keys.