Vercel ships AI Gateway, Workflow SDK, and Sandbox for agents

WHY IT MATTERS: Building production agents today forces you to choose between vendor lock-in with a single provider API or stitching together separate services for model routing, durable execution, and secure isolation. Most teams end up maintaining fragile glue code for retries, state persistence, billing aggregation, and provider failover. Vercel is packaging the infrastructure it already runs at scale into a unified stack so you can ship agents without building that scaffolding yourself.

WHAT CHANGED: Vercel introduced four building blocks under the Agent Stack umbrella. AI SDK and AI Gateway give agents a single interface and endpoint to call, route, and stream from hundreds of models with automatic failover and unified cost tracking across providers. You bring your own keys and pay no markup. Workflow SDK checkpoints every step of a long-running agent job, persists state, retries failures, and pauses for human input or slow webhooks, resuming from the last good step instead of restarting from zero and re-running every model call. Vercel Sandbox spins up an isolated microVM with a full Linux filesystem and Docker support for each agent, keeping unreviewed code away from the host. Credentials are injected only when the agent calls a service, so raw tokens are never exposed to the environment. Vercel Connect integrates with external systems once, then mints short-lived, scoped tokens per task so every agent action traces back to the user who authorized it. Chat SDK is also included to embed agents into existing apps where users already work.

WHAT TO WATCH: Real adoption patterns from the launch are already visible. SERHANT. routes market analysis to Claude, marketing copy to GPT, and image generation to Gemini through a single key. FLORA built a creative agent on Workflow SDK that fans out across more than fifty image models without losing state when a step fails. If you are currently managing multiple provider APIs, hand-writing retry logic, or running agent code in unprotected environments, evaluate whether the stack can replace your internal abstractions. The critical question is whether Vercel Connect will support your specific third-party services out of the box, or if you will still need custom OAuth integrations for some tools.