fix(anthropic): pdf-native-providers reuses resolveAnthropicMessagesUrl

sunapi386 · sunapi386 · commit 33b444d7c8d5 · 2026-04-29T11:13:58.000-04:00
Greptile flagged two issues with the inline URL build:

P1 (real bug): the chain used `??` instead of `||`, so a whitespace-only
ANTHROPIC_BASE_URL trimmed to "" passed nullish-checks and produced a
relative `/v1/messages` URL that fetch() can't resolve.

P2 (pre-existing): the inline path always appended `/v1/messages`, so a
proxy URL ending in `/v1` (common with LiteLLM) would hit `/v1/v1/messages`.

Both fixed by reusing the canonical resolveAnthropicMessagesUrl helper —
single precedence chain, single `/v1` suffix logic, no duplication.
diff --git a/src/agents/tools/pdf-native-providers.ts b/src/agents/tools/pdf-native-providers.ts
@@ -6,6 +6,7 @@
 import { normalizeProviderTransportWithPlugin } from "../../plugins/provider-runtime.js";
 import { isRecord } from "../../utils.js";
 import { normalizeSecretInput } from "../../utils/normalize-secret-input.js";
+import { resolveAnthropicMessagesUrl } from "../anthropic-transport-stream.js";
 
 type PdfInput = {
   base64: string;
@@ -62,12 +63,8 @@ export async function anthropicAnalyzePdf(params: {
   }
   content.push({ type: "text", text: params.prompt });
 
-  const baseUrl = (
-    params.baseUrl ??
-    process.env.ANTHROPIC_BASE_URL?.trim() ??
-    "https://api.anthropic.com"
-  ).replace(/\/+$/, "");
-  const res = await fetch(`${baseUrl}/v1/messages`, {
+  const url = resolveAnthropicMessagesUrl(params.baseUrl);
+  const res = await fetch(url, {
     method: "POST",
     headers: {
       "Content-Type": "application/json",
