Agent Credential Management

6/17/2026

This post introduces the 'Agent Stack' as a collection of building blocks for creating production-grade agents. It details three core capabilities: connecting to models (AI SDK, AI Gateway), executing complex workflows (Workflow SDK, Vercel Sandbox), and connecting to data and tools (Vercel Connect, Chat SDK). It also introduces the 'eve' agent framework. Vercel Connect is highlighted as a system for scoped, short-lived access to data and systems, building upon previous work in credential management.

6/17/2026

This post introduces Vercel Connect, a new system for agent authentication and authorization. It details the architecture of runtime credential exchange, replacing static tokens with short-lived, scoped credentials. Key technical aspects include OIDC for app identity, scoped token requests with provider-specific details (scopes, resource restrictions), per-user token scoping, environment-based access containment, and token revocation mechanisms. It also describes how Vercel Connect handles event-driven agents via verified webhook forwarding and provides integration details with various SDKs and frameworks.

6/17/2026

This post introduces Vercel for Enterprise Apps and Agents, a platform designed to enable companies to safely ship AI-powered applications and agents behind their access and security boundaries. It details three key components: Vercel Passport for identity provider integration to secure internal apps and agents, Vercel Connect for providing agents with short-lived, scoped credentials to external systems (Slack, GitHub, Snowflake, Salesforce, Linear, etc.) via OAuth/OIDC, and Enterprise Managed Users for full lifecycle control of Vercel/v0 users through SAML SSO and Directory Sync. It also announces Bring Your Own Cloud (BYOC) on AWS for running workloads within a customer's AWS account. The post highlights how these features address challenges in managing access, security, and data for internal agents and apps, enabling secure prototyping and production deployment.

8/6/2025

Introduces Vercel MCP (Model Context Provider) server, a secure, OAuth-compliant interface enabling AI clients (like Cursor and Claude) to interact with Vercel projects. This provides AI tools with structured, read-only access to Vercel documentation, deployment logs, and project metadata. The MCP server supports the Model Context Protocol specification for tools and prompts, allowing AI models to call external systems. It emphasizes security through a read-only mode, an allowlist of approved clients, and OAuth consent screens to prevent issues like the Confused Deputy problem. The post also highlights the potential for developers to build their own MCP servers.

8/28/2024

Vercel now supports OpenID Connect (OIDC) Federation, allowing developers to replace long-lived credentials with short-lived, RSA-signed JSON Web Tokens (JWTs) for external requests in builds and Vercel Functions. This enhances security by minimizing the risk of compromised static credentials and automates token issuance and rotation. The implementation leverages Vercel as an Identity Provider (IdP) to issue verifiable JWTs that can be used to authenticate with third-party services like AWS, Azure, Firebase, and GCP.

5/16/2024

This post introduces the concept of a Data Access Layer (DAL) for Next.js applications to centralize authentication and authorization checks. It explains the differences between client-side and server-side code, and server and client components in Next.js. The post then details how to implement fine-grained authorization using OpenFGA (or Okta FGA) for relationship-based access control (ReBAC), providing an example authorization model and demonstrating how to integrate the OpenFGA SDK into the DAL for checking permissions.

12/14/2022

This post announces the expansion of Auth.js to support SvelteKit, introducing SvelteKit Auth. It details the use of `@auth/core` and the `@auth/sveltekit` package, demonstrating how to configure OAuth providers (e.g., GitHub) using environment variables and implement user sign-in/sign-out functionality within SvelteKit applications. It also shows how to protect routes for authenticated users.