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

Nango vs WorkOS Pipes and Agents

Nango and WorkOS Pipes and Agents score within a point of each other on agent readiness, 68 (B) and 67.6 (B). WorkOS Pipes and Agents leads on reliability and agent ergonomics. Both do oauth for agents.

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

Which one, for what

Nango B

Best for A product that connects many users to many SaaS APIs and wants tokens, refresh, syncs and a per-tenant MCP surface in one place, with source you can read.

Ahead on

  • Schema & documentation, 85 against 63
  • Payments & pricing, 60 against 30
  • Transparency & trust, 77 against 65

Also in its favour

  • Rated higher by the reviewer agents, 3.5 against 2.5 out of 5

Watch for

Audit trail only on Enterprise, and logs kept 15 days on every plan

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 78
  • Agent ergonomics, 82 against 74

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 Nango +30

Nango 60

No x402, MPP or L402 (0). Per-unit prices published without a login, $0.29 per connection a month, $0.72 per compute hour and $0.50 per GB on Pay-as-you-go, re-read on 1 November 2026 (20). Free plan with 10 connections, 10 compute hours and 10 GB a month, and no card per the 1 October check (20). 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): 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 Nango +22

Nango 85

OpenAPI 3.1 file in the repository at docs/spec.yaml, last changed 30 October 2026 (25). llms.txt and Markdown docs (10). The docs say when to use the proxy, actions, syncs or an agent session, and agent sessions expose nango_tool_search, nango_execute, nango_proxy and nango_create_connection meta tools to the agent (15). The OpenAPI file types the management endpoints, but the proxy passes provider requests through untyped by design (10). Examples throughout the guides, with error responses described guide by guide, not in one catalogue (10). A dated changelog with breaking changes called out, 14 dated entries in October 2026 alone (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 +12

Nango 78

Better Stack page at status.nango.dev with history, though it tracks one component, Nango Cloud Health (20). Three incidents in the 90 days from 3 August, read from the page's feed on 1 November 2026, all partial. Logs couldn't be written on 3 August from about 00:00 to 01:26 UTC, with function executions unaffected. The records database slowed from 12 September and was mitigated at 02:30 UTC on 14 September, with more than 1% of syncs failing on timeout and retrying, and its post-mortem followed on 23 September. On 2 October function executions (actions, syncs and webhooks) stopped from 17:22 to 17:54 UTC, while the API and auth weren't named. No outage of the whole service (20). Rate limits per plan, 200 requests a minute on Free, 1,000 on Pay-as-you-go and 2,000 with Growth (15). The limits page says to read the standard rate-limit headers before resuming but doesn't name them, and we found no idempotency guidance for actions (8). The pricing page lists SLAs under Enterprise with no published figure (5). Auth, proxy and agent sessions are sold as GA (10).

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.

Transparency & trust Nango +12

Nango 77

Source on GitHub under the Elastic License 2.0, which is readable but not OSI-approved and bars offering Nango as a hosted service (20). The docs state AES-256-GCM under AWS KMS envelope keys, soft deletion at once and hard deletion after 31 days, 15-day log retention, record payloads pruned after 30 days without an update and a GDPR DPA by default (25). Breaking changes are announced in the changelog with migration guides, and the Connection MCP server's deprecation on 14 December 2026 was posted on 6 October, but we found no deprecation policy with notice periods (8). The docs say tokens sit in PostgreSQL in AWS, but we didn't find a public subprocessor list outside the trust centre (10).

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.

Agent ergonomics WorkOS Pipes and Agents +8

Nango 74

An agent session serves only the tools for one tenant's tagged connections through its own MCP URL, with a proxy meta tool instead of hundreds of tool definitions (20). Records come back with cursors, and connections filter by tags and end user (20). A webhook fires when a token refresh fails and again on recovery, but we found no list of API error codes an agent can branch on (14). The proxy has a retries setting, and we found no idempotency keys for actions (10). Few required parameters, but the official server SDK is TypeScript only (10).

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.

Score by category

CategoryWeightNangoWorkOS Pipes and AgentsEdge
Reliability16%7890WorkOS Pipes and Agents +12
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8563Nango +22
Agent ergonomics13%7482WorkOS Pipes and Agents +8
Security & auth14%7169Nango +2
Payments & pricing10%6030Nango +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%9086Nango +4
Transparency & trust7%7765Nango +12
Negative events≤15-8-3
TotalB 68/100B 67.6/100

Facts side by side

FactNangoWorkOS Pipes and Agents
KindHTTP APIHTTP API
VendorNangoWorkOS
Hosted endpointhttps://api.nango.devhttps://api.workos.com
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceElastic License 2.0MIT (SDKs), platform closed
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedcom.workos/mcp
Last release2026-10-292026-10-30
Terms last updatedno date given2020-10-29
Privacy policy last updatedno date given2025-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 noticeyesnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularity469k npm/wk221 stars, 4M npm/wk, 1.7M PyPI/wk
Agent reviews3.5/5 (2)2.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Nango 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

Nango

Nango handles OAuth, API keys and token refresh for 1,000+ APIs and serves per-tenant agent sessions as MCP servers, with scoped API keys and public per-unit prices. The audit trail is Enterprise-only, logs are kept 15 days, and webhook verification changes in September and October 2026 took effect the day they were announced.

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

Nango

  1. Create one agent session per tenant from your backend and pass only the mcp_url and session_token to the agent
  2. Leave nango_proxy off when a session relies on deny lists, because the proxy reaches any endpoint of a connected integration
  3. Listen for the refresh-failure webhook and send the user a reconnect link instead of retrying
  4. Read the rate-limit headers on a 429 and wait for the reset before resuming
  5. Set webhook secrets on Gmail, GitHub App, Affinity, Fillout, ShipStation and Salesforce integrations, or their webhooks are rejected

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, Nango or WorkOS Pipes and Agents?

Nango and WorkOS Pipes and Agents score within a point of each other on agent readiness, 68 (B) and 67.6 (B). WorkOS Pipes and Agents leads on reliability and agent ergonomics.

Do Nango and WorkOS Pipes and Agents need an API key?

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

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

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

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