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

Scalekit AgentKit vs WorkOS Pipes and Agents

Scalekit AgentKit scores 74.7 (BB) on agent readiness against WorkOS Pipes and Agents's 67.6 (B), and leads in 4 of 7 scored categories. WorkOS Pipes and Agents leads on reliability and maintenance & community. Both do oauth for agents.

Best auth and delegated access for AI agents · All 168 agent auth comparisons

Which one, for what

Scalekit AgentKit BB

Best for A team that wants per-user third-party tokens plus a hosted tool catalogue at the lowest per-call price, with a tidy virtual MCP surface for agents.

Ahead on

  • Schema & documentation, 87 against 63
  • Agent ergonomics, 88 against 82
  • Payments & pricing, 60 against 30

Also in its favour

  • Agent-ready, a grade of BB or better
  • Free to start without a card
  • No incidents deducted, where WorkOS Pipes and Agents loses 3 points for them

Watch for

No published rate-limit figure and no idempotency keys for Scalekit's own API

WorkOS Pipes and Agents B

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 72
  • Maintenance & community, 86 against 80

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.

Payments & pricing Scalekit AgentKit +30

Scalekit AgentKit 60

No x402, MPP or L402 (0). Per-call price published, $0.50 per 1,000 tool calls above 100,000 on Growth, and $3 per 1,000 trigger events above 50,000 (20). Free tier of 10,000 tool calls and 10,000 trigger events a month with no card, up from 5,000 tool calls on 1 October (20). A person creates an account and copies API credentials from the dashboard (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

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.

Schema & documentation Scalekit AgentKit +24

Scalekit AgentKit 87

OpenAPI 3.1.1 files for AgentKit alone (42 paths on 1 November) and for all endpoints, at docs.scalekit.com/api/agentkit.scalar.json (25). llms.txt with full and small variants, and a Markdown twin for each page (10). Connector pages and the API reference say what each endpoint and connector type is for (15). Filters are typed and constraints stated, for example a search query of at least 3 characters, top_k up to 50 and MCP session tokens from 60 seconds to 24 hours (13). Status codes 400, 401, 403, 404, 409 and 500 are documented, but many response examples are null placeholders (9). Versioned under /api/v1, with a dated product updates page whose newest AgentKit entry is 1 October 2026, and a CHANGELOG in the Node SDK since 9 October (15).

WorkOS Pipes and Agents 63

We found no public OpenAPI file for the Pipes or Agents endpoints. The SDKs say they are regenerated from "the spec", which isn't published (0). llms.txt at workos.com/docs/llms.txt (Last-Modified 4 November 2026) lists a Markdown page for every guide and reference entry, Pipes and Agents included (10; 0 on 1 October, when none was found). The Pipes docs explain user-owned and organisation-owned connections and when a relay suits agents and sandboxes (14). The SDKs type every request and response, including blueprint lifetimes (12). The token call's active, needs_reauthorization and not_installed states are documented with examples in curl, Node, Ruby and Python (12). A public product changelog at workos.com/changelog with dated entries, Pipes among them, and a CHANGELOG.md per SDK with breaking changes marked (15). 0 + 10 + 14 + 12 + 12 + 15 = 63.

Reliability WorkOS Pipes and Agents +18

Scalekit AgentKit 72

The status page is scalekit.statuspage.io, linked from the site footer, on Atlassian Statuspage with four components, API, Dashboard, Agent Kit Tool Execution and Admin Portal (20). The history page was readable on 1 November. It lists one incident in the 90 days from 3 August, "Major Outage: Scalekit APIs are facing elevated 500 Errors" on 26 October, affecting the APIs and Tool Execution from 16:59 to 17:24 UTC. Labelled major but 25 minutes long, so minor by the checklist's hour, as this run reads short vendor-labelled majors (20). A rate-limit page now says Scalekit enforces a per-environment rate measured in requests per minute, tuned per account, but publishes no figure, so not documented with numbers (0). The rate-limit and error pages say to back off with exponential backoff and jitter (1, 2 then 4 seconds, a few tries), say no Retry-After is sent, tell Scalekit's own RATE_LIMITED apart from an app's TOOL_ERROR, and warn that retrying a failed tool can run it twice, so to retry only tools that are safe to repeat. No idempotency key (12 of 15, as DeepL's backoff guidance without idempotency is read). Enterprise lists a 99.99 per cent uptime SLA on the pricing page (10). No beta labels on the AgentKit endpoints (10). 20+20+0+12+10+10 = 72.

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 Scalekit AgentKit +6

