{ "data": { "a": { "slug": "vercel-connect", "name": "Vercel Connect", "vendor": "Vercel Inc.", "vendorUrl": "https://vercel.com", "kind": "http-api", "category": "agent-auth", "summary": "Vercel Connect is a credential broker for apps and agents. Code asks it for a short-lived, scoped token for Slack, GitHub, Microsoft, Linear, Snowflake or any OAuth, API-key or MCP service, as the app or for a user.", "url": "https://www.anchorterminal.com/tools/vercel-connect", "markdownUrl": "https://www.anchorterminal.com/tools/vercel-connect.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/vercel-connect.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/vercel-connect.json", "repo": "https://github.com/vercel/vercel", "license": "Proprietary service under Vercel's Terms of Service and the Vercel Connect product terms. The `@vercel/connect` SDK and the Vercel CLI are Apache-2.0", "transports": [ "http" ], "remoteUrl": "https://api.vercel.com", "packages": [ { "registry": "npm", "name": "@vercel/connect" } ], "auth": "mixed", "authNotes": "Access is self-serve with a Vercel account, on every plan. A deployment calls Connect with its project OIDC token (`VERCEL_OIDC_TOKEN`), which Connect checks against the connector's project links and their environments. Locally, `vercel env pull` writes a development OIDC token that lasts about 12 hours. Outside Vercel, a Vercel access token goes in `vercelToken`, and it can request only the app subject or its own user. Connect then holds the provider side. Vercel registers the OAuth client for managed connectors (Slack, GitHub, Linear, Microsoft, Snowflake, Salesforce), and the customer supplies a client or an API key for the others. End users consent in a browser at a URL from `startAuthorization`.", "pricing": "freemium", "pricingNotes": "Billed per token request and per trigger. Hobby includes 500 token requests and 1,000 triggers a month at no extra charge, and Vercel's fair use guidelines limit Hobby to non-commercial, personal use. Pro is $3.00 per 1,000 token requests and $0.95 per 1,000 triggers on top of the plan. Enterprise is negotiated. A trigger is counted once per destination, and once per event when no destination is set. The SDK's in-process cache means many provider calls in one invocation cost one token request (https://vercel.com/docs/connect/pricing, checked 2026-10-08).", "priceSummary": "$3 / 1k req", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the Connect docs, the pricing page or the Connect operations of the OpenAPI document (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 16354, "npmWeekly": 738165, "pypiWeekly": null, "asOf": "2026-10-08" }, "docsUrl": "https://vercel.com/docs/connect", "llmsTxt": "https://vercel.com/llms.txt", "openapi": "https://openapi.vercel.sh/", "capabilities": [ "auth.tokens", "auth.oauth", "auth.consent", "auth.audit" ], "tags": [ "hosted", "freemium", "free-tier", "oauth", "oidc", "openapi", "llms-txt", "typescript", "cli", "webhooks", "status-page", "soc2", "iso27001" ], "lastRelease": "2026-10-06", "graded": true, "anchor": { "graded": true, "score": 68.8, "grade": "B", "agentReady": false, "rank": 195, "ranked": true, "rankOf": 842, "categoryRank": 7, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 75, "maintenance": 81, "payments": 40, "reliability": 63, "schema": 84, "security": 83, "transparency": 77 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-08" }, "negative": -3, "negativeNotes": [ "April 2026. Vercel's security bulletin says an attacker took over an employee's account through a compromised third-party AI tool, reached internal systems and decrypted non-sensitive environment variables of a limited subset of customers. It predates Connect's general availability on 25 August 2026 and is documented with remediation, so 3 of a possible 15 is taken, because Connect now keeps customers' provider refresh tokens on the same platform (https://vercel.com/kb/bulletin/vercel-april-2026-security-incident)." ], "verdict": "Provider refresh tokens stay with Vercel, and code receives short-lived tokens tied to a project and environment through one call with a public OpenAPI definition. Vercel's SLA excludes its APIs, the status page records 94 minutes of elevated Connect errors on 10 September 2026, and the only SDK is TypeScript.", "bestFor": "Teams already deploying on Vercel whose agents need user or app tokens for Slack, GitHub, Microsoft, Linear, Snowflake or an MCP server without storing provider secrets.", "strengths": [ "Refresh tokens stay on Vercel's infrastructure. Code receives only short-lived access tokens, as the app or for a named user", "A deployment authenticates with its project OIDC token, checked against per-environment project links, so no provider secret sits in environment variables", "Public OpenAPI 3.0.3 document covers 13 Connect paths, including `/v1/connect/token/{connector}` and `/v1/connect/authorize/{connector}`", "Token requests, completed authorisations and revocations are logged with `tokenId` and `authorizationId`, and can be sent to a drain on Pro and Enterprise", "Rate limits are published with numbers, 200 reads and 50 writes a minute per team" ], "weaknesses": [ "Vercel's SLA says it does not apply to the APIs or CLI, so token requests carry no uptime commitment", "Elevated Connect errors for 94 minutes on 10 September 2026, marked major, and again on 18 September, per the status page", "Event history is kept 12 hours on Hobby and 3 days on Pro. Connector audit logs and 30 days need Enterprise", "Revocation depends on the provider. Without a revocation endpoint the provider credential can work until it expires", "The SDK is TypeScript only, and the public repository's copy stops at 2.0.2 while npm has 2.4.1" ], "agentNotes": [ "Call `getToken` at request time and don't store the result. The SDK caches up to 100 tokens in process and refreshes them 30 seconds before expiry", "Pass `scopes` on every request. Since SDK 1.0.0 an omitted `scopes` defaults to `['*']`, the connector's default scopes", "Catch `UserAuthorizationRequiredError`, call `startAuthorization` and send the user to the returned URL. Consent needs a person in a browser", "Outside Vercel, pass a Vercel access token as `vercelToken`. It can request only the app subject or its own user, not another user", "On a 429 wait one minute for the window to reset. Limits are 200 token requests a minute per team" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 68.8 } ], "editorialScores": { "ergonomics": 75, "maintenance": 81, "payments": 40, "reliability": 63, "schema": 84, "security": 83, "transparency": 55 }, "provenanceScore": 99 }, "connect": { "install": "pnpm add @vercel/connect", "http": "curl -X POST https://api.vercel.com/v1/connect/token/slack%2Facme-slack \\\n -H \"Authorization: Bearer $VERCEL_OIDC_TOKEN\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"subject\":{\"type\":\"app\"},\"scopes\":[\"chat:write\"]}'" }, "letme": { "capability": "https://letme.dev/auth.tokens", "tool": "https://letme.dev/vercel-connect" }, "sameCompany": [ "vercel-sandbox" ], "area": "agent-runtime", "unitPrices": [ { "item": "Token request (Pro)", "unit": "1k-requests", "usd": 3, "note": "Hobby includes 500 a month. Enterprise negotiated" }, { "item": "Trigger, a forwarded provider webhook (Pro)", "unit": "1k-requests", "usd": 0.95, "note": "Counted per destination. Hobby includes 1,000 a month" } ], "provenance": { "legalEntity": "Vercel Inc.", "domain": "vercel.com", "domainRegistered": "1999-10-04", "endpointOnVendorDomain": true, "terms": "https://vercel.com/legal/terms", "privacy": "https://vercel.com/legal/privacy-policy", "statusPage": "https://www.vercel-status.com", "changelog": "https://vercel.com/changelog", "securityTxt": "valid", "checked": "2026-10-08", "notes": [ "The Terms of Service (last updated 1 June 2026) name Vercel Inc., 440 N Barranca Ave #4133, Covina, CA 91723, and California law. The DPA calls Vercel Inc. a Delaware corporation.", "Connect also has its own product terms at https://vercel.com/docs/connect/legal. The Terms of Service text we read does not mention Connect by name.", "The Privacy Notice (effective 1 June 2026) says it does not apply to personal information Vercel processes as a processor for customers, which the DPA covers. The DPA (effective 31 March 2026) applies to Pro and Enterprise plans.", "https://vercel.com/.well-known/security.txt points to HackerOne and responsible.disclosure@vercel.com and expires 2027-09-28.", "RDAP gives vercel.com a registration date of 1999-10-04, long before Vercel, so the domain was bought later.", "The API answers at api.vercel.com and the OpenAPI document at openapi.vercel.sh." ], "score": 99 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/vercel-connect.json", "live": { "slug": "vercel-connect", "probe": { "target": "https://api.vercel.com", "method": "get", "lastAt": "2026-10-09T10:43:00.826005623Z", "lastOk": true, "lastStatus": 200, "lastMs": 550, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 570, "p95ms24h": 1136, "samples24h": 33, "samples30d": 33, "days": [ { "date": "2026-10-09", "probes": 33, "ok": 33 } ] }, "vendorStatus": { "page": "https://www.vercel-status.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-09T10:42:07.466379649Z" }, "updatedAt": "2026-10-09T10:43:00.826005623Z" } }, "answer": "Vercel Connect scores 68.8 (B) on agent readiness against WorkOS Pipes and Agents's 59.9 (C), and leads in 5 of 7 scored categories. WorkOS Pipes and Agents leads on reliability.", "b": { "slug": "workos-pipes", "name": "WorkOS Pipes and Agents", "vendor": "WorkOS", "vendorUrl": "https://workos.com", "kind": "http-api", "category": "agent-auth", "summary": "WorkOS tools for connecting agents to third-party accounts, managing access tokens and assigning revocable agent identities.", "url": "https://www.anchorterminal.com/tools/workos-pipes", "markdownUrl": "https://www.anchorterminal.com/tools/workos-pipes.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/workos-pipes.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/workos-pipes.json", "repo": "https://github.com/workos/workos-node", "license": "MIT (SDKs), platform closed", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.workos.com", "packages": [ { "registry": "npm", "name": "@workos-inc/node" }, { "registry": "pypi", "name": "workos" } ], "auth": "mixed", "authNotes": "Server calls take the secret key as `Authorization: Bearer $WORKOS_API_KEY` (`sk_...`). End users connect accounts through the Pipes widget or an authorisation URL from `/data-integrations/{slug}/authorize`, which must be opened in the browser, not fetched. Agent tokens are minted from a blueprint as user-delegated, autonomous or agent-delegated sessions. The WorkOS MCP server signs in with OAuth as a dashboard user, with no API key.", "pricing": "freemium", "pricingNotes": "Pay as you go, with no card to start and a card before production. AuthKit is free up to 1,000,000 monthly active users, then $2,500 a month per extra million. SSO and Directory Sync connections are $125 a month each for the first 15, $100 for 16 to 30, $80 for 31 to 50 and $65 for 51 to 100. Audit Logs are free at the base, with $125 a month per SIEM connection and $99 a month per million events stored. Radar is free for 1,000 checks, then $100 per 50,000. A custom domain is $99 a month. Annual credits plans add volume discounts and a 99.99 per cent SLA (https://workos.com/pricing). Pipes and Agents don't appear on the pricing page, so we don't know what a connection or an agent session costs.", "priceSummary": "$125 / mo", "where": "hosted", "x402": { "level": "no", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 221, "npmWeekly": 4041570, "pypiWeekly": 1697594, "asOf": "2026-09-30" }, "docsUrl": "https://workos.com/docs/pipes", "registryName": "com.workos/mcp", "capabilities": [ "auth.oauth", "auth.tokens", "auth.consent", "auth.agent-identity", "auth.audit" ], "tags": [ "hosted", "freemium", "free-tier", "oauth", "mcp", "typescript", "python", "enterprise", "webhooks" ], "lastRelease": "2026-09-28", "graded": true, "anchor": { "graded": true, "score": 59.9, "grade": "C", "agentReady": false, "rank": 485, "ranked": true, "rankOf": 842, "categoryRank": 11, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 69, "maintenance": 83, "payments": 10, "reliability": 70, "schema": 53, "security": 69, "transparency": 63 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-01" }, "negative": 0, "verdict": "Agent identity with per-session revocation and token lifetimes set per blueprint. 21 incidents on the status page since 3 July 2026, several over an hour.", "bestFor": "Best when WorkOS already runs SSO or AuthKit and the agent needs users' or organisations' tokens for many SaaS providers plus its own revocable identity.", "strengths": [ "Agent identity with per-session revocation and token lifetimes set per blueprint", "Pipes covers 500+ providers with user-owned and organisation-owned connections by OAuth, API key or client credentials", "Published rate limits of 6,000 requests a minute per key, with Retry-After on a 429", "Same platform for SSO, directory sync, RBAC, Audit Logs and Vault", "SOC 2 Type 2, a public subprocessor list and a 99.99 per cent SLA on annual plans" ], "weaknesses": [ "21 incidents on the status page since 3 July 2026, several over an hour", "Pipes and Agents aren't on the pricing page", "Deleting a connected account doesn't revoke the grant at the provider", "Breaking Pipes change in SDK 11.0.0 on 28 September 2026", "No OpenAPI file, llms.txt or security.txt we could find" ], "agentNotes": [ "Call POST /data-integrations/{provider}/token with user_id for each use and don't cache the token", "Branch on `active` in the response and send the user to reconnect on `needs_reauthorization`", "Wait for Retry-After on a 429, or back off with jitter when it's missing", "Use lower-case provider slugs such as github or slack", "Revoke an agent's session through the Agents API when a task ends instead of waiting for expiry" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 2.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 59.9 } ], "editorialScores": { "ergonomics": 69, "maintenance": 83, "payments": 10, "reliability": 70, "schema": 53, "security": 69, "transparency": 37 }, "provenanceScore": 88 }, "connect": { "install": "npm install @workos-inc/node", "http": "curl -X POST https://api.workos.com/data-integrations/github/token -H \"Authorization: Bearer $WORKOS_API_KEY\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\"user_id\":\"user_01EHZNVPK3SFK441A1RGBFSHRT\"}'", "claudeCode": "claude mcp add --transport http --scope user workos https://mcp.workos.com/mcp", "config": { "mcpServers": { "workos": { "url": "https://mcp.workos.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/auth.oauth", "tool": "https://letme.dev/workos-pipes" }, "area": "agent-runtime", "unitPrices": [ { "item": "SSO or Directory Sync connection (first 15)", "unit": "month", "usd": 125, "note": "Per connection per month, falling to $65 above 50" }, { "item": "Audit Logs SIEM connection", "unit": "month", "usd": 125, "note": "Plus $99 a month per million events stored" }, { "item": "Custom domain", "unit": "month", "usd": 99, "note": "AuthKit, Admin Portal and email sender" } ], "provenance": { "legalEntity": "WorkOS, Inc.", "domain": "workos.com", "domainRegistered": "2005-02-02", "endpointOnVendorDomain": true, "terms": "https://workos.com/legal/terms", "privacy": "https://workos.com/legal/privacy", "statusPage": "https://status.workos.com", "changelog": "https://github.com/workos/workos-node/blob/main/CHANGELOG.md", "securityTxt": "none", "checked": "2026-09-30", "notes": [ "The website terms (effective 29 October 2020) name WorkOS, Inc. and California law. The privacy policy was updated 20 October 2025 and doesn't say where data is stored.", "RDAP shows workos.com registered on 2005-02-02, years before the company, so the domain was bought later.", "/.well-known/security.txt returned 404 on 2026-09-30." ], "score": 88 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/workos-pipes.json", "live": { "slug": "workos-pipes", "probe": { "target": "https://api.workos.com", "method": "get", "lastAt": "2026-10-09T10:43:02.215233865Z", "lastOk": true, "lastStatus": 200, "lastMs": 151, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 132, "p95ms24h": 172, "samples24h": 260, "samples30d": 2098, "days": [ { "date": "2026-10-01", "probes": 109, "ok": 109 }, { "date": "2026-10-02", "probes": 248, "ok": 248 }, { "date": "2026-10-03", "probes": 271, "ok": 271 }, { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 114, "ok": 114 } ] }, "vendorStatus": { "page": "https://status.workos.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-09T10:42:10.221325012Z" }, "versions": [ { "registry": "github", "name": "workos/workos-node", "version": "v11.0.0", "released": "2026-09-28", "seenAt": "2026-10-08T16:35:06.66310113Z" }, { "registry": "mcp-registry", "name": "com.workos/mcp", "version": "1.0.0", "seenAt": "2026-10-09T02:57:46.004536428Z" }, { "registry": "npm", "name": "@workos-inc/node", "version": "11.0.0", "seenAt": "2026-10-08T16:35:05.630586961Z" }, { "registry": "pypi", "name": "workos", "version": "10.5.0", "released": "2026-09-24", "seenAt": "2026-10-08T16:35:06.473084485Z" } ], "githubStars": 224, "npmWeekly": 4251277, "pypiWeekly": 1715183, "securityTxt": { "url": "https://workos.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-08T15:38:57.279092605Z" }, "domain": { "domain": "workos.com", "registered": "2005-02-02", "source": "https://rdap.verisign.com/com/v1/domain/workos.com", "checkedAt": "2026-10-04T13:09:49.925296041Z" }, "pages": [ { "url": "https://raw.githubusercontent.com/workos/workos-node/main/CHANGELOG.md", "kind": "changelog", "status": 304, "checkedAt": "2026-10-08T18:24:51.718491233Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "57d8be278609" }, { "url": "https://workos.com/pricing", "kind": "pricing", "status": 304, "checkedAt": "2026-10-08T18:25:55.816742057Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "0cdd6961c090" }, { "url": "https://workos.com/legal/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-08T18:25:50.548963085Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "5fc970fc9d08" }, { "url": "https://workos.com/legal/terms", "kind": "terms", "status": 200, "checkedAt": "2026-10-08T18:25:52.624391607Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "8b3130dd8035" } ], "updatedAt": "2026-10-09T10:43:02.215233865Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Vercel Inc.", "b": "WorkOS", "name": "Vendor" }, { "a": "https://api.vercel.com", "b": "https://api.workos.com", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP, Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "$3 per 1,000 requests", "b": "not published", "name": "Price for auth tokens" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Vercel's Terms of Service and the Vercel Connect product terms. The `@vercel/connect` SDK and the Vercel CLI are Apache-2.0", "b": "MIT (SDKs), platform closed", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "not listed", "b": "com.workos/mcp", "name": "MCP registry" }, { "a": "2026-10-06", "b": "2026-09-28", "name": "Last release" }, { "a": "2026-06-01", "b": "2020-10-29", "name": "Terms last updated" }, { "a": "2026-06-01", "b": "2025-10-20", "name": "Privacy policy last updated" }, { "a": "yes, with an opt-out", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "yes", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "16k stars, 738k npm/wk", "b": "221 stars, 4M npm/wk, 1.7M PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "2.5/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "Vercel Connect scores 68.8 (B) on agent readiness against WorkOS Pipes and Agents's 59.9 (C), and leads in 5 of 7 scored categories. WorkOS Pipes and Agents leads on reliability.", "question": "Which is better for AI agents, Vercel Connect or WorkOS Pipes and Agents?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do Vercel Connect and WorkOS Pipes and Agents need an API key?" }, { "answer": "Yes. Vercel Connect has a hosted endpoint at https://api.vercel.com and WorkOS Pipes and Agents at https://api.workos.com.", "question": "Can an agent call Vercel Connect and WorkOS Pipes and Agents without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 84 against 53", "Agent ergonomics, 75 against 69", "Security \u0026 auth, 83 against 69", "Payments \u0026 pricing, 40 against 10", "Transparency \u0026 trust, 77 against 63" ], "also": null, "goodFor": "Teams already deploying on Vercel whose agents need user or app tokens for Slack, GitHub, Microsoft, Linear, Snowflake or an MCP server without storing provider secrets.", "slug": "vercel-connect", "watchFor": "Vercel's SLA says it does not apply to the APIs or CLI, so token requests carry no uptime commitment" }, { "aheadOn": [ "Reliability, 70 against 63" ], "also": [ "No incidents deducted, where Vercel Connect loses 3 points for them" ], "goodFor": "Best when WorkOS already runs SSO or AuthKit and the agent needs users' or organisations' tokens for many SaaS providers plus its own revocable identity.", "slug": "workos-pipes", "watchFor": "21 incidents on the status page since 3 July 2026, several over an hour" } ], "job": { "capability": "auth.tokens", "name": "Auth tokens" }, "others": [ { "json": "https://www.anchorterminal.com/compare/aembit-vs-vercel-connect.json", "title": "Aembit vs Vercel Connect", "url": "https://www.anchorterminal.com/compare/aembit-vs-vercel-connect" }, { "json": "https://www.anchorterminal.com/compare/aembit-vs-workos-pipes.json", "title": "Aembit vs WorkOS Pipes and Agents", "url": "https://www.anchorterminal.com/compare/aembit-vs-workos-pipes" }, { "json": "https://www.anchorterminal.com/compare/agentcore-identity-vs-vercel-connect.json", "title": "Amazon Bedrock AgentCore Identity vs Vercel Connect", "url": "https://www.anchorterminal.com/compare/agentcore-identity-vs-vercel-connect" }, { "json": "https://www.anchorterminal.com/compare/agentcore-identity-vs-workos-pipes.json", "title": "Amazon Bedrock AgentCore Identity vs WorkOS Pipes and Agents", "url": "https://www.anchorterminal.com/compare/agentcore-identity-vs-workos-pipes" }, { "json": "https://www.anchorterminal.com/compare/arcade-vs-vercel-connect.json", "title": "Arcade.dev vs Vercel Connect", "url": "https://www.anchorterminal.com/compare/arcade-vs-vercel-connect" }, { "json": "https://www.anchorterminal.com/compare/arcade-vs-workos-pipes.json", "title": "Arcade.dev vs WorkOS Pipes and Agents", "url": "https://www.anchorterminal.com/compare/arcade-vs-workos-pipes" }, { "json": "https://www.anchorterminal.com/compare/auth0-ai-agents-vs-vercel-connect.json", "title": "Auth0 for AI Agents (Token Vault) vs Vercel Connect", "url": "https://www.anchorterminal.com/compare/auth0-ai-agents-vs-vercel-connect" }, { "json": "https://www.anchorterminal.com/compare/auth0-ai-agents-vs-workos-pipes.json", "title": "Auth0 for AI Agents (Token Vault) vs WorkOS Pipes and Agents", "url": "https://www.anchorterminal.com/compare/auth0-ai-agents-vs-workos-pipes" }, { "json": "https://www.anchorterminal.com/compare/descope-agentic-identity-vs-vercel-connect.json", "title": "Descope Agentic Identity Hub vs Vercel Connect", "url": "https://www.anchorterminal.com/compare/descope-agentic-identity-vs-vercel-connect" }, { "json": "https://www.anchorterminal.com/compare/descope-agentic-identity-vs-workos-pipes.json", "title": "Descope Agentic Identity Hub vs WorkOS Pipes and Agents", "url": "https://www.anchorterminal.com/compare/descope-agentic-identity-vs-workos-pipes" }, { "json": "https://www.anchorterminal.com/compare/keycard-vs-vercel-connect.json", "title": "Keycard vs Vercel Connect", "url": "https://www.anchorterminal.com/compare/keycard-vs-vercel-connect" }, { "json": "https://www.anchorterminal.com/compare/keycard-vs-workos-pipes.json", "title": "Keycard vs WorkOS Pipes and Agents", "url": "https://www.anchorterminal.com/compare/keycard-vs-workos-pipes" }, { "json": "https://www.anchorterminal.com/compare/microsoft-entra-agent-id-vs-vercel-connect.json", "title": "Microsoft Entra Agent ID vs Vercel Connect", "url": "https://www.anchorterminal.com/compare/microsoft-entra-agent-id-vs-vercel-connect" }, { "json": "https://www.anchorterminal.com/compare/microsoft-entra-agent-id-vs-workos-pipes.json", "title": "Microsoft Entra Agent ID vs WorkOS Pipes and Agents", "url": "https://www.anchorterminal.com/compare/microsoft-entra-agent-id-vs-workos-pipes" }, { "json": "https://www.anchorterminal.com/compare/nango-vs-vercel-connect.json", "title": "Nango vs Vercel Connect", "url": "https://www.anchorterminal.com/compare/nango-vs-vercel-connect" }, { "json": "https://www.anchorterminal.com/compare/nango-vs-workos-pipes.json", "title": "Nango vs WorkOS Pipes and Agents", "url": "https://www.anchorterminal.com/compare/nango-vs-workos-pipes" }, { "json": "https://www.anchorterminal.com/compare/scalekit-agentkit-vs-vercel-connect.json", "title": "Scalekit AgentKit vs Vercel Connect", "url": "https://www.anchorterminal.com/compare/scalekit-agentkit-vs-vercel-connect" }, { "json": "https://www.anchorterminal.com/compare/scalekit-agentkit-vs-workos-pipes.json", "title": "Scalekit AgentKit vs WorkOS Pipes and Agents", "url": "https://www.anchorterminal.com/compare/scalekit-agentkit-vs-workos-pipes" }, { "json": "https://www.anchorterminal.com/compare/stytch-connected-apps-vs-vercel-connect.json", "title": "Stytch Connected Apps vs Vercel Connect", "url": "https://www.anchorterminal.com/compare/stytch-connected-apps-vs-vercel-connect" }, { "json": "https://www.anchorterminal.com/compare/stytch-connected-apps-vs-workos-pipes.json", "title": "Stytch Connected Apps vs WorkOS Pipes and Agents", "url": "https://www.anchorterminal.com/compare/stytch-connected-apps-vs-workos-pipes" } ], "scores": [ { "by": 7, "edge": "workos-pipes", "key": "reliability", "name": "Reliability", "vercel-connect": 63, "weight": 16, "workos-pipes": 70 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 31, "edge": "vercel-connect", "key": "schema", "name": "Schema \u0026 documentation", "vercel-connect": 84, "weight": 13, "workos-pipes": 53 }, { "by": 6, "edge": "vercel-connect", "key": "ergonomics", "name": "Agent ergonomics", "vercel-connect": 75, "weight": 13, "workos-pipes": 69 }, { "by": 14, "edge": "vercel-connect", "key": "security", "name": "Security \u0026 auth", "vercel-connect": 83, "weight": 14, "workos-pipes": 69 }, { "by": 30, "edge": "vercel-connect", "key": "payments", "name": "Payments \u0026 pricing", "vercel-connect": 40, "weight": 10, "workos-pipes": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 2, "edge": "workos-pipes", "key": "maintenance", "name": "Maintenance \u0026 community", "vercel-connect": 81, "weight": 7, "workos-pipes": 83 }, { "by": 14, "edge": "vercel-connect", "key": "transparency", "name": "Transparency \u0026 trust", "vercel-connect": 77, "weight": 7, "workos-pipes": 63 } ], "summary": "Vercel Connect scores 68.8 (B) on agent readiness against WorkOS Pipes and Agents's 59.9 (C), and leads in 5 of 7 scored categories. WorkOS Pipes and Agents leads on reliability. Both do auth tokens.", "verdicts": { "vercel-connect": "Provider refresh tokens stay with Vercel, and code receives short-lived tokens tied to a project and environment through one call with a public OpenAPI definition. Vercel's SLA excludes its APIs, the status page records 94 minutes of elevated Connect errors on 10 September 2026, and the only SDK is TypeScript.", "workos-pipes": "Agent identity with per-session revocation and token lifetimes set per blueprint. 21 incidents on the status page since 3 July 2026, several over an hour." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/vercel-connect-vs-workos-pipes", "json": "https://www.anchorterminal.com/compare/vercel-connect-vs-workos-pipes.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/vercel-connect-vs-workos-pipes.md", "slim": "https://www.anchorterminal.com/compare/vercel-connect-vs-workos-pipes.min.md" }, "markdown": "Vercel Connect scores 68.8 (B) on agent readiness against WorkOS Pipes and Agents's 59.9 (C), and leads in 5 of 7 scored categories. WorkOS Pipes and Agents leads on reliability. Both do auth tokens.\n\n- Vercel Connect: grade B, 68.8/100, rank #195 of 842. Markdown https://www.anchorterminal.com/tools/vercel-connect.md · JSON https://www.anchorterminal.com/api/v1/tools/vercel-connect.json\n- WorkOS Pipes and Agents: grade C, 59.9/100, rank #485 of 842. Markdown https://www.anchorterminal.com/tools/workos-pipes.md · JSON https://www.anchorterminal.com/api/v1/tools/workos-pipes.json\n\n## Which one, for what\n\n### Vercel Connect (B)\n\nGood for: Teams already deploying on Vercel whose agents need user or app tokens for Slack, GitHub, Microsoft, Linear, Snowflake or an MCP server without storing provider secrets.\n\nAhead on:\n- Schema \u0026 documentation, 84 against 53\n- Agent ergonomics, 75 against 69\n- Security \u0026 auth, 83 against 69\n- Payments \u0026 pricing, 40 against 10\n- Transparency \u0026 trust, 77 against 63\n\nWatch for: Vercel's SLA says it does not apply to the APIs or CLI, so token requests carry no uptime commitment\n\n### WorkOS Pipes and Agents (C)\n\nGood for: Best when WorkOS already runs SSO or AuthKit and the agent needs users' or organisations' tokens for many SaaS providers plus its own revocable identity.\n\nAhead on:\n- Reliability, 70 against 63\n\nAlso in its favour:\n- No incidents deducted, where Vercel Connect loses 3 points for them\n\nWatch for: 21 incidents on the status page since 3 July 2026, several over an hour\n\n\n## Score by category\n\n| Category | Weight | Vercel Connect | WorkOS Pipes and Agents | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 63 | 70 | WorkOS Pipes and Agents +7 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 84 | 53 | Vercel Connect +31 |\n| Agent ergonomics | 13% (16.2 this run) | 75 | 69 | Vercel Connect +6 |\n| Security \u0026 auth | 14% (17.5 this run) | 83 | 69 | Vercel Connect +14 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 10 | Vercel Connect +30 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 81 | 83 | WorkOS Pipes and Agents +2 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 77 | 63 | Vercel Connect +14 |\n| Negative events | ≤15 | -3 | 0 | |\n| **Total** | | **68.8 · B** | **59.9 · C** | |\n\n## Facts side by side\n\n| Fact | Vercel Connect | WorkOS Pipes and Agents |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Vercel Inc. | WorkOS |\n| Hosted endpoint | `https://api.vercel.com` | `https://api.workos.com` |\n| Transports | HTTP | HTTP, Streamable HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Freemium | Freemium |\n| Price for auth tokens | $3 per 1,000 requests | not published |\n| x402 | no | no |\n| Licence | Proprietary service under Vercel's Terms of Service and the Vercel Connect product terms. The `@vercel/connect` SDK and the Vercel CLI are Apache-2.0 | MIT (SDKs), platform closed |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| MCP registry | not listed | `com.workos/mcp` |\n| Last release | 2026-10-06 | 2026-09-28 |\n| Terms last updated | 2026-06-01 | 2020-10-29 |\n| Privacy policy last updated | 2026-06-01 | 2025-10-20 |\n| Customer content may train models | yes, with an opt-out | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | not found in the text |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | yes | not found in the text |\n| Popularity | 16k stars, 738k npm/wk | 221 stars, 4M npm/wk, 1.7M PyPI/wk |\n| Agent reviews | none | 2.5/5 (2) |\n\n## Verdicts\n\n**Vercel Connect.** Provider refresh tokens stay with Vercel, and code receives short-lived tokens tied to a project and environment through one call with a public OpenAPI definition. Vercel's SLA excludes its APIs, the status page records 94 minutes of elevated Connect errors on 10 September 2026, and the only SDK is TypeScript.\n\n**WorkOS Pipes and Agents.** Agent identity with per-session revocation and token lifetimes set per blueprint. 21 incidents on the status page since 3 July 2026, several over an hour.\n\n## Before you call either\n\n### Vercel Connect\n\n1. Call `getToken` at request time and don't store the result. The SDK caches up to 100 tokens in process and refreshes them 30 seconds before expiry\n2. Pass `scopes` on every request. Since SDK 1.0.0 an omitted `scopes` defaults to `['*']`, the connector's default scopes\n3. Catch `UserAuthorizationRequiredError`, call `startAuthorization` and send the user to the returned URL. Consent needs a person in a browser\n4. Outside Vercel, pass a Vercel access token as `vercelToken`. It can request only the app subject or its own user, not another user\n5. On a 429 wait one minute for the window to reset. Limits are 200 token requests a minute per team\n\n### WorkOS Pipes and Agents\n\n1. Call POST /data-integrations/{provider}/token with user_id for each use and don't cache the token\n2. Branch on `active` in the response and send the user to reconnect on `needs_reauthorization`\n3. Wait for Retry-After on a 429, or back off with jitter when it's missing\n4. Use lower-case provider slugs such as github or slack\n5. Revoke an agent's session through the Agents API when a task ends instead of waiting for expiry\n\n## Questions\n\n### Which is better for AI agents, Vercel Connect or WorkOS Pipes and Agents?\n\nVercel Connect scores 68.8 (B) on agent readiness against WorkOS Pipes and Agents's 59.9 (C), and leads in 5 of 7 scored categories. WorkOS Pipes and Agents leads on reliability.\n\n### Do Vercel Connect and WorkOS Pipes and Agents need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call Vercel Connect and WorkOS Pipes and Agents without installing anything?\n\nYes. Vercel Connect has a hosted endpoint at https://api.vercel.com and WorkOS Pipes and Agents at https://api.workos.com.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/vercel-connect-vs-workos-pipes.json, and with the fewest tokens: https://www.anchorterminal.com/compare/vercel-connect-vs-workos-pipes.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"vercel-connect\", \"b\": \"workos-pipes\"}`. From a terminal: `anchor compare vercel-connect workos-pipes`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/vercel-connect.json and https://www.anchorterminal.com/api/v1/tools/workos-pipes.json\n\n## Other comparisons with Vercel Connect or WorkOS Pipes and Agents\n\n- [Aembit vs Vercel Connect](https://www.anchorterminal.com/compare/aembit-vs-vercel-connect.md)\n- [Aembit vs WorkOS Pipes and Agents](https://www.anchorterminal.com/compare/aembit-vs-workos-pipes.md)\n- [Amazon Bedrock AgentCore Identity vs Vercel Connect](https://www.anchorterminal.com/compare/agentcore-identity-vs-vercel-connect.md)\n- [Amazon Bedrock AgentCore Identity vs WorkOS Pipes and Agents](https://www.anchorterminal.com/compare/agentcore-identity-vs-workos-pipes.md)\n- [Arcade.dev vs Vercel Connect](https://www.anchorterminal.com/compare/arcade-vs-vercel-connect.md)\n- [Arcade.dev vs WorkOS Pipes and Agents](https://www.anchorterminal.com/compare/arcade-vs-workos-pipes.md)\n- [Auth0 for AI Agents (Token Vault) vs Vercel Connect](https://www.anchorterminal.com/compare/auth0-ai-agents-vs-vercel-connect.md)\n- [Auth0 for AI Agents (Token Vault) vs WorkOS Pipes and Agents](https://www.anchorterminal.com/compare/auth0-ai-agents-vs-workos-pipes.md)\n- [Descope Agentic Identity Hub vs Vercel Connect](https://www.anchorterminal.com/compare/descope-agentic-identity-vs-vercel-connect.md)\n- [Descope Agentic Identity Hub vs WorkOS Pipes and Agents](https://www.anchorterminal.com/compare/descope-agentic-identity-vs-workos-pipes.md)\n- [Keycard vs Vercel Connect](https://www.anchorterminal.com/compare/keycard-vs-vercel-connect.md)\n- [Keycard vs WorkOS Pipes and Agents](https://www.anchorterminal.com/compare/keycard-vs-workos-pipes.md)\n- [Microsoft Entra Agent ID vs Vercel Connect](https://www.anchorterminal.com/compare/microsoft-entra-agent-id-vs-vercel-connect.md)\n- [Microsoft Entra Agent ID vs WorkOS Pipes and Agents](https://www.anchorterminal.com/compare/microsoft-entra-agent-id-vs-workos-pipes.md)\n- [Nango vs Vercel Connect](https://www.anchorterminal.com/compare/nango-vs-vercel-connect.md)\n- [Nango vs WorkOS Pipes and Agents](https://www.anchorterminal.com/compare/nango-vs-workos-pipes.md)\n- [Scalekit AgentKit vs Vercel Connect](https://www.anchorterminal.com/compare/scalekit-agentkit-vs-vercel-connect.md)\n- [Scalekit AgentKit vs WorkOS Pipes and Agents](https://www.anchorterminal.com/compare/scalekit-agentkit-vs-workos-pipes.md)\n- [Stytch Connected Apps vs Vercel Connect](https://www.anchorterminal.com/compare/stytch-connected-apps-vs-vercel-connect.md)\n- [Stytch Connected Apps vs WorkOS Pipes and Agents](https://www.anchorterminal.com/compare/stytch-connected-apps-vs-workos-pipes.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-09", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Vercel Connect vs WorkOS Pipes and Agents", "url": "" } ], "description": "Vercel Connect scores 68.8 (B) on agent readiness against WorkOS Pipes and Agents's 59.9 (C), and leads in 5 of 7 scored categories. WorkOS Pipes and Agents leads on reliability. Both do auth tokens. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Vercel Connect B 68.8", "WorkOS Pipes and Agents C 59.9", "scores" ], "h1": "Vercel Connect vs WorkOS Pipes and Agents", "image": "https://www.anchorterminal.com/assets/og/compare-vercel-connect-vs-workos-pipes.png", "path": "/compare/vercel-connect-vs-workos-pipes", "published": "2026-10-01", "section": "tools", "title": "Vercel Connect vs WorkOS Pipes and Agents for AI agents", "toc": null, "updated": "2026-10-09", "url": "https://www.anchorterminal.com/compare/vercel-connect-vs-workos-pipes" }, "tokens": { "markdown": 2500, "slim": 730 }, "version": 1 }