Vercel Connect
An enterprise integration and data governance product from Vercel. By implementing scoped connectors, it mints temporary tokens for each agent task, enabling least-privilege access under a zero-trust security architecture.
Timeline (last 90 days)
Requests to obtain and refresh access tokens also go through Secure Compute routing, consistent with business API calls.
This update only changes the network path of requests, and the credential management mechanism remains unchanged, so developers still do not need to store long-lived provider keys or build their own OAuth flow.
Configuring Secure Compute routing does not require writing additional network configuration code.
When the selected network is unavailable, routed requests fail directly rather than falling back to Connect's shared IP, which is an intentional design choice.
Vercel Connect officially supports Secure Compute routing, allowing developers to access service providers with IP allowlists, such as Salesforce and Snowflake, through dedicated static IPs.
Vercel Connect previously used a shared IP pool for outbound requests, which could not meet the requirements of enterprise-grade service providers that need IP allowlists.
After enabling Secure Compute routing, requests that Connect makes to providers go through the dedicated static IP of the selected network, rather than Connect's shared IP.
The request when first creating a connector and all provider discovery requests bypass the selected network and connect directly to the provider, not going through the static IP.
The Secure Compute routing setting only applies to provider requests sent by Connect and does not affect the application's own direct API routing.
Currently Vercel Connect's MCP Events APIs all carry the experimental_ prefix, meaning interface signatures may still change, and they are not suitable for direct use in production systems with extremely high stability requirements.
12 more timeline events
All Facts (20)
EVE supports plugging in open-source adapters such as Postgres, OpenAI Responses API, and Docker, and can also be deployed to Vercel in one click using Vercel Workflows, Sandbox, and Vercel Connect.
60%UnverifiedWhen the selected network is unavailable, routed requests fail directly rather than falling back to Connect's shared IP, which is an intentional design choice.
50%UnverifiedVercel Connect previously used a shared IP pool for outbound requests, which could not meet the requirements of enterprise-grade service providers that need IP allowlists.
50%UnverifiedAfter enabling Secure Compute routing, requests that Connect makes to providers go through the dedicated static IP of the selected network, rather than Connect's shared IP.
50%UnverifiedConfiguring Secure Compute routing does not require writing additional network configuration code.
50%UnverifiedThis update only changes the network path of requests, and the credential management mechanism remains unchanged, so developers still do not need to store long-lived provider keys or build their own OAuth flow.
50%UnverifiedRequests to obtain and refresh access tokens also go through Secure Compute routing, consistent with business API calls.
50%UnverifiedThe Secure Compute routing setting only applies to provider requests sent by Connect and does not affect the application's own direct API routing.
50%UnverifiedThe request when first creating a connector and all provider discovery requests bypass the selected network and connect directly to the provider, not going through the static IP.
50%UnverifiedConnect provides experimental_verifyMcpEvent for verifying the legitimacy of an event's origin on the server side; this step cannot be omitted, otherwise third parties can forge events and push them to the application.
50%UnverifiedConnect can wrap AI SDK's event discovery and subscription interfaces as Agent tools, so that after an Agent enables the event capability of an MCP connection in eve, it can discover events, create subscriptions, view subscription status, and stop subscriptions.
50%UnverifiedCurrently Vercel Connect's MCP Events APIs all carry the experimental_ prefix, meaning interface signatures may still change, and they are not suitable for direct use in production systems with extremely high stability requirements.
50%UnverifiedThe event capability depends on support on the MCP server side—if the server does not expose webhooks, Connect has nothing to subscribe to.
50%UnverifiedConnect's experimental_subscribe interface supports the ttlMs parameter (for example, 24 hours), automatically renews before expiry, and developers do not need to implement polling or renewal logic themselves.
50%UnverifiedConnect's experimental_subscribe interface supports the idempotencyKey parameter, and submitting the same key repeatedly will not create duplicate subscriptions.
50%UnverifiedConnect also supports Cross-App Access (XAA) and extends this capability to MCP authorization scenarios, allowing Agents to reuse the authorization relationships already configured by the enterprise when making cross-application calls.
50%UnverifiedVercel Connect enables scoped connectors and mints tokens for each agent task, so that agents only access the specific context needed for their work.
50%UnverifiedVercel Connect officially supports Secure Compute routing, allowing developers to access service providers with IP allowlists, such as Salesforce and Snowflake, through dedicated static IPs.
50%UnverifiedVercel Connect has officially entered the public beta of MCP Events, allowing developers to let applications and Agents subscribe to webhook events from MCP-compatible servers.
50%UnverifiedVercel's Connect feature has officially entered public beta, adding the Enterprise-Managed Authorization (EMA) capability.
50%