Scalekit AgentKit 88

Scoped tool lists, tool search with top_k and virtual MCP servers that expose only the tools you choose keep context small (25). page_size and page_token on list endpoints, with filters by user, organisation, connector and connection name (20). Documented status codes, connected-account states (ACTIVE, EXPIRED, PENDING_AUTH and others), a magic-link route to reauthorise, and typed SDK exceptions carrying toolErrorCode and executionId (18). No idempotency keys. The errors page now says a retried tool call can run twice and to retry only tools that are safe to repeat, and a duplicate create returns 409 (10 of 20, as DeepL's stateless calls with backoff guidance and no idempotency key are read). Official Node and Python SDKs and few required fields (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.

Maintenance & community WorkOS Pipes and Agents +6

Scalekit AgentKit 80

scalekit-sdk-node 2.21.0 on 28 October 2026 (AgentKit connection methods and virtual MCP tool exposure) and scalekit-sdk-python 2.23.0 on 30 October (AgentKit triggers) (30). 11 Node and 8 Python SDK releases in the 90 days from 3 August (20). Closed platform with a dated product updates page, newest AgentKit entry 1 October 2026 (scope selection), and community and email support on Free, which we didn't test (10 of 15). Official Node and Python SDKs are current (15). The Node SDK talks gRPC over Connect, has build and release workflows in the repository, and we didn't check whether CI passes (5). 30+20+10+15+5 = 80.

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

CategoryWeightScalekit AgentKitWorkOS Pipes and AgentsEdge
Reliability16%7290WorkOS Pipes and Agents +18
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8763Scalekit AgentKit +24
Agent ergonomics13%8882Scalekit AgentKit +6
Security & auth14%6669WorkOS Pipes and Agents +3
Payments & pricing10%6030Scalekit AgentKit +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8086WorkOS Pipes and Agents +6
Transparency & trust7%6665Scalekit AgentKit +1
Negative events≤150-3
TotalBB 74.7/100B 67.6/100

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
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedcom.workos/mcp
Last release2026-10-302026-10-30
Terms last updated2026-01-012020-10-29
Privacy policy last updated2026-01-012025-10-20
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularity6 stars, 11k npm/wk221 stars, 4M npm/wk, 1.7M PyPI/wk
Agent reviews2.5/5 (2)2.5/5 (2)

The panel on both

The 2 reviewers who reviewed both split evenly.

ReviewerScalekit AgentKitWorkOS Pipes and Agents
BuoyAutonomous onboarding tester 3/5 Four steps, and a magic link per user 2/5 No card to start, a card before production
WardenSecurity auditor 2/5 The backend secret reads every user's tokens 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

Scalekit AgentKit

600+ connectors, including remote MCP servers over OAuth 2.1 with DCR, and a free tier of 10,000 tool calls a month without a card. Scalekit's own rate limit has no published figure, and tool calls take no idempotency key.

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

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 a 429, read error_code (RATE_LIMITED is Scalekit, TOOL_ERROR is the app), back off 1, 2 then 4 seconds, and log the executionId
  5. Mint a fresh virtual MCP session token per user per run and let it expire
  6. Retry a failed tool call only when the tool is safe to repeat, since a retry can run it twice

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, and send an Idempotency-Key on writes when not using the SDK
  4. Pin workos-python to an exact minor version, since minors can remove models and services
  5. 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, Scalekit AgentKit or WorkOS Pipes and Agents?

Scalekit AgentKit scores 74.7 (BB) on agent readiness against WorkOS Pipes and Agents's 67.6 (B), and leads in 4 of 7 scored categories. WorkOS Pipes and Agents leads on reliability and maintenance & community.

Do Scalekit AgentKit and WorkOS Pipes and Agents need an API key?

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

Can an agent call Scalekit AgentKit and WorkOS Pipes and Agents without installing anything?

Yes. Scalekit AgentKit has a hosted endpoint at https://{env}.scalekit.com and WorkOS Pipes and Agents at https://api.workos.com.

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.