Vercel Connect ends credential sprawl for agents
Covered by Signal Brief for B2B SaaS product managers — one of 5 tools in Issue #12 · vercel.com
What it does
Vercel this week took Connect out of public beta and made it generally available — an attempt to end credential sprawl for AI agents. The premise: every useful agent reaches beyond your codebase, posting to Slack, opening pull requests, querying Snowflake, and for years granting that reach meant provisioning a long-lived token and hoping it never leaked. Connect replaces stored credentials with runtime requests. You register a connector once for a provider — Slack, GitHub, Snowflake, Shopify, Workday, or your own OAuth service — attach it to the projects and environments that need it, and your code calls getToken at runtime; tokens are scoped to the task in the request, expire on their own, and refresh automatically. No second secret is required: every deployment carries an OIDC identity the SDK uses to prove who is asking. Scoping happens per step — one step of an agent might request read-only access to a single repository, the next asks for permission to open an issue — and identity is per request too: tokens act as the app by default, or as a named user who approved a one-time consent flow. GA ships more than 100 preset connectors, managed connectors for Slack, GitHub, Linear, and Salesforce, support for any OAuth-capable MCP server, and the governance layer production demands: fine-grained RBAC over who can create connectors, audit logs, token and trigger observability, and one-command revocation. Inbound events get the same treatment — providers send webhooks to Connect, which verifies signatures server-side and re-attests them with an OIDC identity, so your app holds no bot token and no signing secret. Pricing is usage-based: the Hobby tier includes 500 token requests and 1,000 triggers a month at no cost, and Pro runs $3 per 1,000 token requests.
Why it matters for PMs
Agent-to-SaaS connectivity is standardizing, and the pattern is worth internalizing before you design your next integration. Three points. First, “access becomes a request” is the reference architecture for agent features: per-step scoping, auto-expiring tokens, named-user identity, audit logs, and RBAC are exactly the controls enterprise procurement asks about — building them in from day one shortens security reviews and makes agent work safe to expand. Second, connector catalogs are becoming distribution channels: being a managed connector — the way Linear and Salesforce are here — means every agent built on the platform is one call away from your product. If you sell B2B software, ask whether you should be listed in these catalogs, and whether your API and MCP surfaces are clean enough to be consumed without a human in the loop. Third, note where the trust boundary landed: the app holds no secrets at all, and even inbound webhooks are verified and re-attested by the platform. That is a preview of how integration infrastructure gets rebuilt for agents — and a reminder that if your product is the system being connected to, your job is to make authorization expressive enough that an agent can ask for exactly what it needs and nothing more.
The link Signal Brief published for this tool in Issue #12.
The other 4 tools in Issue #12
5 tools like these, every weekday before standup.
Join Signal Brief for $10/month or $96/year — every tool with why it matters for PMs and a direct link. No sponsors, no noise.
Start your 7-day free trialNo card required to start. Cancel anytime.