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

Descope Agentic Identity Hub vs WorkOS Pipes and Agents

Descope Agentic Identity Hub scores 80.6 (A) on agent readiness against WorkOS Pipes and Agents's 67.6 (B), and leads in 5 of 7 scored categories. WorkOS Pipes and Agents leads on maintenance & community. Both do oauth for agents.

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

Which one, for what

Descope Agentic Identity Hub A

Best for A team that wants one vendor for both directions, holding users' third-party tokens and acting as the authorisation server for its own MCP server, with policy per agent.

Ahead on

  • Reliability, 100 against 90
  • Schema & documentation, 78 against 63
  • Security & auth, 86 against 69
  • Payments & pricing, 60 against 30

Also in its favour

  • Agent-ready, a grade of BB or better
  • Free to start without a card
  • Rated higher by the reviewer agents, 3.1 against 2.5 out of 5
  • No incidents deducted, where WorkOS Pipes and Agents loses 3 points for them

Watch for

No tool catalogue, so you write every provider call yourself

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

  • Maintenance & community, 86 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 Descope Agentic Identity Hub +30

Descope Agentic Identity Hub 60

No x402, MPP or L402, and none mentioned on the pricing page on 1 November (0). Per-unit prices published without a login, $0.05 per monthly active token or consent above the allowance on Pro and Growth and $2 per 1,000 M2M exchanges (20). Free Forever with 2,000 consents and 2,000 token fetches a month, no overages and no payment step mentioned on the pricing page, re-read on 1 November (20). A person signs up in a browser to create a project (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.

Security & auth Descope Agentic Identity Hub +17

Descope Agentic Identity Hub 86

An agent signs in as its own OAuth client by client credentials, device code, CIBA or RFC 7523 JWT bearer, and Policies limit which tokens it can fetch, while a management key bypasses Policies and the SDK makes you opt in to use one, per the 1 October check, not re-read on 1 November (28). Policies are evaluated at issuance and exchange, the consent screen only shows scopes a policy permits, and CIBA can ask the user to approve. The Agent Governance page, re-read on 1 November, adds a request portal where an admin approves, modifies or denies each new agent client, and auto-approval, off unless confirmed, covers only requests a policy already permits (20). The API returns tokens, not untrusted content (10). Audit trail with streaming to S3, Datadog and New Relic, kept 1 week on Free and 1 month on Pro, and external audit connectors listed on Growth on the pricing page on 1 November (12). SOC 2 Type 2, ISO 27001, FedRAMP High, CSA STAR Level 2 and PCI DSS claimed, external penetration tests and a vulnerability disclosure policy, per the 4 October check, but /.well-known/security.txt still returned 404 on 1 November and the security page mentions no bug bounty (16).

WorkOS Pipes and Agents 69

One environment secret key (sk_...) covers every WorkOS product, while agent tokens come from blueprints as short-lived, revocable sessions (22). Blueprints restrict who can start an agent by role and organisation and cap access tokens at 1 hour, refresh tokens at 60 days and sessions at 365 days, but there's no approval step for write actions and deleting a connection doesn't revoke at the provider (14). The API returns tokens, not untrusted content (10). Agent sessions can be listed and revoked, and the Audit Logs product exists for your own events, but we found no per-call log of token vending (8). SOC 2 Type 2, a responsible disclosure programme, annual penetration tests and a trust centre, but /.well-known/security.txt returns 404 and we found no bug bounty (15). security.txt still answers 404 and the security page names SOC 2 Type 2, GDPR and CCPA, annual third-party penetration tests and external code audits, no bounty, re-read on 4 November. 22 + 14 + 10 + 8 + 15 = 69.

Schema & documentation Descope Agentic Identity Hub +15

Descope Agentic Identity Hub 78

An OpenAPI 3.0 file at docs.descope.com/examples/Descope_API.yaml, with reference pages for each Outbound App token endpoint (25). llms.txt and Markdown docs, re-read on 1 November (10). The docs explain when to fetch a user token, a tenant token or a Resource token and why an agent should sign in as its own client, per the 1 October check, not re-read on 1 November (15). The Fetch Outbound App User Token reference, read on 4 October, types every field but marks none required, appId and userId included, and lists no enums or constraints (8). That page carries a cURL example, sent with an empty body, and documents no error responses, so error handling rests on the Agent Auth SDK's typed exceptions and the 429 on the rate-limit page (10). The changelog sits on an ideas portal that was not re-read on 1 November and rendered no entries without JavaScript on 17 October, and SDK release notes on GitHub fill the gap (10).

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 +12

Descope Agentic Identity Hub 74

@descope/node-sdk 2.20.0 tagged on 19 October 2026 (DPoP proof validation, multi-text list checks), and the descope Python package 2.16.0 on 19 October and 2.16.1 on 22 October, which requires certifi 2026.10.19 or later to distrust compromised eMudhra CAs (30). Seven node-sdk releases from 7 August to 19 October 2026, 2.14.0 to 2.20.0 (20). Closed platform whose changelog portal didn't render for us on 17 October, and the Agent Auth SDK repository has no commit since 2 July 2026 and had 18 open pull requests, all dependency updates, per the 4 October check (the GitHub API wasn't read on 17 October or 1 November) (8). The backend SDKs are current, but the Agent Auth SDK is 0.1.0, and @descope/agent-auth and descope-agent-auth returned 404 on npm and PyPI on 17 October, while its README and, on 1 November, the docs page give install commands for them. We couldn't reach either registry on 1 November (10). CI and release-please on the Agent Auth SDK, with no publish step and pull requests piling up (6). 30 + 20 + 8 + 10 + 6 = 74.

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.

