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

Arcade.dev vs WorkOS Pipes and Agents

WorkOS Pipes and Agents scores 67.6 (B) on agent readiness against Arcade.dev's 66.5 (B), and leads in 2 of 7 scored categories. Arcade.dev leads on schema & documentation, payments & pricing and transparency & trust. Both do oauth for agents.

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

Which one, for what

Arcade.dev B

Best for A product whose agent acts in many users' SaaS accounts and wants the tools written and run for it, not only the tokens.

Ahead on

  • Schema & documentation, 87 against 63
  • Payments & pricing, 60 against 30
  • Transparency & trust, 71 against 65

Also in its favour

  • Runs on your own machine
  • Free to start without a card

Watch for

The terms of 15 July 2025 call the service an early version provided as is, with no uptime commitment below Enterprise

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 63
  • Maintenance & community, 86 against 76

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 Arcade.dev +30

Arcade.dev 60

No x402, MPP or L402 (0). Per-unit prices published without a login, $0.01 a tool call on Team, and the pricing page no longer lists an auth-event charge on 1 November (20). Free tier of 2,000 tool calls a month with no card (20). A person signs up in a browser to get a project key (0). 0 + 20 + 20 + 0 = 40. 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.

Reliability WorkOS Pipes and Agents +27

Arcade.dev 63

Atlassian Statuspage at status.arcade.dev with per-component history for the Engine API, Cloud API, Tools APIs and each provider integration (20). Three incidents from 3 August to 1 November, read from history.atom. On 29 October some tool authorisation links on Arcade Cloud returned a 502 for about five hours, later limited to a few MCP servers, while authorised tools kept running. On 6 and 7 October authorisation prompts hung in one client (Claude Cowork). On 7 October a Google authorisation report turned out to be a non-production environment. All partial, so minor only (20). The only rate limit with a number is 100 requests a minute on the audit-log API, nothing for the authorise or execute calls, per the 1 October check (5). Upstream rate limits come back as UpstreamRateLimitError with retry_after_ms and a documented wait-and-retry rule, but the OpenAPI file defines no 429 and no idempotency key, re-read on 1 November (8). Enterprise lists 24/7 SLA-backed support with no published uptime figure (5). The terms dated 15 July 2025 still call the service an early version under development, re-read on 1 November, so half marks for availability (5). 20 + 20 + 5 + 8 + 5 + 5 = 63.

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.

Schema & documentation Arcade.dev +24

Arcade.dev 87

OpenAPI 3.0 at api.arcade.dev/v1/swagger with 51 paths on 1 November (39 on 1 October) and Error schemas on 400, 401, 403, 404 and 500 among other codes (25). llms.txt and Markdown docs, and the releases site serves every page as Markdown (10). Operations carry summaries and descriptions, but they say what a call does more often than when to use it (14). Required fields and limits are typed (limit max 1,000 since 1.11.2, 25,000 before), though filter on formatted_tools is still a JSON string (11). The tool error hierarchy is documented with retryable and fatal classes and worked examples (12). Versioned under /v1, and the docs changelog now redirects to releases.arcade.dev, dated release notes for each version (1.11.4 on 28 October, 1.11.3 on 21 October, 1.11.2 on 13 October, 1.11.1 on 2 October) with a preview of what Arcade Cloud runs ahead of the next release (15). 25 + 10 + 14 + 11 + 12 + 15 = 87.

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.

Maintenance & community WorkOS Pipes and Agents +10

Arcade.dev 76

