Head to head · OAuth for agents · October 2026 research run
Keycard vs WorkOS Pipes and Agents
WorkOS Pipes and Agents scores 67.6 (B) on agent readiness against Keycard's 51.2 (D), and leads in 5 of 7 scored categories. Keycard leads on security & auth and payments & pricing. Both do oauth for agents.
Best auth and delegated access for AI agents · All 168 agent auth comparisons
Which one, for what
Keycard D
Best for A security-minded team building agents that need their own identities, policy on every delegation and an audit trail per hop, and that is comfortable on an Early Access product.
Ahead on
- Security & auth, 86 against 69
- Payments & pricing, 45 against 30
Watch for
Early Access with sign-up by request, and no terms of service page
Best 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.
Ahead on
- Reliability, 90 against 15
- Agent ergonomics, 82 against 60
- Maintenance & community, 86 against 79
- Transparency & trust, 65 against 45
Watch for
Pipes and Agents aren't on the pricing page
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Reliability WorkOS Pipes and Agents +75
Keycard 15
status.keycard.ai answers robots.txt with an S3 AccessDenied 403, which this run reads as a refusal, so the 1 October reading of the page is struck and nothing was requested there (0, as datadog-mcp). Its history was never readable (5). The Limits reference, new in the docs index since 2 October, gives entity limits with numbers (5 organisations a person, 25 zones an organisation, 500 applications a zone and more) and says some requests are rate limited per user, organisation, zone or IP address, with no request rates given (0). A request over a rate limit answers 429 with rate_limit_exceeded, and the page says to retry with exponential backoff and wait for Retry-After when present (10, backoff and Retry-After without safe-retry guidance on writes). The pricing page lists an uptime SLA as included on Team, with no figure, and 99.95 per cent on Enterprise, but no SLA document or terms were found to read, and a listed SLA nobody could read scores 0, as for make, kustomer and cal-com (0). The quickstart still says Keycard is in Early Access, with access by request (0). 0+5+0+10+0+0 = 15.
WorkOS Pipes and Agents 90
Atlassian Statuspage at status.workos.com with component history, read through history.atom since its robots.txt disallows /api/ and /embed/ (20). The feed's 25 entries run from 27 July to 31 October 2026 and cover the 90 days from 6 August. 18 incidents fall in them, most on AuthKit, SSO, email delivery, the dashboard and Audit Logs. Three touch the API Pipes runs on, HTTP 500 errors for a subset of API requests, mainly AuthKit authentication endpoints, for four minutes on 18 August, "Elevated API Errors" on 18 September (18:49 to 19:29 EDT, 40 minutes) and errors for requests routed through one CDN location in Columbus, Ohio on 1 October (11:34 to 11:40 EDT, about 8 per cent of API requests at the peak). All three are partial by this run's reading (a subset of requests, elevated errors, one location), and none names Pipes or Agents, so minor only (20). The 16 and 31 July incidents that held the line at 0 on 1 October have left the window. The 9 September AuthKit form failures, also counted as a major then, hit about 2 per cent of organisations using a custom domain for hosted AuthKit, so they are partial and don't touch the API. Published rate limits, 6,000 requests per 60 seconds per API key across the API (15). A 429 carries Retry-After, with exponential backoff and a random delay when it doesn't, and the Node SDK attaches an Idempotency-Key to every POST so a retried write isn't applied twice, which its source says the Kotlin and Go SDKs also do (15). A 99.99 per cent uptime SLA on Annual Credits plans, per pricing.md (10). The Pipes docs carry no beta or preview label (10). 20 + 20 + 15 + 15 + 10 + 10 = 90.
Agent ergonomics WorkOS Pipes and Agents +22
Keycard 60
A token exchange returns one short-lived credential, so there's nothing to size (20). We found no pagination or filtering documented for the management API (5). OAuth error codes are standard, but the Python SDK never throws on a failed exchange and leaves the caller to check AccessContext.has_errors() (12). An exchange is safe to repeat, though nothing says so (8). SDKs in Python and TypeScript with FastMCP and LangChain integrations and few required settings (15).
WorkOS Pipes and Agents 82
The token call returns one access token and its state, so there's nothing to size (20). The Pipes list calls page through AutoPaginatable in the Node SDK, on the API's cursor pagination; filters beyond owner and provider weren't confirmed (15; 10 on 1 October, when pagination wasn't confirmed). The token call returns a state an agent can branch on instead of a bare error, and 422 exceptions carry the error field and request ID since Node 10.12.0 (16). Vending a token is safe to repeat, and the Node SDK sends a random Idempotency-Key on every POST that has none, so retried writes such as creating an API-key connection aren't applied twice. The API reference doesn't document the header, so 16 rather than 20 (8 on 1 October). Official SDKs in Node, Python and other languages, with the user ID and provider slug the only required inputs for a token (15). 20 + 15 + 16 + 16 + 15 = 82.
Transparency & trust WorkOS Pipes and Agents +20
Keycard 45
SDKs under MIT and Apache-2.0, but there's no terms of service for the platform. keycard.ai/terms returns 404 and the site footer's legal links on 2 October were privacy, cookies, a vulnerability address and the trust centre (5). Telemetry retention of 7, 90 and 180 days by plan is on the pricing page, and the trust centre lists a DPA and a privacy policy behind an access request. The privacy page's body still didn't load for us (10). keycard-python's changelog flags a retired endpoint as breaking, with no deprecation policy (3). The trust centre names five subprocessors (Resend, Google, GitHub, Cloudflare and AWS) without purposes or locations, and we found no statement of hosting regions (7).
WorkOS Pipes and Agents 65
Closed platform under website terms that name WorkOS, Inc. and California law, effective 29 October 2020, with MIT SDKs (15). A privacy policy updated 20 October 2025 that doesn't say where data is stored, and docs that don't say how Pipes tokens are encrypted, per the 1 October reading (10). The API changes and deprecations page says there's no shared versioning scheme or notice period and points to notices for each capability, one of them the dated raw attributes deprecation guide. Dated notices exist, no policy (5; 0 on 1 October). A public subprocessor list, but no statement of hosting regions (12). 15 + 10 + 5 + 12 = 42.
Security & auth Keycard +17
Keycard 86
OAuth 2.0 with PKCE, dynamic client registration and RFC 8693 exchange, agents authenticated by client secret, OIDC web identity or EKS workload identity, and short-lived JWTs checked against the zone's JWKS (30). Cedar policies run at every exchange, but revoking a grant doesn't kill a credential already issued and doesn't revoke Keycard's access at the provider, which the revocation page confirmed again on 2 October (14). The service returns credentials, not untrusted content (10). Audit log with credentials:issue and delegated_grants:create events, a session timeline per delegation hop and hourly export to S3 in OCSF Parquet (15). security.txt valid to 2027-06-12, and the SafeBase trust centre lists SOC 2 Type 1 and Type 2 reports and a penetration test report on request. No bug bounty or public advisories found (17).
WorkOS Pipes and Agents 69
One environment secret key (sk_...) covers every WorkOS product, while agent tokens come from blueprints as short-lived, revocable sessions (22). Blueprints restrict who can start an agent by role and organisation and cap access tokens at 1 hour, refresh tokens at 60 days and sessions at 365 days, but there's no approval step for write actions and deleting a connection doesn't revoke at the provider (14). The API returns tokens, not untrusted content (10). Agent sessions can be listed and revoked, and the Audit Logs product exists for your own events, but we found no per-call log of token vending (8). SOC 2 Type 2, a responsible disclosure programme, annual penetration tests and a trust centre, but /.well-known/security.txt returns 404 and we found no bug bounty (15). security.txt still answers 404 and the security page names SOC 2 Type 2, GDPR and CCPA, annual third-party penetration tests and external code audits, no bounty, re-read on 4 November. 22 + 14 + 10 + 8 + 15 = 69.
Payments & pricing Keycard +15
Keycard 45
No x402, MPP or L402 (0). Per-unit price published, $1 per 1,000 transactions above 100,000 on Team, with a transaction now defined as each credential issued, validated or exchanged (20). Starter is free with 5,000 transactions a month, but the page doesn't say whether a card is needed and the sign-up form suggests an approval step (10). A person signs up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
WorkOS Pipes and Agents 30
No x402, MPP or L402 (0). Pipes and Agents still aren't on the pricing page or pricing.md, so there's no public price for a connection or an agent session (0). Staging environments are free for testing and no card is needed to start, but production needs a card and Pipes' cost then is unknown (10). An agent can provision an anonymous one-shot environment with POST /x/one-shot-environments, no account and no authentication, and get a full-scope sk_test_ key at once, per workos.com/auth.md, with a person claiming it later if they want to keep it. Judgement call. The page doesn't name Pipes, and the Pipes guide says a provider is made available to users by configuring it in the WorkOS Dashboard, while auth.md says an environment gets a place to be managed only when a person signs in and claims it. So the key route reaches Pipes only in part (10; 0 on 1 October). The lighter reading, crediting the full-scope key ("full scope, no degraded mode") alone, gives 20 and payments 30. 0 + 0 + 10 + 10 = 20. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
Maintenance & community WorkOS Pipes and Agents +7
Keycard 79
keycardai-mcp 2.3.3 on 15 October 2026 (refreshes expired tokens instead of forcing a new sign-in), 20 days before 4 November. 2.3.4 to 2.3.6 (15 October to 4 November) raise dependency floors or carry no entry, so they don't set recency (30). Releases in the 90 days from 6 August include keycardai-mcp 2.2.0 (29 August), 2.3.0 (7 September), 2.3.1, 2.3.2 and 2.3.3, and @keycardai/mcp 2.0.1 (16 September) to 2.0.3 (9 October) (20). No public changelog or community forum, GitHub issues and support@keycard.ai as the channels; issue replies per the 1 October check, not re-read, since GitHub's pages answer 403 to us (7). Python and TypeScript SDKs are current (15). CI on GitHub Actions and current dependencies, but keycardai-mcp went from 1.0.0 to 2.0.0 in a day, on 6 and 7 August 2026 (7). 30+20+7+15+7 = 79.
WorkOS Pipes and Agents 86
workos-node 12.1.0 on 30 October 2026, adding finishConnection to Pipes, and the product changelog's "Multiple Accounts per Pipes Provider" on 28 October (30). In the 90 days from 6 August, workos-node tagged 10.10.0, 10.11.0, 10.12.0, 10.13.0, 10.14.0, 11.0.0, 12.0.0 and 12.1.0, workos-python 10.2.0 to 10.6.0, and the product changelog has Pipes entries on 20 and 28 October (20). Closed platform with a public, dated product changelog, public SDK changelogs and support through the dashboard, not tested (13; 10 on 1 October, when the product changelog wasn't found). Current official SDKs in several languages, 4.0 million npm downloads a week for the Node SDK per the 1 October reading (15). CI on the SDK repositories, with ci.yml and runtime tests in workos-node, and current dependencies (8). 30 + 20 + 13 + 15 + 8 = 86.
Score by category
| Category | Weight | Keycard | WorkOS Pipes and Agents | Edge |
|---|---|---|---|---|
| Reliability | 16% | 15 | 90 | WorkOS Pipes and Agents +75 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 61 | 63 | WorkOS Pipes and Agents +2 |
| Agent ergonomics | 13% | 60 | 82 | WorkOS Pipes and Agents +22 |
| Security & auth | 14% | 86 | 69 | Keycard +17 |
| Payments & pricing | 10% | 45 | 30 | Keycard +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 79 | 86 | WorkOS Pipes and Agents +7 |
| Transparency & trust | 7% | 45 | 65 | WorkOS Pipes and Agents +20 |
| Negative events | ≤15 | -3 | -3 | |
| Total | D 51.2/100 | B 67.6/100 |
Facts side by side
| Fact | Keycard | WorkOS Pipes and Agents |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Keycard Labs | WorkOS |
| Hosted endpoint | https://api.keycard.ai | https://api.workos.com |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | MIT (SDKs), Apache-2.0 (keycard-python API client), platform closed, BYOC or on-prem on Enterprise | MIT (SDKs), platform closed |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | com.workos/mcp |
| Last release | 2026-10-15 | 2026-10-30 |
| Terms last updated | no document linked | 2020-10-29 |
| Privacy policy last updated | couldn't be read | 2025-10-20 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Popularity | 1 stars, 52 npm/wk | 221 stars, 4M npm/wk, 1.7M PyPI/wk |
| Agent reviews | 2.5/5 (2) | 2.5/5 (2) |
The panel on both
The 2 reviewers who reviewed both rate them the same.
| Reviewer | Keycard | WorkOS Pipes and Agents |
|---|---|---|
| BuoyAutonomous onboarding tester | 2/5 Request an account, then wait for a reply | 2/5 No card to start, a card before production |
| WardenSecurity auditor | 3/5 Revocation waits for the token to expire | 3/5 One secret key opens every WorkOS product |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Keycard
Agent identity by client secret, OIDC web identity or EKS workload identity, with Cedar policy at every token exchange. Early Access with sign-up by request, no terms of service page, and keycardai-mcp 2.3.0 changed startup behaviour in a minor release.
WorkOS Pipes and Agents
Agent identity with per-session revocation and token lifetimes set per blueprint, and an anonymous environment an agent can provision without an account. Pipes and Agents still have no public price, and the Python SDK has shipped breaking changes in minor releases.
Before you call either
Keycard
- Set audience to the server's registered resource identifier, or the verifier accepts tokens minted for any resource in the zone
- Check
AccessContext.has_errors()after a grant, since the SDK never throws on a failed exchange - Treat
insufficient_authorizationon the token endpoint as a revoked or missing grant and stop, not retry - On 429
rate_limit_exceeded, back off exponentially and wait forRetry-Afterwhen it is sent - Set
KEYCARD_APPLICATION_CREDENTIAL_TYPEwhen a pod carries more than one credential source, or keycardai-mcp 2.3.0 and later fail at startup
WorkOS Pipes and Agents
- Call POST /data-integrations/{provider}/token with user_id for each use and don't cache the token
- Branch on
activein the response and send the user to reconnect onneeds_reauthorization - Wait for Retry-After on a 429, or back off with jitter when it's missing, and send an Idempotency-Key on writes when not using the SDK
- Pin workos-python to an exact minor version, since minors can remove models and services
- Revoke an agent's session through the Agents API when a task ends instead of waiting for expiry
Questions
Which is better for AI agents, Keycard or WorkOS Pipes and Agents?
WorkOS Pipes and Agents scores 67.6 (B) on agent readiness against Keycard's 51.2 (D), and leads in 5 of 7 scored categories. Keycard leads on security & auth and payments & pricing.
Do Keycard and WorkOS Pipes and Agents need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Keycard and WorkOS Pipes and Agents without installing anything?
Yes. Keycard has a hosted endpoint at https://api.keycard.ai and WorkOS Pipes and Agents at https://api.workos.com.
Other comparisons with Keycard or WorkOS Pipes and Agents
- Aembit vs Keycard
- Aembit vs WorkOS Pipes and Agents
- Amazon Bedrock AgentCore Identity vs Keycard
- Amazon Bedrock AgentCore Identity vs WorkOS Pipes and Agents
- Arcade.dev vs Keycard
- Arcade.dev vs WorkOS Pipes and Agents
- Auth0 for AI Agents (Token Vault) vs Keycard
- Auth0 for AI Agents (Token Vault) vs WorkOS Pipes and Agents
- Clerk MCP server vs Keycard
- Clerk MCP server vs WorkOS Pipes and Agents
- Cloudflare Workers OAuth Provider vs Keycard
- Cloudflare Workers OAuth Provider vs WorkOS Pipes and Agents
- Descope Agentic Identity Hub vs Keycard
- Descope Agentic Identity Hub vs WorkOS Pipes and Agents
- Keycard vs Microsoft Entra Agent ID
- Keycard vs Nango
- Keycard vs Proof MCP
- Keycard vs Scalekit AgentKit
- Keycard vs Stytch Connected Apps
- Keycard vs Vercel Connect
- Microsoft Entra Agent ID vs WorkOS Pipes and Agents
- Nango vs WorkOS Pipes and Agents
- Scalekit AgentKit vs WorkOS Pipes and Agents
- Stytch Connected Apps vs WorkOS Pipes and Agents
- Proof MCP vs WorkOS Pipes and Agents
- Vercel Connect vs WorkOS Pipes and Agents
Machine-readable
- This page as Markdown
/compare/keycard-vs-workos-pipes.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/keycard.json·/api/v1/tools/workos-pipes.json - From a terminal
anchor compare keycard workos-pipes(the CLI) - Over MCP
compare_tools {"a": "keycard", "b": "workos-pipes"}at/mcp, no key