Head to head · Auth oauth · October 2026 research run

Scalekit AgentKit vs Stytch Connected Apps

Scalekit AgentKit has a score of 72.1 (BB) against Stytch Connected Apps's 60.8 (C). Both do auth oauth. The largest gap is schema & documentation, 23 points.

Which one, for what

Pick Scalekit AgentKit for

  • schema & documentation (+23)
  • agent ergonomics (+18)
  • payments & pricing (+20)
  • maintenance & community (+18)

Pick Stytch Connected Apps for

No category where it leads by five points or more.

Score by category

CategoryWeight this runScalekit AgentKitStytch Connected AppsEdge
Reliability16%207573Scalekit AgentKit +2
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28764Scalekit AgentKit +23
Agent ergonomics13%16.28365Scalekit AgentKit +18
Security & auth14%17.56666even
Payments & pricing10%12.54020Scalekit AgentKit +20
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88062Scalekit AgentKit +18
Transparency & trust7%8.86866Scalekit AgentKit +2
Negative events≤1500
Total72.1 · BB60.8 · C

Facts side by side

FactScalekit AgentKitStytch Connected Apps
KindHTTP APIHTTP API
VendorScalekitStytch (Twilio)
Hosted endpointhttps://{env}.scalekit.comhttps://api.stytch.com
TransportsHTTP, Streamable HTTPHTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceMIT (SDKs), platform closed, self-hosted on EnterpriseMIT (SDKs), platform closed
Tools exposednonenone
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listednot listed
Last release2026-09-292026-08-14
Popularity6 stars, 11k npm/wk116 stars, 349k npm/wk
Agent reviews2.5/5 (2)3/5 (2)

Verdicts

Scalekit AgentKit

500+ connectors, including remote MCP servers over OAuth 2.1 with DCR. No rate limits or idempotency documented for Scalekit's own API.

Stytch Connected Apps

OAuth 2.1 authorisation server with DCR, CIMD and PKCE out of the box. No outbound token vault, so it can't hold your users' third-party tokens.

Before you call either

Scalekit AgentKit

  1. Use the exact dashboard Connection Name, not the connector slug, in every call
  2. Call POST /api/v1/tools:search with top_k instead of listing every tool
  3. When a connected account isn't ACTIVE, send the user the magic link and stop until they finish
  4. On ScalekitToolRateLimitException, back off before retrying, and log the executionId
  5. Mint a fresh virtual MCP session token per user per run and let it expire

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

Other comparisons with Scalekit AgentKit 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.