arcade-mcp 1.17.1 on 29 October 2026, published to PyPI by the repository's release-on-version-change workflow, and self-hosted Arcade 1.11.4 on 28 October (30). In the last 90 days arcade-mcp moved to 1.15.2, 1.16.0, 1.16.1, 1.16.2, 1.16.3, 1.17.0 and 1.17.1, and self-hosted Arcade shipped eleven dated releases from 1.9.5 (6 August) to 1.11.4 (20). Closed platform with a dated release-notes site, which replaced the docs changelog that stopped at 26 July 2026, a Discord community, and a GitHub repository where new issues are restricted. Issue reply times weren't re-read, since GitHub's pages answered 403 (10 of 15). The REST clients lag. arcadepy's newest tag is v1.10.0 of 6 November 2025 and @arcadeai/arcadejs's v2.4.1 of 21 April 2026, from clones on 1 November (8). CI workflows run on arcade-mcp, which supports Python 3.10 to 3.13 (8). 30 + 20 + 10 + 8 + 8 = 76.

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.

Transparency & trust Arcade.dev +6

Arcade.dev 71

Closed platform under terms that name Arcade AI, Inc. and California law, with the MIT arcade-mcp framework beside it (15). The Arcade Cloud page lists retention (logs and audit trails up to 1 year, training data up to 5 years) and AES-256 field encryption, but it says tool inputs and results become training data unless the organisation opts out, while the privacy policy of 10 September 2026 says content from connected third-party accounts isn't used to train models (15). No deprecation policy, and the terms say parts of the service may change or be removed with no stated notice (5). United States hosting is stated, and the privacy policy names 25 or more service providers as a partial list with the rest on request (12). The Arcade Cloud page and the privacy policy are per the 1 October check, not re-read on 1 November.

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.

Score by category

CategoryWeightArcade.devWorkOS Pipes and AgentsEdge
Reliability16%6390WorkOS Pipes and Agents +27
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8763Arcade.dev +24
Agent ergonomics13%8682Arcade.dev +4
Security & auth14%7169Arcade.dev +2
Payments & pricing10%6030Arcade.dev +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7686WorkOS Pipes and Agents +10
Transparency & trust7%7165Arcade.dev +6
Negative events≤15-7-3
TotalB 66.5/100B 67.6/100

Facts side by side

FactArcade.devWorkOS Pipes and Agents
KindHTTP APIHTTP API
VendorArcade.devWorkOS
Hosted endpointhttps://api.arcade.devhttps://api.workos.com
TransportsHTTP, Streamable HTTP, stdioHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceMIT (arcade-mcp framework and SDKs), platform closedMIT (SDKs), platform closed
Read-only variant documentedyesno
llms.txtyesyes
MCP registrynot listedcom.workos/mcp
Last release2026-10-292026-10-30
Terms last updated2025-07-152020-10-29
Privacy policy last updated2026-09-102025-10-20
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot 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
Popularity1k stars, 125k npm/wk, 70k PyPI/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.

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

Arcade.dev

Consent flow, token storage and refresh, and tool execution in one service, so the model never holds a provider token. The terms of 15 July 2025 call the service an early version provided as is, with no uptime commitment below Enterprise, and October's self-hosted releases fixed several access-control flaws without an advisory.

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

Arcade.dev

  1. Call POST /v1/tools/authorize first and send the user the returned URL when the status isn't completed
  2. Pass a stable user ID from your own database as user_id, never a shared value
  3. Read retry_after_ms on an UpstreamRateLimitError and wait that long before calling again
  4. Register your own OAuth app and a custom user verifier before real users sign in, because the default apps only accept members of your Arcade project
  5. Revoke a user's access with DELETE /v1/admin/user_connections/{id}
  6. Filter formatted_tools on read_only or destructive before handing a toolkit to an agent that shouldn't write

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, Arcade.dev or WorkOS Pipes and Agents?

WorkOS Pipes and Agents scores 67.6 (B) on agent readiness against Arcade.dev's 66.5 (B), and leads in 2 of 7 scored categories. Arcade.dev leads on schema & documentation, payments & pricing and transparency & trust.

Do Arcade.dev and WorkOS Pipes and Agents need an API key?

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

Can an agent call Arcade.dev and WorkOS Pipes and Agents without installing anything?

Yes. Arcade.dev has a hosted endpoint at https://api.arcade.dev and WorkOS Pipes and Agents at https://api.workos.com.

Other comparisons with Arcade.dev 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.