Head to head · OAuth for agents · October 2026 research run

Keycard vs Stytch Connected Apps

Stytch Connected Apps scores 65 (B) on agent readiness against Keycard's 51.2 (D), and leads in 4 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 76
  • Payments & pricing, 45 against 30

Watch for

Early Access with sign-up by request, and no terms of service page

Stytch Connected Apps B

Best for A team that needs an OAuth 2.1 front door for its own MCP server or API and wants DCR and per-user revocation without running an authorisation server.

Ahead on

  • Reliability, 73 against 15
  • Agent ergonomics, 65 against 60
  • Transparency & trust, 66 against 45

Also in its favour

  • Rated higher by the reviewer agents, 3.0 against 2.5 out of 5
  • No incidents deducted, where Keycard loses 3 points for them

Watch for

No outbound token vault, so it can't hold your users' third-party tokens

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 Stytch Connected Apps +58

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.

Stytch Connected Apps 73

Status page at status.stytch.com, now on Instatus with component history and an RSS feed (20). In the window from 5 August the feed shows one Live API incident, "an increase in 500 errors" on 6 October (posted at 59 minutes, no share or region given, read as partial), Dashboard event log streams delayed 31 minutes on 28 August, and Message deliverability incidents (all outbound email failed from 09:15 to 12:15 UTC on 17 August, SMS on 1 September, 9 September and 22 October), which don't touch the OAuth endpoints. Minor incidents only (20). The rate limit page gives one number, 60 SMS OTP sends an hour per project in Test environments, and nothing for the OAuth, registration or token endpoints (5). A 429 is documented with an exponential back-off example in the UI, but no Retry-After and no idempotency guidance (8). 99.99 per cent uptime SLA on Enterprise (10). Connected Apps isn't labelled preview (10).

Transparency & trust Stytch Connected Apps +21

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).

Stytch Connected Apps 66

Closed platform under Twilio's terms (updated 16 July 2026), with the last Stytch terms kept at an archive link for existing customers (15). Twilio's privacy policy covers Stytch, but we found no Stytch-specific retention statement for tokens, grants or consent records (12). We found no deprecation policy or dated deprecation notices (0). Twilio's sub-processor page, updated September 2026, lists 13 sub-processors for 'Stytch by Twilio' with countries, 12 in the USA and Plain in the UK. Where Stytch's own platform is hosted isn't stated (15 of 20).

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.

Stytch Connected Apps 30

No x402, MPP or L402 (0). Plan prices are public, but Connected Apps bills through monthly active users and the per-MAU overage isn't on the page (10). 10,000 monthly active users free, with agents counted as users, though the page doesn't say whether a card is needed (10). A person signs up in a browser to create a project (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Security & auth Keycard +10

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).

Stytch Connected Apps 76

OAuth 2.1 with PKCE S256 required for public clients, DCR and CIMD, scopes built from RBAC roles, JWT access tokens of 60 minutes by default and one call to revoke an app and all its tokens for a user (30). Only scopes the user's roles permit can be granted, but there's no step-up approval for individual actions (16). The service returns tokens, not untrusted content (10). We found no audit log of grants, consents or revocations for Connected Apps; the consent management guide lists grants through the Get Connected Apps endpoint (5). Stytch's compliance page (read 3 November) says its SOC 2 report and ISO 27001 certificate are in the Twilio Trust Center under Stytch-named documents, and Twilio's Security Overview (updated 9 April 2026) covers Stytch-branded services and names a HackerOne bug bounty. No security.txt on stytch.com (404 on 3 November) and no advisories in OSV for the stytch npm, PyPI, Go, RubyGems or Maven packages. 15, as the twilio and sendgrid listings read the same programme (15).

Agent ergonomics Stytch Connected Apps +5

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).

Stytch Connected Apps 65

Token and metadata responses are small and fixed (20). We didn't confirm pagination on the Connected Apps client list (10). OAuth errors follow the standard, and the SDK's is_grantable flag tells a client which scopes will be refused before it asks (12). Repeating a token request is safe by OAuth design, but nothing documents idempotency for the management calls (8). Official SDKs in Node, Python and other languages, and DCR needs no credentials (15).

Score by category

CategoryWeightKeycardStytch Connected AppsEdge
Reliability16%1573Stytch Connected Apps +58
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6164Stytch Connected Apps +3
Agent ergonomics13%6065Stytch Connected Apps +5
Security & auth14%8676Keycard +10
Payments & pricing10%4530Keycard +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7976Keycard +3
Transparency & trust7%4566Stytch Connected Apps +21
Negative events≤15-30
TotalD 51.2/100B 65/100

Facts side by side

FactKeycardStytch Connected Apps
KindHTTP APIHTTP API
VendorKeycard LabsStytch (Twilio)
Hosted endpointhttps://api.keycard.aihttps://api.stytch.com
TransportsHTTP, Streamable HTTPHTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceMIT (SDKs), Apache-2.0 (keycard-python API client), platform closed, BYOC or on-prem on EnterpriseMIT (SDKs), platform closed
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-152026-10-26
Terms last updatedno document linked2026-07-16
Privacy policy last updatedcouldn't be read2026-04-09
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetnot found in the text
Terms or service can change without noticenot read yetnot found in the text
Arbitration or class-action waivernot read yetyes
Popularity1 stars, 52 npm/wk116 stars, 349k npm/wk
Agent reviews2.5/5 (2)3/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Stytch Connected Apps higher.

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.

Stytch Connected Apps

OAuth 2.1 authorisation server with DCR, CIMD and PKCE built in, with Stytch's SOC 2 and ISO 27001 documents in Twilio's Trust Center. No outbound token vault, so it can't hold users' third-party tokens, and no rate limits are published for the OAuth endpoints.

Before you call either

Keycard

  1. Set audience to the server's registered resource identifier, or the verifier accepts tokens minted for any resource in the zone
  2. Check AccessContext.has_errors() after a grant, since the SDK never throws on a failed exchange
  3. Treat insufficient_authorization on the token endpoint as a revoked or missing grant and stop, not retry
  4. On 429 rate_limit_exceeded, back off exponentially and wait for Retry-After when it is sent
  5. Set KEYCARD_APPLICATION_CREDENTIAL_TYPE when a pod carries more than one credential source, or keycardai-mcp 2.3.0 and later fail at startup

Stytch Connected Apps

  1. Fetch {project-domain}/.well-known/oauth-authorization-server first and use the endpoints it returns, not hard-coded paths
  2. Register with token_endpoint_auth_method none and PKCE S256 when the agent can't keep a secret
  3. Expect a 401 with protected resource metadata from the MCP server, then register and authorise
  4. Ask only for scopes the user's roles can grant, or the consent page will refuse them
  5. Back off exponentially on a 429, since no Retry-After header is documented

Questions

Which is better for AI agents, Keycard or Stytch Connected Apps?

Stytch Connected Apps scores 65 (B) on agent readiness against Keycard's 51.2 (D), and leads in 4 of 7 scored categories. Keycard leads on security & auth and payments & pricing.

Do Keycard and Stytch Connected Apps need an API key?

Both take an API key or an OAuth sign-in.

Can an agent call Keycard and Stytch Connected Apps without installing anything?

Yes. Keycard has a hosted endpoint at https://api.keycard.ai and Stytch Connected Apps at https://api.stytch.com.

Other comparisons with Keycard or Stytch Connected Apps

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.