Vercel AI Updates: May 21, 2026

1. Grok Build 0.1 lands on Vercel AI Gateway as an agentic-coding beta with no non-reasoning mode

Vercel. Vercel added xAI’s Grok Build 0.1 beta to the AI Gateway, identifying it as the model powering the Grok Build CLI and a coding model “trained for agentic work.” The integration exposes the model as xai/grok-build-0.1 in the AI SDK with fixed reasoning effort and no non-reasoning mode, so callers cannot trade off latency for cheaper non-thinking inference the way they can with most other gateway models. The placement on the gateway is a quick way for AI SDK users to wire Grok Build into existing apps without provisioning xAI credentials separately, and slots Grok Build into the same coding-model tier as Codex, Claude Code, and Gemini 3.5 Flash on the gateway. Source

2. Chat SDK adds built-in AI SDK toolsets with approval-by-default and lazy loading

Vercel. Vercel’s Chat SDK now ships AI SDK tools through a new chat/ai subpath, packaging built-in toolsets for reader, messenger, and moderator presets, plus an approval-by-default model for write operations and lazy loading for tools that should only initialize on first use. The release lines up with the Chat SDK’s broader move from a chat-UI scaffold to an agent runtime, and the parallel rollout of callback URLs on buttons and modals lets cards pause workflow runs and resume on user interaction across the supported messaging platforms. Combined, the changes are a notable step toward making the Chat SDK a viable substrate for production human-in-the-loop agent workflows rather than just chat interfaces. Source

3. Vercel AI Gateway gets a WordPress plugin exposing 40+ providers via one key

Vercel. Vercel published a WordPress plugin for the AI Gateway that gives WordPress 7.0+ sites access to “hundreds of models from 40+ providers through a single API key,” including Anthropic, Google, and OpenAI, with automatic fallbacks and multi-modal content generation supported out of the box. The plugin makes Vercel’s gateway the model-routing layer for a large class of CMS-driven sites without requiring developers to glue together individual provider SDKs, and is the first official Vercel surface aimed at the WordPress ecosystem rather than the Next.js or Nuxt stacks. Source