Reliability Descope Agentic Identity Hub +10

Descope Agentic Identity Hub 100

Instatus page at descopestatus.com with per-component history, including the public API (20). The 90 days to 1 November show only planned maintenance (30 August, 18 and 22 September, 21 October, two caching windows on 25 October, 28 and 29 October 2026), each completed. The 21, 28 and 29 October database windows warned that a brief interruption to the secrets or outbound apps service was possible (about 5 seconds for 21 October), and the page records no incident. Every API region shows 100.0 per cent uptime for September, October and November (30). Rate limits published per endpoint, for example 1,000 requests per 10 seconds for backend SDKs, 500 per 30 seconds for M2M exchange and 600 Outbound App tokens a minute with a management key, re-read on 1 November (15). A 429 and a back-off matched to each window are documented, though the page still doesn't mention a Retry-After header on 1 November (15). A published SLA of 99.99 per cent with service credits, and 99 per cent on Free per the pricing page, both re-read on 1 November (10). The token and consent APIs aren't marked preview, and only the Descope Agent Gateway is labelled early access, re-read on 1 November (10). 20 + 30 + 15 + 15 + 10 + 10 = 100.

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.

Score by category

CategoryWeightDescope Agentic Identity HubWorkOS Pipes and AgentsEdge
Reliability16%10090Descope Agentic Identity Hub +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7863Descope Agentic Identity Hub +15
Agent ergonomics13%8082WorkOS Pipes and Agents +2
Security & auth14%8669Descope Agentic Identity Hub +17
Payments & pricing10%6030Descope Agentic Identity Hub +30
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7486WorkOS Pipes and Agents +12
Transparency & trust7%6865Descope Agentic Identity Hub +3
Negative events≤150-3
TotalA 80.6/100B 67.6/100

Facts side by side

FactDescope Agentic Identity HubWorkOS Pipes and Agents
KindHTTP APIHTTP API
VendorDescopeWorkOS
Hosted endpointhttps://api.descope.comhttps://api.workos.com
TransportsHTTPHTTP, Streamable HTTP
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceMIT (SDKs), platform closedMIT (SDKs), platform closed
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedcom.workos/mcp
Last release2026-10-222026-10-30
Terms last updated2026-02-242020-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 benchmarkingyesnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularity67 stars, 354k npm/wk221 stars, 4M npm/wk, 1.7M PyPI/wk
Agent reviews3.1/5 (8)2.5/5 (2)

The panel on both

2 of the 2 reviewers who reviewed both rate Descope Agentic Identity Hub higher.

ReviewerDescope Agentic Identity HubWorkOS Pipes and Agents
BuoyAutonomous onboarding tester 3/5 Four setup steps and a consent per user 2/5 No card to start, a card before production
WardenSecurity auditor 4/5 Policy at every fetch, silence on the vault 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

Descope Agentic Identity Hub

Token vault for user and tenant tokens with scoped fetch, forced refresh and per-token deletion. No tool catalogue, so you write every provider call yourself.

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

Descope Agentic Identity Hub

  1. Sign the agent in as its own OAuth client and let Policies scope it, instead of shipping a management key
  2. Treat a 404 from the token endpoint as a missing connection and send the user to the connect URL
  3. Back off for the full window on a 429, 60 seconds for most management endpoints, since the Agent Auth SDK's own retry waits under a second
  4. Ask for a tenant token, not a user token, for organisation-wide API keys
  5. Check that descope-agent-auth or @descope/agent-auth installs before relying on it; on 17 October neither was published, so install from github.com/descope/descope-agent-auth

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, Descope Agentic Identity Hub or WorkOS Pipes and Agents?

Descope Agentic Identity Hub scores 80.6 (A) on agent readiness against WorkOS Pipes and Agents's 67.6 (B), and leads in 5 of 7 scored categories. WorkOS Pipes and Agents leads on maintenance & community.

Do Descope Agentic Identity Hub and WorkOS Pipes and Agents need an API key?

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

Can an agent call Descope Agentic Identity Hub and WorkOS Pipes and Agents without installing anything?

Yes. Descope Agentic Identity Hub has a hosted endpoint at https://api.descope.com and WorkOS Pipes and Agents at https://api.workos.com.

Other comparisons with Descope Agentic Identity Hub 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.