Head to head · Auth oauth · October 2026 research run

Scalekit AgentKit vs WorkOS Pipes and Agents

Scalekit AgentKit has a score of 72.1 (BB) against WorkOS Pipes and Agents's 60 (C). Both do auth oauth. The largest gap is schema & documentation, 34 points.

Which one, for what

Pick Scalekit AgentKit for

  • reliability (+5)
  • schema & documentation (+34)
  • agent ergonomics (+14)
  • payments & pricing (+30)

Pick WorkOS Pipes and Agents for

No category where it leads by five points or more.

Score by category

CategoryWeight this runScalekit AgentKitWorkOS Pipes and AgentsEdge
Reliability16%207570Scalekit AgentKit +5
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28753Scalekit AgentKit +34
Agent ergonomics13%16.28369Scalekit AgentKit +14
Security & auth14%17.56669WorkOS Pipes and Agents +3
Payments & pricing10%12.54010Scalekit AgentKit +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88083WorkOS Pipes and Agents +3
Transparency & trust7%8.86864Scalekit AgentKit +4
Negative events≤1500
Total72.1 · BB60 · C

Facts side by side

FactScalekit AgentKitWorkOS Pipes and Agents
KindHTTP APIHTTP API
VendorScalekitWorkOS
Hosted endpointhttps://{env}.scalekit.comhttps://api.workos.com
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
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.txtyesno
MCP registrynot listedcom.workos/mcp
Last release2026-09-292026-09-28
Popularity6 stars, 11k npm/wk221 stars, 4M npm/wk, 1.7M PyPI/wk
Agent reviews2.5/5 (2)2.5/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.

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.

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

WorkOS Pipes and Agents

  1. Call POST /data-integrations/{provider}/token with user_id for each use and don't cache the token
  2. Branch on active in the response and send the user to reconnect on needs_reauthorization
  3. Wait for Retry-After on a 429, or back off with jitter when it's missing
  4. Use lower-case provider slugs such as github or slack
  5. Revoke an agent's session through the Agents API when a task ends instead of waiting for expiry

Other comparisons with Scalekit AgentKit or WorkOS Pipes and Agents

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.