From c452be194976ff9776a36203e777a83770ded3f5 Mon Sep 17 00:00:00 2001 From: Bryce Bjork Date: Thu, 25 Jun 2026 20:22:23 -0400 Subject: [PATCH] feat(setup): honor AI_GATEWAY_BASE_URL when validating the gateway key validateGatewayApiKey built an @ai-sdk/gateway provider with no baseURL, so it always hit ai-gateway.vercel.sh. Forward AI_GATEWAY_BASE_URL to createGateway so the key check can target a self-hosted or proxied gateway. No behavior change when the variable is unset. Co-Authored-By: Claude Opus 4.8 (1M context) --- .changeset/gateway-base-url-env.md | 5 +++++ packages/eve/src/setup/validate-gateway-key.ts | 1 + 2 files changed, 6 insertions(+) create mode 100644 .changeset/gateway-base-url-env.md diff --git a/.changeset/gateway-base-url-env.md b/.changeset/gateway-base-url-env.md new file mode 100644 index 000000000..745eef78d --- /dev/null +++ b/.changeset/gateway-base-url-env.md @@ -0,0 +1,5 @@ +--- +"eve": patch +--- + +`validateGatewayApiKey` now honors the `AI_GATEWAY_BASE_URL` environment variable when constructing the gateway provider, so the `AI_GATEWAY_API_KEY` check can be pointed at a self-hosted or proxied AI Gateway instead of always hitting `ai-gateway.vercel.sh`. diff --git a/packages/eve/src/setup/validate-gateway-key.ts b/packages/eve/src/setup/validate-gateway-key.ts index a7c856ee3..10e5d71db 100644 --- a/packages/eve/src/setup/validate-gateway-key.ts +++ b/packages/eve/src/setup/validate-gateway-key.ts @@ -54,6 +54,7 @@ export async function validateGatewayApiKey( try { const provider = createGateway({ apiKey, + baseURL: process.env.AI_GATEWAY_BASE_URL, fetch: (url: Parameters[0], init?: Parameters[1]) => globalThis.fetch(url, { ...init, signal: effectiveSignal }), });