[AI Gateway] Use gateway token for Claude Code; add Bedrock and Vertex docs

[adriandlam]

Summary

Updates the Claude Code setup guide (AI Gateway → Integrations → Coding agents) to authenticate with
the Cloudflare AI Gateway token instead of an Anthropic API key, and adds Amazon Bedrock and Google
Vertex AI setup paths to the same page.

File	Change
integrations/coding-agents/claude-code.mdx	Swap ANTHROPIC_API_KEY for the gateway token; add Bedrock + Vertex sections

What changed

• Anthropic (updated) — ANTHROPIC_API_KEY now holds the Cloudflare gateway token (<CF_AIG_TOKEN>)
  rather than an Anthropic API key
• Amazon Bedrock (new) — routes Claude Code through AI Gateway's Bedrock endpoint using
  CLAUDE_CODE_USE_BEDROCK, ANTHROPIC_BEDROCK_BASE_URL, and CLAUDE_CODE_SKIP_BEDROCK_AUTH. The gateway signs requests with the AWS credentials stored via BYOK
• Google Vertex AI (new) — routes Claude Code through AI Gateway's Vertex endpoint using CLAUDE_CODE_USE_VERTEX, ANTHROPIC_VERTEX_BASE_URL, ANTHROPIC_VERTEX_PROJECT_ID, CLOUD_ML_REGION,
  and CLAUDE_CODE_SKIP_VERTEX_AUTH. The gateway injects the Google Cloud credentials stored via BYOK

Notes

• Each new section provides macOS/Linux and Windows (PowerShell) tabs, matching the existing
  Anthropic section.
• Auth wording for Bedrock/Vertex is backed by the respective provider docs.
• No files were renamed or moved, so no redirects are required.

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.

[cloudflare-docs-bot]

Review

⚠️ 2 warnings found in commit 70ba683.

Code Review

This code review is in beta and may not always be helpful — use your judgment.

Warnings (2)

File	Issue
ai-gateway/integrations/coding-agents/claude-code.mdx line 39	Wrong value for ANTHROPIC_API_KEY — The added step sets ANTHROPIC_API_KEY="<CF_AIG_TOKEN>", but the page prerequisites require an Anthropic API key, the note describes ANTHROPIC_API_KEY as the Anthropic key, and the Anthropic provider docs use apiKey for the Anthropic key and the gateway token only in cf-aig-authorization. Fix: Use the user's Anthropic API key for ANTHROPIC_API_KEY and keep the gateway token only in ANTHROPIC_CUSTOM_HEADERS. If the intent is to use Unified Billing without a provider key, remove the Anthropic API key prerequisite and update the note.
ai-gateway/integrations/coding-agents/claude-code.mdx line 76	Bedrock base URL missing trailing slash — ANTHROPIC_BEDROCK_BASE_URL ends with .../aws-bedrock/bedrock-runtime/<AWS_REGION> without a trailing slash, while the AI Gateway Bedrock docs use .../bedrock-runtime/us-east-1/ and append the model path after the region. SDK URL joining can drop the region if the slash is omitted. Fix: Add a trailing slash after <AWS_REGION> in both the macOS/Linux and Windows Bedrock examples.

Style Guide Review

✅ No style-guide issues found.

Commands

Only codeowners can run commands. Post a comment with the command to trigger it.

Command	Description
/review	Runs a review now. Incremental if a prior review exists, full if not.
/full-review	Re-reviews the entire PR diff from scratch, ignoring incremental history. Useful after a rebase, when you want a fresh review, or if the bot gets out of sync and reports issues that no longer exist.
/ignore-review-limit	Permanently lifts the 2-review automatic limit for this PR. Future pushes will trigger reviews as normal.

[Copilot]

Pull request overview

Updates the AI Gateway “Claude Code” integration guide to route requests through AI Gateway using gateway authentication, and expands the page with setup instructions for routing Claude Code via Amazon Bedrock and Google Vertex AI provider endpoints.

Changes:

• Updates the Anthropic setup commands to use the AI Gateway token in ANTHROPIC_API_KEY and the cf-aig-authorization header.
• Adds a new “Use Amazon Bedrock” section with OS-specific environment variable setup.
• Adds a new “Use Google Vertex AI” section with OS-specific environment variable setup.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[superhighfives]

/bonk review this

[ask-bonk]

This is a useful expansion — adding Bedrock and Vertex paths gives readers more flexibility.

However, the Anthropic section now has significant internal inconsistencies. The code sets ANTHROPIC_API_KEY to the gateway token, but the frontmatter description (line 3), introduction (line 13), prerequisites (line 21), and note (lines 24-26) still describe the old flow where the user provides their own Anthropic API key and Anthropic bills them directly. The note even says 'This configuration does not use BYOK' and 'Anthropic bills you for model usage' — neither of which matches the new token-only setup.

Please either:

• Update the surrounding text to match the new code (remove the Anthropic API key prerequisite, rewrite the note to explain how gateway auth works, and update the description/intro), OR
• Revert ANTHROPIC_API_KEY to the user's Anthropic API key and keep the gateway token only in ANTHROPIC_CUSTOM_HEADERS if that was not the intended change.

Also, the Bedrock base URL examples are missing the trailing slash after <AWS_REGION>. The AI Gateway Bedrock docs show the URL ending with .../bedrock-runtime/<AWS_REGION>/, and omitting the slash can cause path-joining issues.

[ask-bonk]

Done! I submitted a review on PR #31681.

Key findings:

1. Internal inconsistency in Anthropic section — The code now sets ANTHROPIC_API_KEY to the AI Gateway token, but the description, introduction, prerequisites, and note still describe the old flow (user provides their own Anthropic API key, Anthropic bills directly, no BYOK). This is confusing for readers and needs to be resolved by either updating all the surrounding text or reverting the ANTHROPIC_API_KEY change.

2. Bedrock URL missing trailing slash — Both macOS/Linux and Windows examples for the Bedrock base URL omit the trailing / after <AWS_REGION>. The AI Gateway Bedrock docs include it, and skipping it can cause path-joining issues when the client appends the model path.

3. New Bedrock and Vertex sections — These additions are well-structured and match the existing format. No issues there beyond the Bedrock slash.

github run

[adriandlam]

ty @superhighfives! addressed all comments :)