AI Agent News/stories/ai-sdk-zai-3-0-44-accepts-async-api-key-and-token-settings.md

Frameworks

@ai-sdk/zai 3.0.44 accepts async API key and token settings

The @ai-sdk/zai 3.0.44 patch release lets provider API key and token settings be a promise or a synchronous or asynchronous callback. It also makes the experimental OpenAI Live getServerWebSocketConfig() method asynchronous, so callers must await its result.

Source: github.com/vercel/ai/releases/tag/%40ai-sdk%2Fzai%403.0.44

The AI SDK provider package @ai-sdk/zai released version 3.0.44 on 30 October. Its main change lets provider API key and token settings be given as a promise or as a synchronous or asynchronous callback. Credentials are now resolved for each authenticated request, and existing authentication behavior and synchronous credential serialization are kept.

The experimental OpenAI Live getServerWebSocketConfig() method can now resolve asynchronously. Code that uses its result must await it before reading the connection settings. The release also updates @ai-sdk/openai-compatible to 3.0.82, @ai-sdk/provider-utils to 5.0.72 and @ai-sdk/provider to 4.0.35.

Why it matters if you build agents

Agents that need short-lived tokens can now fetch credentials at request time, for example from a secrets store, instead of loading them once at startup.

Any code that calls getServerWebSocketConfig() needs to add await, or it will work with an unresolved result instead of the connection settings.

Get stories like this every weekday

One short email with the day's agent tooling news.

Subscribe