Linq is now a Vercel Managed Connector

Vercel Connect now offers Linq as a managed connector, allowing Vercel deployments and eve agents to send and receive iMessage, RCS, and SMS without storing long-lived Linq API keys or webhook-signing secrets in environment variables. Vercel holds the credentials, issues short-lived environment-scoped tokens through OIDC, logs token activity, supports connector links and webhook triggers, and charges by token request with SDK caching intended to reduce usage. Developers can create and attach a connector through the dashboard or CLI, while the eve framework can add a Linq channel that automatically verifies inbound requests, maintains durable chat sessions, identifies senders, handles read receipts and typing indicators, and supports message filtering. The channel’s default steering behavior cancels and replaces active turns when follow-up messages arrive, but applications with irreversible tool actions should require approval or use queued turns. Deployments may also call Linq’s API directly using exchanged tokens, while direct webhooks require HMAC validation. Recommended operational practices include separating production and preview connectors, handling duplicate events idempotently, retrying one token refresh after a 401 error, accounting for SMS feature limitations, managing group-chat behavior, and monitoring number reputation.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.