---
type: "post"
slug: "vercel-connect-gives-apps-and-agents-scoped-connectors"
title: "Vercel Connect gives apps and agents scoped connectors"
description: "Vercel Connect reached general availability with 100+ connectors that issue short-lived, task-scoped tokens at runtime, on the argument that a vault never fixes a long-lived credential."
retrieval_nugget: "Vercel Connect reached general availability with 100+ connectors that issue short-lived, task-scoped tokens at runtime, on the argument that a vault never fixes a long-lived credential."
published_at: "2026-09-01"
updated_at: "2026-09-12"
record_date: "2026-08-25"
date_kind: "discovered_at"
topics: ["agent-security","agents","ai","mcp","security"]
entities: ["Vercel"]
source_url: "https://vercel.com/blog/the-end-of-credential-sprawl-for-agents"
source_title: "The end of credential sprawl for agents"
source_domain: "vercel.com"
source_terms: ["Vercel","Connect","apps","scoped","connectors"]
summary_word_count: 194
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:vercel-connect-gives-apps-and-agents-scoped-connectors"
status: "published"
source_urls: ["https://vercel.com/blog/the-end-of-credential-sprawl-for-agents"]
visuals: []
editorial_provenance: {"schema_version":"newruntime-editorial-copy-v1","content_status":"source_grounded_final","final_copy_sha256":"sha256:91c48b6dbe0df6d89a2566fac40fbf57756269d9d77dd2614b8f6fc7d891da3f","reviewed_at":"2026-09-12T10:00:00Z","source_evidence_count":1,"verified_claim_count":2,"site_analysis_schema_version":"newruntime-site-analysis-v1","site_object_kind":"field_note","observed_fact_count":2,"implication_count":1,"watch_condition_count":1,"related_record_count":3}
analysis: {"schema_version":"newruntime-site-analysis-v1","object_kind":"field_note","thesis":"Vercel Connect is generally available, with the ecosystem past 100 connectors after public beta, unified behaviour and added governance features.","observed_facts":[{"text":"Vercel Connect is generally available with more than 100 connectors after its public beta.","source_urls":["https://vercel.com/blog/the-end-of-credential-sprawl-for-agents"]},{"text":"Tokens are requested by code at runtime, scoped to the task, and expire on their own rather than being provisioned long-lived.","source_urls":["https://vercel.com/blog/the-end-of-credential-sprawl-for-agents"]}],"mechanism":"instead of provisioning a long-lived token, code requests a token at runtime, scoped to the task, that expires on its own","why_now":"Agents made this worse by reaching beyond the codebase to post to Slack, open pull requests, query a warehouse or call an internal API, which is simultaneously the source of their value and of the exposure.","implications":["putting a token in a vault made it harder to steal without making it less dangerous once stolen, because it still never expires and no vault limits what a leaked credential can do"],"evidence_boundary":"This is a general-availability announcement describing the model and connector count, without published token lifetimes, scope granularity or audit format.","watch_conditions":["The condition to watch is whether Connect exposes which task a token was issued for in an inspectable log, because task-scoped is only auditable if the task is recorded alongside the grant."],"related_records":[{"url":"https://newruntime.com/posts/chaindrop-agent-identity-control-plane","relation":"Prior coverage of identity as the root of agent security."},{"url":"https://newruntime.com/posts/knownagents-turns-ai-bot-identity-into-an-authentication-boundary-against-sp","relation":"Prior coverage of authentication boundaries for agents."},{"url":"https://newruntime.com/topics/agent-security","relation":"Topic hub for credential and access scope."}]}
routes: {"html":"https://newruntime.com/posts/vercel-connect-gives-apps-and-agents-scoped-connectors/","markdown":"https://newruntime.com/posts/vercel-connect-gives-apps-and-agents-scoped-connectors.md","json":"https://newruntime.com/posts/vercel-connect-gives-apps-and-agents-scoped-connectors.json"}
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
---

# Vercel Connect gives apps and agents scoped connectors

## Retrieval answer

Vercel Connect reached general availability with 100+ connectors that issue short-lived, task-scoped tokens at runtime, on the argument that a vault never fixes a long-lived credential.

Vercel Connect is generally available, with the ecosystem past 100 connectors after public beta, unified behaviour and added governance features. The mechanism is narrow and specific: instead of provisioning a long-lived token, code requests a token at runtime, scoped to the task, that expires on its own.

The argument against the usual alternative is the sharper part. Managing credentials became its own workload — rotation scripts, secrets copied across environments, tokens shared between users — and putting a token in a vault made it harder to steal without making it less dangerous once stolen, because it still never expires and no vault limits what a leaked credential can do. Agents made this worse by reaching beyond the codebase to post to Slack, open pull requests, query a warehouse or call an internal API, which is simultaneously the source of their value and of the exposure.

Short-lived and scoped is the same conclusion reached from the identity side in [ChainDrop showing agent security starts with identity](https://newruntime.com/posts/chaindrop-agent-identity-control-plane/) and in [KnownAgents treating bot identity as an authentication boundary](https://newruntime.com/posts/knownagents-turns-ai-bot-identity-into-an-authentication-boundary-against-sp/). The [agent security hub](https://newruntime.com/topics/agent-security/) tracks credential scope as a first-class control.

This is a general-availability announcement describing the model and connector count, without published token lifetimes, scope granularity or audit format. The condition to watch is whether Connect exposes which task a token was issued for in an inspectable log, because task-scoped is only auditable if the task is recorded alongside the grant.

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- topic hub: [Agent Security](https://newruntime.com/topics/agent-security.md): Explore the agent-security topic hub.
- topic hub: [Agents](https://newruntime.com/topics/agents.md): Explore the agents topic hub.
- topic hub: [Ai](https://newruntime.com/topics/ai.md): Explore the ai topic hub.
- collection: [Field Notes](https://newruntime.com/posts.json): Open the latest editorial analysis.
- collection: [Source Ledger](https://newruntime.com/source-ledger.json): Inspect the public source evidence graph.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)